Copy-ready prompts

Build a single-purpose web app:

Product: [one sentence]
User: [who]
Primary job: [one action]
Must have:
- [flow 1]
Must NOT:
- login, multiplayer, payment
- purple gradients, emoji icons, lorem

UI: editorial dark, mobile-first, real copy
Definition of done:
- works ~390px width
- primary action has no console errors
- empty + success states

Ship name: [name]

Before changing any files, produce a plan only:

Goal: [...]
Constraints: [...]
Proposed steps: numbered, with file paths
Risks: [...]
Test command: [...]
Questions: only if blocked

Do not edit until I say APPROVE.

You are helping debug a [language/framework] project.
Goal: root cause + smallest safe fix.
Context:
- Error: [exact]
- Command: [test/build]
- Files: [paths + snippets]
Constraints:
- Do not rewrite unrelated code
- If evidence is thin, ask for the missing log/file
Output:
1) Root cause hypothesis
2) Files to inspect
3) Minimal patch
4) Test command

Implement [feature] in [paths].
Before editing: short plan + risks.
Constraints:
- Preserve public API unless noted
- Small reviewable diffs
- Update/add tests
Success:
- [test command] passes
- [behavior] unchanged outside feature

Review this diff as a senior engineer.
Focus: correctness, security, edge cases, missing tests.
Ignore pure style.
Return only:
- Blocking issues
- Non-blocking suggestions
- Tests to add
- Questions for the author

Do not add features. Fix only:

1) [exact bug — click path + what I saw]
2) [second bug]
3) Primary button label: “[verb]”

Keep the same layout structure.
List changes in bullets.

Audit this app for ship readiness.
Check: mobile layout, console errors, empty/error states, dead buttons, secrets, a11y basics, obvious performance issues.
Return checklist PASS/FAIL with the highest-risk FAIL first.

Explain this repo.
- What it does
- Folder map
- How to run dev/test/build
- Risks before editing
Keep it under one page.