start
Skill0 starsChanged 5 days agoMITView on GitHub
Start a new product with the Builder Method — sets up the builder/ folder, asks who the user is, and begins the Idea phase. Use when someone wants to build an app, website or tool from an idea, or says "start a builder project".
135 other projects use a version of this.
Adopted by
Most recently taken up by
- srinator22/agent-kerneltheir own version, first seen Nov 15, 2026
- willink-oss/willink-claude-kittheir own version, first seen Nov 15, 2026
- chuanglibs/Claude-Code-Game-Studios-Codextheir own version, first seen Nov 15, 2026
- relai-ai/agent-eval-looptheir own version, first seen Nov 15, 2026
- ansvisor/ansvisortheir own version, first seen Nov 8, 2026
- dsifry/metaswarmtheir own version, first seen Nov 8, 2026
Used with
Projects with it also use setup-engine, team-audio and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
CoralGameSkillsetup-engine
Configure the project's game engine and version. Pins the engine in CLAUDE.md, detects knowledge gaps, and populates engine reference docs via WebSearch when the version is beyond the LLM's training data.
Also in 13 projects that use this
CoralGameSkillteam-audio
Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation.
Also in 13 projects that use this
lilangMaxSkillcreate-stories
Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.
Also in 11 projects that use this
lilangMaxSkillstory-done
End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.
Also in 11 projects that use this
- +5 more from CoralGame
- +3 more from lilangMax
Other versions135 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 135
- anthropics/knowledge-work-plugins★ 36ksame name
- Donchitos/Claude-Code-Game-Studios★ 27ksame name
- openai/plugins★ 7.8ksame name
- SterlingChin/marvin-template★ 1ksame name
- educlopez/ui-craft★ 441same name
- ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool★ 432same name
- dsifry/metaswarm★ 426same name
- pixel-cellar/Claude-Code-Game-Studios★ 324same name
- ansvisor/ansvisor★ 233same name
- alexeykrol/claude-code-starter★ 194same name
125 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 2 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 122 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Read these first and follow them throughout:
- Very specific: line 16
If builder/state.json already exists in the current folder, don't change anything.
- Very specific: line 18
If there's no state.json but builder/*.md files exist (e.g.
- Distinctive: line 22
Ask, together in one short message (skip anything the user already told you):
- Very specific: line 27
If the user asked you to proceed with defaults, use: a name derived from what they said, none, and the language they wrote in.
- Very specific: line 36
all six phases { "status": "not_started" }.
- Very specific: line 38
Create the progress page, builder/progress.html plus builder/progress-data.js, exactly as state-rules.md ("Updating the progress page") …
“Common” is measured: kept by at least 6 in 10 of the 122 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Start a Builder project
You are the guide of the Builder Method: six phases (Idea → PRD → Design → Build → Iterate → Ship) that take a person who may not code from an idea to a published product.
Read these first and follow them throughout:
${CLAUDE_PLUGIN_ROOT}/skills/_shared/tone.md${CLAUDE_PLUGIN_ROOT}/skills/_shared/state-rules.md
1. Check for an existing project
If builder/state.json already exists in the current folder, don't change anything. Tell the user which project this is and where it stands (phase and step), and offer to continue with /builder:next. Stop here.
If there's no state.json but builder/*.md files exist (e.g. 01-idea.md, 02-prd.md), this is an existing project whose state was lost. Don't start fresh: rebuild the state as "Damaged or missing state" in state-rules.md explains, then offer /builder:next. Stop here.
2. Get to know the user
Ask, together in one short message (skip anything the user already told you):
- The project name: short, lowercase, hyphens are fine (e.g.
booking-app). - Their coding experience:
none,someordeveloper. - The language for the conversation and the project files (default: the language they are writing in).
If the user asked you to proceed with defaults, use: a name derived from what they said, none, and the language they wrote in.
3. Create the project
- Create
builder/state.jsonwith:schemaVersion: 1,pluginVersion: "0.1.0";project: { name, createdAt: <today YYYY-MM-DD>, hasFrontend: null };profile: { codingExperience, language }(language as a two-letter code such asenores);cycle: 1,currentPhase: "idea";- all six phases
{ "status": "not_started" }; flows: [],tasks: [],decisions: { pending: 0, total: 0 },debt: [].
- Create the progress page,
builder/progress.htmlplusbuilder/progress-data.js, exactly asstate-rules.md("Updating the progress page") explains. - Tell the user, in two or three lines, what the
builder/folder is, and that they can openbuilder/progress.htmlin a browser at any time to see where they are.
4. Begin
Explain the six phases in one short paragraph. Then start Phase 1 by following the idea skill (/builder:idea). If the user only asked to set up the project, stop after setup and point to /builder:next.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

