Hey everyone,

I built Builder Kit, a small open-source tool that turns one project idea into a full planning kit for vibe-coding projects.

How I built it:

\- Frontend: simple static UI, no account system

\- Backend: Node.js + Express

\- ZIP generation: "archiver"

\- Output: twelve Markdown files like "MASTERPLAN.md", "ROADMAP.md", "ARCHITECTURE.md", "CLAUDE.md", prompts, acceptance criteria, and a run log

\- No LLM is used at runtime — the documents are generated from structured templates and domain rules

The goal was to solve a problem I kept having: starting a new Claude Code project with no clear plan. Instead of asking Claude to build from a vague idea, this creates a structured repo-ready planning kit first.

Main build insight:

The most useful part was not generating more text, but making all files consistent with each other so Claude Code can treat the plan as the contract.

Demo:

https://claude-code-public-builder-kit.vercel.app

Repo:

https://github.com/BEKO2210/Claude-Code-Public-Builder-Kit

Would love feedback on the workflow, especially whether “no LLM at runtime” is a strength or a limitation.

One sentence in, complete project plan out