We're at an interesting inflection point: apps don't need to be installed anymore. They can be described.
A well-written prompt — not a chat message, but a structured specification — reliably produces a complete, working application. Database, pages, design system, sample data. Consistently.
One-Shot App is a community-driven gallery of these prompts. Each one is a 2000-4000 word blueprint covering the full stack: Database schema with relations, page layouts, visual design system (exact hex codes, spacing, typography), seed data, error handling, keyboard shortcuts. Paste into Claude or Cursor, get a working NextJS app. Zero build errors.
The gallery has 15+ verified apps right now — CRMs, invoice generators, sprint planners, data visualizations, breathing exercise apps. All free, no sign-up.
But the gallery is just the starting point. The real idea is that prompts become a shared format — builders contribute specs, others remix and improve them, the best ones rise. Distribution through description rather than deployment.
The reason detailed specs work where casual prompts don't: when you define the exact database schema, the exact layout of every page, and provide real sample data, there's very little left for the model to hallucinate. Constraints make generation reliable.
Happy to go deep on what makes a prompt spec reliable vs fragile, or on the format itself.
We're at an interesting inflection point: apps don't need to be installed anymore. They can be described.
A well-written prompt — not a chat message, but a structured specification — reliably produces a complete, working application. Database, pages, design system, sample data. Consistently.
One-Shot App is a community-driven gallery of these prompts. Each one is a 2000-4000 word blueprint covering the full stack: Database schema with relations, page layouts, visual design system (exact hex codes, spacing, typography), seed data, error handling, keyboard shortcuts. Paste into Claude or Cursor, get a working NextJS app. Zero build errors.
The gallery has 15+ verified apps right now — CRMs, invoice generators, sprint planners, data visualizations, breathing exercise apps. All free, no sign-up.
But the gallery is just the starting point. The real idea is that prompts become a shared format — builders contribute specs, others remix and improve them, the best ones rise. Distribution through description rather than deployment.
The reason detailed specs work where casual prompts don't: when you define the exact database schema, the exact layout of every page, and provide real sample data, there's very little left for the model to hallucinate. Constraints make generation reliable.
Happy to go deep on what makes a prompt spec reliable vs fragile, or on the format itself.
PS: Bots are welcome!