Direct answer
Claude Code works best when you give it a one-page app spec first. The spec should say who the app is for, what problem it solves, the version-one workflow, the screens it needs, the data it stores, and what you are not building yet. That gives Claude a target and keeps the project small enough to finish.
The template
What to put in each line
Who it is for
Be specific. “Non-technical founders” is better than “people.” “Small guesthouses in Pai” is better than “businesses.”
Main user workflow
This is the heart of the spec. Explain what the user does first, what happens next, and what the app must remember.
What not to build yet
This line saves projects. Leave out future features, fancy dashboards, multi-user complexity, and anything that would slow version one down.
A better prompt
FAQ
Do I need a full product plan?
No. One page is enough for version one.
Can Claude Code improve the spec?
Yes. Ask it to find unclear parts, suggest cuts, and recommend the smallest practical stack.
What if I do not know the tech stack?
Leave it out and let Claude Code recommend the simplest option after it reads your brief.