Copy this into a note
App name:
Who it is for:
Problem it solves:
Version-one outcome:
Main user workflow:
Screens needed:
Data the app stores:
Integrations:
Admin needs:
Design style:
What not to build yet:
Definition of done:
Read the full guide
How to use it
Keep each line short. Be specific about the user, the pain, and the first useful outcome. If you cannot fit the answer on one page, the project is probably too big for version one.
Example
App name: GuestTrack
Who it is for: small retreat businesses
Problem it solves: booking requests are scattered across too many channels
Best prompt to pair with it
Read this one-page app spec first.
Do not start coding yet.
First tell me:
1. What is still unclear
2. What version one should include
3. What should be cut
4. The smallest useful build plan
5. Any questions that materially affect the result
Then wait for my answer before making changes.
FAQ
How long should the spec be?
One page. If it gets longer, version one is probably too big.
Do I need a perfect stack first?
No. Start with the problem and the workflow. Add the stack after the target is clear.
Can Claude Code help improve the spec?
Yes. Ask it to identify unclear parts, suggest cuts, and propose the smallest practical plan.
Why it matters at Claude Camp
The spec is the first filter for turning a vague idea into a build path. That is why it belongs at the front of the course and at the front of a calm build week in Pai.
Apply for Claude Camp