APPLICATION BLUEPRINTS FOR CODING AGENTS
A prompt builds a generic app. A blueprint builds the right one.
Hand your coding agent a blueprint and it inherits the hundreds of domain decisions a prompt cannot carry: workflows, permissions, edge cases, regulatory rules, terminology, the things that normally take weeks of client workshops to pin down. The agent writes the code. The blueprint tells it what to build.
// faq
Frequently asked
What exactly is a blueprint?
A complete, human-readable specification of an entire application: data model, roles, flows and business rules, written to be handed to a coding agent rather than locked into one codebase.
Is a blueprint tied to a framework?
No. Every blueprint ships with a default stack as a starting point, but you can tell your agent to re-target any framework and regenerate the same product.
Do I need an account to download?
No. Reading and downloading blueprints never requires an account. Sign in only to submit or manage your own.
Can I sell what I build?
It depends on the licence on each blueprint. MIT and Apache-2.0 blueprints permit commercial use, modification and white-labelling with no attribution required in shipped software.
How do I use one with a coding agent?
Download the markdown and hand it to your agent as context. It builds the whole application from the blueprint. Prepend a one-line instruction to change the target stack.
What makes this better than a boilerplate?
A boilerplate hands you someone else's code and stack, permanently. A blueprint hands you the engineering judgement, and your agent generates fresh code on the stack you choose.
Ship your own blueprint.
Publish a blueprint once and let anyone regenerate it on any stack. Downloads are free, no account required to read.