Genesis operates through five specialised agents, each managing a distinct phase of the workflow.
Agents
interviewer.md
Reads the user's opening message, extracts project details, and asks only the minimum necessary follow-up questions.
planner.md
Assembles generation plans by consulting agent catalogues and stack profiles.
scaffold-writer.md
Handles application boilerplate: entry points, package configuration, and documentation.
claude-infra-writer.md
Writes Claude infrastructure components (CLAUDE.md, settings, agents, skills, memory) using templates.
finaliser.md
Manages git initialisation, commits, registry updates, and summaries.
Skills
Four primary skills support the workflow:
| Skill | Purpose |
|---|---|
/genesis | Main orchestrator coordinating the four-phase workflow |
/registry | Displays previously created projects in formatted tables |
/validate | Verifies Claude infrastructure completeness |
/update | Manages Genesis version updates while preserving user configuration |
Templates and references
Template files use {{PLACEHOLDER}} syntax and cover:
- CLAUDE.md skeletons (lean, standard, full variants)
- settings.json with permission and hook placeholders
- Agent instruction files
- Skill definition files
- Memory file templates
- MCP configuration templates
Reference documents include comprehensive agent catalogues and stack profiles spanning six supported stacks: Node.js/TypeScript, Python, Go, Rust, Ruby, and Java/Kotlin.
Memory and configuration
Genesis separates concerns into two categories:
- Version-controlled files: CLAUDE.md, agents, skills, templates, references. Updated when you pull new versions.
- Gitignored user files: personalisation.md, environment.md. Never overwritten by updates, preserving your preferences.
This separation means you can pull the latest Genesis improvements without losing your personal configuration.