Optional context
Add context when it helps
This prompt works as-is. Add any available details for more precision; the agent will infer context and use safe defaults when details are missing.
- A one-sentence product idea and target users
- Required technical or deployment constraints
- Observable acceptance criteria for the primary journey
- Boundaries for permitted assets and data
Ready-to-use prompt
Complete coding prompt
Copy and run it as-is. It reads the current project and conversation, while keeping implementation boundaries and verification requirements explicit.
Act as a coding agent responsible for end-to-end delivery. Turn the current product idea into a working Web MVP for the current target users, while respecting the current technical constraints and the current acceptance criteria. First inspect the current directory, available files, runtime, and repository conventions. If this is an empty project, choose the smallest stack that satisfies the constraints. If code already exists, reuse its structure, components, and scripts. Never invent files, APIs, command results, or business rules.
Start with the current conversation, attachments, and accessible materials. Treat available information as the input. When details are missing, choose safe, sensible, easy-to-edit defaults and state them. Ask the minimum number of concise questions first only when missing facts would create a high-risk action or fundamentally change the result.
Restate the user problem, the smallest complete user journey, and the explicit non-goals in one short section. Ask no more than three blocking questions, and only when a wrong answer would cause major rework; continue all work that does not depend on those answers. Implement one complete primary flow with clear information hierarchy, real interactions, credible sample data, and loading, empty, error, and retry states. Support mobile and desktop layouts, keyboard use, and semantic accessibility. Do not place secrets, personal information, or unlicensed assets in the code. Do not add authentication, administration, or abstractions that are unrelated to the MVP outcome.
Run the real application and exercise the primary journey instead of judging source code alone. Run the repository's applicable formatting, type, test, and build checks, then repair failures introduced by this task. Report the delivered behavior, important files, run instructions, observed verification evidence, unverified areas, and sensible next steps. Claim completion only when commands and page behavior actually pass; if permissions or external services block progress, state the exact blocker and leave a recoverable result.
After it finishes
Do not rely on a claim of completion
Check the real page, runtime behavior, and test evidence item by item.
- The primary journey works in the real page
- Loading empty error and retry states are observable
- Mobile desktop and keyboard behavior work
- Test and build evidence plus remaining risks are recorded truthfully
Inspiration source
This prompt is an original adaptation. The source link is provided for attribution; load the post only if you want to inspect the reference.
The X embed stays off until you choose to load it. Loading it may share your IP address and browser information with X.