agentleFS
craigcossairtcraigcossairt/trellis/.claude/skills/launch-check/SKILL.md

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

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
  1. Distinctive:

    Check for and flag any test/dev artifacts that would look unprofessional:

    line 16
  2. Distinctive:

    Search for hardcoded test emails, phone numbers, or names in the codebase

    line 18
  3. Very specific:

    Search for TODO, FIXME, HACK, XXX in screens/pages that are part of the demo flow

    line 19
  4. Distinctive:

    Check for debug print/log statements in production code paths

    line 20
  5. Distinctive:

    No default framework placeholder icons visible

    line 50

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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, XXX in 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 -20

2. 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.