Type
What are you building?
Pick the closest match. This shapes the tech stack and the shape of the output.
Overview
What's the name of your product or feature?
A clear, descriptive name helps Claude understand what it's building.
Examples: "Smart Recipe Finder", "Team Standup Bot", "Expense Tracker"
Overview
What problem does this solve?
Start with chips to flag the pain, then add one specific sentence about who has this problem.
Good: "Freelancers lose track of billable hours because switching between timer apps and invoicing tools is cumbersome." Avoid vague statements like "it's hard to manage things."
Overview
How does your product solve this?
2–3 sentences describing the core approach.
What's the goal of this build?
Shapes how polished and feature-complete the output needs to be.
Users
Who will use this?
Pick every archetype that fits.
Technical skill level?
Experience
Walk through the main user flow, step by step
From opening the app to completing the goal. Numbered steps work well.
What are the key screens or views?
One per line. Skip this if you're building a CLI tool, API, or automation.
Features
What are the must-have features?
Describe each feature concretely: what the user clicks, what shows up, how errors surface.
Quick-add common capabilities
Tap anything this build needs. Claude will wire these in.
AI-powered features?
Select any. Leave all unchecked if there's no AI involved.
Technical
What data does the app work with?
Describe the key entities. Even informal is fine — Claude will formalize it.
External integrations
Tick what's involved. Claude will mock these with realistic sample data for the prototype.
Technology stack
Pick one. If unsure, let Claude decide.
Design
Visual style
Pick the moods that fit. Combine freely.
Color palette
Pick a preset or describe your own below.
Layout priority
Design references
Sample content and copy
Only add if you want specific labels or data. Otherwise Claude will invent realistic samples.
Scope
What's explicitly NOT part of this build?
Ticking these tells Claude to mock or skip them. This is the fastest way to prevent scope creep.
Browser support, performance targets, accessibility level, offline, etc.
Success
What does success look like?
Concrete, observable. How will you know Claude hit the mark?
Edge cases, prior attempts, hidden constraints, inspiration.