Step 1 of 10
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?
Be specific about who has this problem and why current solutions fall short
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?
Describe the core approach in 2-3 sentences
What's the goal of this prototype?
This shapes how detailed the output needs to be
Users
Who will use this and in what context?
Describe the primary users, their skill level, and when they'd reach for this product
Think about: role, technical comfort level, context of use (on-the-go, at desk, in meetings), and what they're trying to accomplish.
Experience
Walk through the main user flow, step by step
Describe what happens from the moment the user opens the app to completing their goal
What are the key screens or views?
List every distinct screen the user will encounter
Features
What are the must-have features?
List each feature with enough detail that a developer could build it. Include what happens on click, what data is shown, and how errors are handled.
Any AI-powered features?
Describe any features that should use AI (summarization, generation, classification, recommendations, etc.)
Technical
What data does the app need to work with?
Describe the key data objects, even informally. What gets created, stored, or displayed?
Any APIs, integrations, or external data sources?
External services, authentication, data sources. Note what can be mocked for the prototype.
Technology preferences?
Choose based on complexity. Simple apps work great with plain HTML/CSS/JS.
Design
What visual style are you going for?
Describe the mood and aesthetic. References to known products work well.
Color preferences?
Specific hex codes, general direction, or a brand to reference
Layout priorities
Design references or inspiration?
Sample content and data
Provide realistic example data, button labels, and key copy the prototype should use
Scope
What's explicitly NOT included in this prototype?
Setting boundaries prevents scope creep and helps Claude focus on what matters
Any constraints or requirements?
Accessibility needs, performance targets, specific browser support, offline capability, etc.
Success
What does success look like for this prototype?
How will you know the prototype achieved its goal? Be concrete.
Anything else Claude should know?
Edge cases, assumptions, inspiration, prior attempts, or context that doesn't fit elsewhere