Kits¶
A kit is a set of template files that define a project's AI development workflow. When you run mold new or mold init, the selected kit determines which files are created.
Built-in kits¶
Original¶
The default kit. Provides a standard Claude Code workflow with markdown-based task tracking.
Files generated:
CLAUDE.md-- project instructions for Claude Code.claude/settings.json-- Claude Code settings with allowed commandsdocs/TODO.md-- markdown task list.repomixignore-- files excluded from Repomix contextrepomix.config.json-- Repomix configuration.claude/commands/review.md--/reviewslash command.claude/commands/test.md--/testslash command.claude/commands/doc.md--/docslash command.claude/commands/refactor.md--/refactorslash command
Select it: mold new my-app (default) or mold new my-app --kit original
Beads¶
Git-backed issue tracking via the bd CLI. Designed for developers who want structured issue management stored in their git history.
Files generated:
CLAUDE.md-- project instructions for Claude Code.claude/settings.json-- Claude Code settings.repomixignore-- Repomix exclusionsrepomix.config.json-- Repomix configuration.claude/commands/feature.md--/featureslash command.claude/commands/fix.md--/fixslash command.claude/commands/review.md--/reviewslash command.claude/commands/session-start.md--/session-startslash command.claude/commands/session-end.md--/session-endslash command
Select it: mold new my-app --beads or mold new my-app --kit beads
Forge¶
Product lifecycle orchestration -- AI-powered workflow from ideation to launch. Provides a structured forge/ directory with eight lifecycle phases, each containing guided templates for taking a product from idea to post-launch iteration.
Files generated:
CLAUDE.md-- project instructions for Claude CodeARCHITECTURE.md-- stack-aware architecture documentFORGE-GUIDE.md-- guide to the forge lifecycle workflow.claude/commands/ideate.md--/ideateslash command.claude/commands/research.md--/researchslash command.claude/commands/define.md--/defineslash command.claude/commands/design.md--/designslash command.claude/commands/develop.md--/developslash command.claude/commands/test.md--/testslash command.claude/commands/launch.md--/launchslash command.claude/commands/iterate.md--/iterateslash command.claude/commands/delegate.md--/delegateslash command.claude/commands/status.md--/statusslash command.claude/commands/session-start.md--/session-startslash command.claude/commands/session-end.md--/session-endslash commandforge/FORGE.md-- lifecycle overview and status trackerforge/01-ideation/-- idea capture and screeningforge/02-research/-- market analysis, competitive landscape, user personasforge/03-product-definition/-- PRD, MVP scope, roadmapforge/04-design/-- architecture, API design, tech stack, wireframesforge/05-development/-- sprint backlog, decisions, changelogforge/06-testing/-- test plan, bug tracker, security reviewforge/07-launch/-- deployment plan, go-to-market, launch checklistforge/08-post-launch/-- metrics, feedback log, iteration backlog
Forge enables beads issue tracking by default. Use --no-beads to disable it.
Select it: mold new my-product --kit forge
Without beads: mold new my-product --kit forge --no-beads
Custom kits¶
You can create your own kits with custom template files. See mold kit for registration and management.
A custom kit is a directory containing:
-
kit.toml-- metadata file (required):name = "my-kit" description = "My custom project template" -
Template files -- any files you want rendered into new projects. Templates support Go
text/templatesyntax with variables like{{ .ProjectName }},{{ .Author }}, and{{ .TechStack }}.
Registering a custom kit¶
mold kit add ~/my-kits/react-kit
Using a custom kit¶
mold new my-app --kit react-kit
Setting as default¶
mold config set default-kit react-kit
All kits include¶
Regardless of which kit you choose, all built-in kits generate:
CLAUDE.mdwith project instructions.claude/settings.jsonwith allowed commands.repomixignoreandrepomix.config.jsonfor Repomix- Claude Code slash commands
The difference is in the workflow philosophy: Original uses markdown TODOs, Beads uses git-backed issue tracking, and Forge provides a full product lifecycle with eight guided phases.