Start from a map, an op-log and a prompt.
A blueprint is three things: the primitives map for an app that ships on the platform today, the build as an op-log of named operations, and a starter prompt written in a builder's vocabulary. Copy the prompt, swap in your nouns, build.
Not installers. Blueprints are prompts and maps; your agent assembles the app from governed primitives, and you preview the diff before anything lands.
Six shapes we see most often.
Each card is a full build: objects, forms, workflows, grids, screens and groups, with the operation log and the prompt that produced them.
Field service inspection
A work queue on the inspector's phone, photo and signature capture, and a PDF report emailed to the site contact when the inspection is marked complete.
Compliance checklist
Sectioned checklists worked in stages, a reviewer sign-off with a signature, and a change log that records who changed what on every record.
CRM-lite
Accounts, contacts, tasks and whatever the customer calls the thing in the pipeline — deal, engagement, matter — plus a pipeline grid by stage and a workflow that assigns and emails the owner.
Approval workflow
A request form, routing by amount to a manager or a director, email at every step, and a change log that records who approved what and when.
Intake form and survey
A public form that takes submissions without a sign-in, a triage queue for the team behind it, and a change log on every record.
Ops dashboard frontend
A Vite/React dashboard over the tables you already have — one object view, one grid, four tiles and a trend — deployed and promoted through dev, staging and production.
No blueprint matches both filters yet. Clear one, or tell us which app you need.
Copy the prompt. Adjust the vocabulary. Build.
Copy the starter prompt.
Every blueprint ends in a prompt written the way the platform likes to be asked: groups first, then objects, forms, screens, workflow. Paste it into Claude Code or any MCP client connected through the desktop app.
Put your nouns in.
If your customer says job, not inspection, change it in the prompt. Objects, forms and the drawer come out in their language, because the agent creates what you describe.
Preview the diff, then commit.
The agent works through approximately 100 named operations on governed primitives. preview-solution-edit returns an entity-level diff you read before anything lands; commit-solution-edit lands it as one save.
The monster does the typing. You do the naming.
Illustrative until verified.
Every operation and primitive named in a blueprint exists on the platform today and appears in the operation list. We have not yet run each blueprint end-to-end and captured the screens — that is what the illustrative badge means. When we have, the badge flips to verified and the placeholders become screenshots.
Sending this to IT? The security overview answers authentication, groups and tenant isolation; the IT brief is the short version, and ownership covers what you keep.
Want a blueprint for something else? Tell us the app — or read the use cases for the longer version of each.
Bring us something you want built.
CodeMonster is invite only while we work directly with early adopters. Request an invite and we will meet, scope what you want to build, and get you productive. You bring the AI subscription you already pay for.