Full-Stack Planning Prompt: Build One Working Feature
Break an application idea into a small working flow, data model and tests. Review security and deployment decisions before production use.
Illustrative cover; not a verified result from this prompt.
Read the full prompt
Help plan and implement a small [APP TYPE] using [STACK AND VERSIONS]. Users need to [PRIMARY TASK]. Constraints: [CONSTRAINTS]. Start by identifying unanswered requirements, then propose one working end-to-end feature. Include the minimum data model, API contract, interface states, validation and tests. Add authentication only if the use case needs it, explaining the approach. Use placeholder environment variables rather than secrets. State what has not been executed or verified. Do not label untested generated code production-ready.
Begin with one complete user flow
An application is easier to check when the first version does one useful thing. Supply your stack versions and say whether users need accounts. A large request for every screen often leaves important behavior unfinished.
Example: a shared reading list
Start with “A local prototype where I add a book title, list saved books and mark one finished.” Ask for the data model, three corresponding operations and a simple screen showing loading, empty and error states. Keep payment, social sharing and notifications outside this first step.
Check what happens when the title is empty, the server is unavailable or the same submission is sent twice. These cases reveal more than an attractive success screenshot.
Review before deployment
Run the project and its meaningful tests in an isolated environment. Inspect input validation, access controls and database migrations before connecting real data. Do not paste production secrets into the conversation or commit them with the code. A generated Docker file or authentication example still needs review for your actual hosting environment.