Builder Kit

Free · No install · 30 seconds

From one sentence to a complete project plan.

Tell us your idea in plain language. Get back twelve ready-to-use planning documents — vision, roadmap, risks, architecture, and a starter prompt for Claude or ChatGPT. No terminal, no setup, no cloud account.

Launch the tool See how it works

✓ MIT-licensed open source ✓ Works without a Claude account ✓ Built by humans, runs without an LLM

How it works

From one word to a working project.

The wizard is just the entry door. Here is what actually happens between "I have an idea" and "Claude is shipping code for me".

  1. 1

    One word in.

    You type something short — even a single phrase like "Training Plan App". No essay required, no forms to fill out, no jargon expected.

  2. 2

    The wizard sharpens it.

    Three short follow-up questions: who's it for, what should it do better, and is anything sparse — then a one-glance summary before generating. If you only typed one word, the wizard nudges you to add a little more.

  3. 3

    12 documents are generated.

    Vision, roadmap, risks, architecture, marketing brief, prompts — all consistent with each other, all immediately useful. No TODO stubs, no placeholder paragraphs.

  4. 4

    You sharpen the plan with Claude Code.

    Use Claude Code — in your browser via your GitHub repo, or in your terminal in the unzipped folder. Claude Code reads every file in the kit and can edit them directly. Each session iterates on one piece of the plan — Phase 1 / Step 1, then Step 2, then a risk you want to dig into. The plan stops being a stub and becomes the spec your project actually runs on.

  5. 5

    Claude builds autonomously.

    Once the plan is sharp, Claude executes against it — writes the code, runs the tests, reports back. You stay in the loop only on decisions, not on every line. The masterplan is the contract; Claude works it down phase by phase.

Start with one word

Try these

Six ideas, one click each.

Each card runs the full generator on the deployed app. Click and watch — every kit is fresh, every kit is yours.

"A training plan app for amateur runners."

App, audience: amateur runners — domain inferred as health & wellness. ≈12 files, 47 sections, 6.8k words, < 1 second.

Generate this →

"A bookkeeping tool for solo freelancers."

Tool, audience: solo freelancers — domain finance. Includes auditable-defaults bullets, KYC posture notes, ADR template.

Generate this →

"A marketplace for indie crafters."

Platform/marketplace, audience: indie crafters — domain retail & e-commerce. PCI & storefront-accessibility risks built in.

Generate this →

"A volunteer scheduling platform for animal shelters."

Platform, audience: animal-shelter coordinators — domain non-profit & community. Donor-trust + volunteer safeguarding bullets baked in.

Generate this →

"A factory floor monitoring dashboard for small manufacturers."

Dashboard, audience: small manufacturers — domain manufacturing. OT/IT boundary risks, NIS2/IEC 62443, OEE/MTBF posture all wired in.

Generate this →

"A civic engagement app for municipal councils."

App, audience: municipal councils — domain government & civic. Procurement-aware, accessibility (WCAG) and FOI/transparency bullets included.

Generate this →

Real output

This is what the kit gives you.

One snippet from a real generated MASTERPLAN.md for the idea "A SaaS dashboard for small business accountants". Browse the full 12-file output on GitHub.

MASTERPLAN.md ~280 lines · 1 of 12 files 
## 1. One-line summary

A SaaS dashboard for small business accountants who need to see month-end
status across all their clients without bouncing between five tools.

## 2. Audience

Small business accountants — typically firms of 1–10 partners managing
30–200 clients each. They are domain experts, not power users; first-run
flow has to make the daily core action obvious in under three minutes.

## 3. Domain-specific risks (professional services)

- Trust and credibility: a single embarrassing output destroys word-of-mouth.
  Slow rollout and a supervised mode beat a fast generic launch.
- Client-data privacy: assume PII and privileged information will end up
  in the system. No third-party logging, conservative retention, clear
  export + delete on request.
- Liability and expectation management: the product assists, it does not
  give legal / financial / tax / strategic advice…

Inside every kit

Twelve files, every time.

Substantial content; no orphan TODO stubs (the test suite enforces that).

MASTERPLAN.md

Vision, scope, success metrics — single source of truth.

ROADMAP.md

Five phases from foundation to scale, each with an exit gate.

ARCHITECTURE.md

Recommended starting architecture and open questions.

ACCEPTANCE_CRITERIA.md

Phase-tied checklists of what "done" actually means.

DOCS/product-brief.md

Audience, jobs-to-be-done, top user stories.

DOCS/market-positioning.md

Positioning statement and competitive frame.

DOCS/technical-decisions.md

Stack candidates and an ADR template.

PROMPTS/initial-prompt.md

A drop-in first prompt to start your Phase 0 chat.

PROMPTS/run-plan-20-sessions.md

A 20-session execution plan from empty repo to product.

README.md

Project entry point with quick start and structure.

CLAUDE.md

Operating rules for any Claude Code session in your repo.

RUN_LOG.md

Append-only session journal, seeded with Run #001.

For developers

Or run it locally.

Same tool, your machine. Two runtime dependencies (Express + archiver), no build step, MIT licensed.

git clone https://github.com/BEKO2210/Claude-Code-Public-Builder-Kit
cd Claude-Code-Public-Builder-Kit
npm install
npm start
# open http://localhost:5173

Or hit the API directly: 

curl -s -X POST https://claude-code-public-builder-kit.vercel.app/api/generate.zip \
  -H 'Content-Type: application/json' \
  -d '{"idea":"A SaaS dashboard for small business accountants"}' \
  -o kit.zip