Setup flow
Docs
Generate the prompt for the required project foundation files.
What you need before starting
- Finish the intake inputs first so the prompt reflects the right context.
- Confirm the docs file list matches the fixed v1 scope.
Required files list
Generate only the setup docs needed for the fixed v1 flow.
- docs/brief.md
- docs/sitemap.md
- docs/ui-system.md
- docs/ux-rules.md
- docs/content-model.md
Docs generation prompt
Copy the exact prompt after checking the current project input.
Prompt for generating the setup docs
Create the required setup foundation docs for the project below.
Project name: App Setup Flow
Repo name: app-setup-flow
Folder name: app-setup-flow
One-line description: A guided setup tool for starting Next.js web app projects with exact steps, prompts, and done states.
Target audience: The product creator setting up new web app foundations.
Primary goal: Move from app idea to an agent-ready Next.js backbone.
Primary visitor action: Walk the flow phase by phase and copy the required commands and prompts.
Secondary actions:
Refine the project brief
Review generated outputs
Verify the backbone locally
Routes and pages:
/
/setup/intake
/setup/scaffold
/setup/docs
/setup/files
/setup/backbone
/setup/verify
Visual direction:
Warm off-white background, white and cool-tinted cards, anthracite text, light blue accents, subtle borders, subtle shadows.
UX rules:
Mobile first
Visible input labels
Copy buttons must be obvious
Current phase stays visible
Every setup page includes previous and next navigation
Constraints:
Next.js App Router
TypeScript
Tailwind CSS
Vercel
No auth in v1
No backend in v1
No analytics in v1
No CMS in v1
Required shared components:
Header
Footer
Container
Section
Card
Button
Input
Textarea
Phase progress nav
Code block with copy button
Prompt block with copy button
Checklist
Required UI states:
Default
Hover
Focus
Active phase
Empty context notice
Checklist complete state
Definition of done:
All main routes exist
Global layout exists
Shared UI primitives exist
Commands and prompts are easy to copy on mobile
The foundation can be refined without redesigning the structure
Return exactly these files with short direct copy:
- docs/brief.md
- docs/sitemap.md
- docs/ui-system.md
- docs/ux-rules.md
- docs/content-model.md
Keep the product as a guided setup tool for Next.js web app projects. Do not turn it into a marketing site or a generic docs site.Current project input preview
Review the shared context before generating the docs files.
Current project input
Driven by the shared project context used across the flow.
- Project name
- App Setup Flow
- Repo name
- app-setup-flow
- Folder name
- app-setup-flow
- One-line description
- A guided setup tool for starting Next.js web app projects with exact steps, prompts, and done states.
- Target audience
- The product creator setting up new web app foundations.
- Primary goal
- Move from app idea to an agent-ready Next.js backbone.
- Primary visitor action
- Walk the flow phase by phase and copy the required commands and prompts.
Secondary actions
- Refine the project brief
- Review generated outputs
- Verify the backbone locally
Routes and pages
- /
- /setup/intake
- /setup/scaffold
- /setup/docs
- /setup/files
- /setup/backbone
- /setup/verify
Visual direction
- Warm off-white background, white and cool-tinted cards, anthracite text, light blue accents, subtle borders, subtle shadows.
UX rules
- Mobile first
- Visible input labels
- Copy buttons must be obvious
- Current phase stays visible
- Every setup page includes previous and next navigation
Constraints
- Next.js App Router
- TypeScript
- Tailwind CSS
- Vercel
- No auth in v1
- No backend in v1
- No analytics in v1
- No CMS in v1
Required shared components
- Header
- Footer
- Container
- Section
- Card
- Button
- Input
- Textarea
- Phase progress nav
- Code block with copy button
- Prompt block with copy button
- Checklist
Required UI states
- Default
- Hover
- Focus
- Active phase
- Empty context notice
- Checklist complete state
Definition of done
- All main routes exist
- Global layout exists
- Shared UI primitives exist
- Commands and prompts are easy to copy on mobile
- The foundation can be refined without redesigning the structure