Understand the two halves of every web application using a restaurant analogy that makes it click.
"Before implementing this feature, split the work into frontend and backend responsibilities.
1. Explain what the user sees and interacts with
2. Explain what the server must handle behind the scenes
3. List the files or systems likely to change on each side
4. Call out any data that must never live in the frontend
5. Stop before changing auth, permissions, or the data model without my approval
I want a clean boundary, not a blurry full-stack mess."Prompt FAQ
Understand the two halves of every web application using a restaurant analogy that makes it click. Use it when you need a safer starting point than a blank prompt and you want the agent to stay inside explicit constraints.
No. Treat it as a safe starter. Replace the task, files, constraints, and verification details with your actual context before you run it.
Read the diff, run the checks, and stop after one reviewable step. If you need deeper context, open the lesson that explains the reasoning behind the prompt.
A practical framework for choosing the right tools and technologies for your project — with sensible defaults for AI-assisted builders.
Open prompt pageUnderstand how HTML provides structure and CSS provides style — the visual foundation of every web page.
Open prompt pageWhat JavaScript does, why TypeScript exists, and where you'll see them in every web project you build.
Open prompt page