Welcome to claude-base
Claude Code configuration template for an optimal workflow: Explore → Specify → Plan → TDD → Audit → Commit
claude-base is a complete set of configurations, commands, and automations to maximize your productivity with Claude Code. It offers a structured workflow and specialized agents for each type of task.
Why claude-base?
The problem
When you use Claude Code without structure:
- You code without understanding the existing code → bugs and regressions
- You implement without a plan → constant refactoring
- You make giant commits → unreadable history
- You waste time looking for the right commands
The solution
claude-base enforces a structured workflow:
Explore → Specify → Plan → TDD → Audit → Commit
Each step has its dedicated commands, specialized agents, and best practices.
Key numbers
| Component | Count | Description |
|---|---|---|
| Commands | 106 | Manually triggered commands (/name) |
| Agents | 44 | Autonomous sub-agents with isolated context |
| Skills | 53 | Auto-triggered on keywords |
| Rules | 32 | Rules per technology/file |
| Presets | 11 | Stack-specific bundles installable via --preset <name> |
Domains covered
| Domain | Commands | Description |
|---|---|---|
| WORK | 15 | Main workflow (explore, plan, commit, PR) |
| DEV | 16 | Development (TDD, API, components, debug) |
| QA | 13 | Quality (review, security, performance, a11y) |
| OPS | 28 | Operations (CI/CD, Docker, monitoring, GitFlow) |
| DOC | 5 | Documentation (changelog, README, architecture) |
| BIZ | 9 | Business (model, MVP, pricing, pitch) |
| GROWTH | 9 | Growth (SEO, analytics, landing, funnel) |
| DATA | 2 | Data (pipeline, analytics, modeling) |
| LEGAL | 5 | Legal (GDPR, ToS, payment) |
Quick start
# Install the foundation (one-liner)
curl -fsSL https://raw.githubusercontent.com/christopherlouet/claude-base/main/install.sh | bash
# Stack-specific init (auto-filtered foundation + curated vendor pointers)
claude-base init --preset nextjs ./my-web-app # Next.js fullstack
claude-base init --preset fastapi ./my-api # Python async backend
claude-base init --preset phaser ./my-game # 2D web game (vendor-pointer)
claude-base preset list # See all 11 presets
When no --preset is passed on an empty directory, an interactive prompt asks "What are you building?" with an 8-entry intent taxonomy (Web frontend / API-Backend / Mobile-Desktop / Game-Interactive media / Data-Database / Infra-DevOps / CLI-Automation / Other-Generic) and filters the subsequent menu accordingly.
Then in Claude Code:
# Discover available commands
/assistant
# Start by exploring the code
/work:work-explore
# Plan a change
/work:work-plan