Review This Prompt And Feedback it.

ROLE

You are an expert [e.g. full-stack developer / product designer / ML engineer] with deep experience in [tech stack / domain].

Your job is to build this project end-to-end — from architecture to final output — with zero hand-holding needed.

PROJECT

Name: [Project name]

Type: [Web app / CLI tool / API / Dashboard / Bot / etc.]

One-liner: [What it does in one sentence]

Target user: [Who will use this]

GOAL

Build a complete, working, production-ready [project type] that [core functionality].

The output must be immediately usable — not a skeleton, not a mockup. Real code. Real structure.

STACK

Frontend: [React / Next.js / HTML+CSS / etc. or "your call"]

Backend: [Node / FastAPI / Django / etc. or "your call"]

Database: [Supabase / MongoDB / SQLite / etc.]

Auth: [Clerk / Firebase / JWT / none]

Hosting target: [Vercel / Railway / local only]

→ If stack is flexible, write "Recommend and justify the best stack."

FEATURES

Must have {{(MVP)}}:

- [Feature 1]

- [Feature 2]

- [Feature 3]

Nice to have {{(if scope allows)}}:

- [Feature A]

- [Feature B]

CONSTRAINTS

- No [library/pattern you want to avoid]

- Must work on [OS / browser / environment]

- Budget/API limit: [free tier only / specific limit]

- Deadline pressure: [prototype in 1 day / full build in a week]

- [Any other hard rules]

DELIVER

Give me, in this exact order:

1. Project structure — full folder tree with file names

2. All source files — complete code, no placeholders, no "TODO"

3. Setup instructions — exact commands to install + run

4. Env variables list — every key needed with a sample value

5. What to build next — 3 smart next steps after MVP

   OUTPUT RULES

- Write every file in full — no truncation, no "...rest of code here"

- Use code blocks with language tags for every file

- If a file is long, still write it fully — I need copy-paste ready output

- Don't explain basics. I know how to code. Be concise where it's obvious.

- If you make a design decision, state it in one line. Don't over-justify.

- Ask clarifying questions ONLY if something is truly ambiguous. Otherwise, make the smart call and proceed.