Shawn Mervin

Build me something

Describe your business in a sentence. Five Claude agents plan it, design it, fill it with believable data, build a working app and inspect it, in about a minute, while you watch the yard.

Or try

The build crew is off shift right now. Shared builds still open; new ones are back soon.

Three builds per visitor per day. Each one runs five models, so they're rationed. Briefs are kept for 90 days with city-level location, never an IP.

  1. PlannerHaiku 4.5waiting
  2. DesignerHaiku 4.5waiting
  3. DataHaiku 4.5waiting
  4. BuilderSonnet 4.6waiting
  5. ReviewerHaiku 4.5waiting
your-app.prototype

The app appears here as the builder writes it.

Time—
Tokens—
Cost—

The planner turns your sentence into screens, records and the one action that saves you the most time.

How the yard works

infra/live/agent/build.mjs

One AWS Lambda function with response streaming runs the crew on Amazon Bedrock. The planner (Claude Haiku) turns your sentence into a plan. The designer and the data agent take that plan and work at the same time, which is why their crates leave the planner together. The builder (Claude Sonnet) waits for both, then writes the app, and every character streams to this page as it is written: the building in the yard rises with it. The reviewer runs automatic checks and reads the result.

What comes back is untrusted code, so it is treated that way. It runs in a sandboxed frame with no access to this site, its cookies or storage, and it carries a security policy that blocks every network request. A sketch is not a product: the reviewer's last word is always what a real build would add, and that part is my job.

  • multi-agent orchestration
  • Claude on Bedrock
  • Lambda streaming
  • sandboxed iframes + CSP
  • DynamoDB

Got an operation that's outgrown its spreadsheets?

Tell me what your business does and where it's jamming up. If I'm not the right person for it, I'll say so and point you somewhere better.

What to send, and what happens next