Vibe coding kickoff
From Proof of Concepts with AI - free, no signup needed.
Prompt template
Build a [TYPE OF APP/PROTOTYPE] with the following spec: User: [WHO WILL USE THIS AND WHAT THEY'RE TRYING TO DO] Key screens: 1. [SCREEN 1 - what it shows and what actions are available] 2. [SCREEN 2 - what it shows and what actions are available] 3. [SCREEN 3 - if needed] Key interactions: - [INTERACTION 1] - [INTERACTION 2] Visual style: [dark/light theme, minimal/bold, desktop/mobile, style reference if any] Data: use realistic hardcoded sample data - no backend needed. Out of scope: [LIST WHAT IT DOES NOT NEED TO DO] Build this as a single self-contained file. Prioritise: correct interactions > visual polish > completeness. Make it look intentional, not like a wireframe.
How to use it well
- Replace every [BRACKETED] placeholder - vague inputs produce vague outputs.
- Add your role and constraints at the top if your assistant does not already know them.
- Critique the first answer explicitly (“too generic because…”) and ask for a second pass.
- Save the version that worked into a project or system prompt so you never retype it.