Your build starts here
Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.
Build [product] for [users] so they can [main outcome].
Starting point: [new project or existing repository].
Main journey: [start action] -> [key steps] -> [successful result].
Required behavior: [small set of concrete capabilities].
Storage and accounts: [local/shared, signed in/anonymous, data ownership].
Design: [style, references, device sizes, accessibility needs].
Scope boundaries: [important exclusions or compatibility requirements].
Inspect the existing project and follow its conventions. For a new project,
choose a simple approach suited to these requirements and explain material
tradeoffs briefly. Implement the smallest complete user journey first,
then finish the required behavior.
Done means:
- [observable result]
- [relevant persistence or permission check]
- [failure or empty state]
Run appropriate checks. Report what changed, verification results,
and any remaining setup needed to use the result.Make this prompt yours
Replace bracketed fields with your goal, current behavior, and relevant evidence. Keep requirements that affect the task. Check the result against the acceptance criteria you supplied.
The docs behind it
These references explain the underlying concepts and APIs. The prompt templates and project plans are original examples to adapt to your own setup.
Documentation links checked .
Editorial review · October 28, 2026
Limited: Read the complete original template or project/path specification for conceptual consistency, explicit scope, and checkable outcomes. No implementation or prompt-quality benchmark was executed.