launch-check
Skill5 starsChanged 10 days agoMITView on GitHub
Run a pre-demo/pre-launch audit of the app - test data, broken screens, missing error states, brand consistency. Use when asked to 'demo check', 'launch check', 'pre-demo audit', 'check before user interview', 'audit before demo'.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- ssaarthakk/dev-setuptheir own version, first seen Nov 8, 2026
- Ces107/agent-forgetheir own version, first seen Oct 25, 2026
- lfxiui/usefulmint-skillstheir own version, first seen Oct 20, 2026
- matt-warchol/launch-checktheir own version, first seen Oct 20, 2026
- path-to-ai-com/ptai-ecom-toolkittheir own version, first seen Oct 15, 2026
- me2resh/apexyardtheir own version, first seen Oct 8, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- me2resh/apexyard★ 542same name
- ssaarthakk/dev-setup★ 2same name
- matt-warchol/launch-check★ 1same name
- 20030419zhanghongyi/AI-Software-Engineering-Workflow-Template★ 0same name
- Ces107/agent-forge★ 0same name
- lfxiui/usefulmint-skills★ 0same name
- path-to-ai-com/ptai-ecom-toolkit★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository48 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/project.mdcCursor rule
- bug-reportSkill
- build-verification-skillSkill
- daily-briefSkill
- grill-designSkill
- launch-checkSkill
- learnSkill
- pin-guardrailSkill
- prd-to-issuesSkill
- review-dependency-updatesSkill
- security-auditSkill
- setupSkill
- tddSkill
- trellis-surveySkill
- trellis-syncSkill
- worktreeSkill
- write-a-prdSkill
- build-verification-skillSkill
- daily-briefSkill
- grill-designSkill
- learnSkill
- pin-guardrailSkill
- prd-to-issuesSkill
- review-dependency-updatesSkill
- security-auditSkill
- setupSkill
- trellis-surveySkill
- trellis-syncSkill
- write-a-prdSkill
- bug-reportSkill
- build-verification-skillSkill
- daily-briefSkill
- grill-designSkill
- launch-checkSkill
- learnSkill
- pin-guardrailSkill
- prd-to-issuesSkill
- review-dependency-updatesSkill
- security-auditSkill
- setupSkill
- tddSkill
- trellis-surveySkill
- trellis-syncSkill
- worktreeSkill
- write-a-prdSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Check for and flag any test/dev artifacts that would look unprofessional:
- Distinctive: line 18
Search for hardcoded test emails, phone numbers, or names in the codebase
- Very specific: line 19
Search for TODO, FIXME, HACK, XXX in screens/pages that are part of the demo flow
- Distinctive: line 20
Check for debug print/log statements in production code paths
- Distinctive: line 50
No default framework placeholder icons visible
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
You are running a pre-demo audit. This ensures the app is presentable for user interviews, investor pitches, or a launch.
<!-- FILL IN: the bracketed slots below once the project has real screens and branding. -->Audit Steps
1. Test Data Cleanup
Check for and flag any test/dev artifacts that would look unprofessional:
- Search for hardcoded test emails, phone numbers, or names in the codebase
- Search for
TODO,FIXME,HACK,XXXin screens/pages that are part of the demo flow - Check for debug print/log statements in production code paths
grep -rn "TODO\|FIXME\|HACK\|XXX" <source-dir> | head -20
grep -rn "console\.log\|debugPrint\|print(" <source-dir> | head -202. Critical Screen Audit
Review each screen in the demo flow for polish (no layout overflow, no missing states):
<!-- FILL IN: list your critical screens/pages as checkboxes, grouped by flow -->- Entry point (splash / landing / login)
- Core flow screen 1
- Core flow screen 2
- Settings / profile
3. Error State Coverage
For each critical screen, verify:
- Empty state exists and is user-friendly (not blank or an error)
- Network error handling (what happens offline?)
- Loading states (skeleton/spinner, not blank white)
4. Brand Consistency
<!-- FILL IN: brand colors, fonts, logo asset names -->- Brand colors used consistently
- Correct fonts for headings and body
- Logo displays correctly
- No default framework placeholder icons visible
5. Static Analysis
# FILL IN: your lint/typecheck command, e.g. `npm run lint` or `flutter analyze`Output Format
Produce a report with:
- PASS items (confirmed good)
- WARN items (minor, won't break the demo but should fix)
- FAIL items (must fix before demo)
End with a prioritized fix list for any FAIL items.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

