kakaroto-config
v2.2.0
Published
Claude Code configuration by Pedro Jahara - autonomous workflows for /build, /resolve, /deliberate, /gate
Downloads
181
Maintainers
Readme
kakaroto-config
Claude Code configuration for autonomous development workflows.
Quick Install
# Local installation (recommended - installs to ./.claude/)
npx kakaroto-config
# Global installation (installs to ~/.claude/)
npx kakaroto-config --globalLocal is recommended because each project can have its own customizations while inheriting the global rules.
Updating
To update to the latest version, run the same command again:
# Update local installation
npx kakaroto-config@latest
# Update global installation
npx kakaroto-config@latest --globalThe installer will detect the existing .claude/ folder and ask if you want to overwrite.
Note: If you previously installed globally (
~/.claude/) and want to switch to local (./.claude/), just runnpx kakaroto-config@latestin your project folder. Both can coexist - Claude Code will use local config when available.
What Gets Installed
.claude/
├── CLAUDE.md # Global rules (autonomy, coding standards)
├── ARCHITECTURE.md # Full documentation of the system
├── skills/ # Skill workflows (invoked via /skill)
│ ├── build/SKILL.md # /build orchestrator (3 phases)
│ ├── build-understand/ # Phase: requirements + plan-file handling + V4+ approval
│ ├── build-implement/ # Phase: autonomous implementation (+ verify-template.md)
│ ├── build-certify/ # Phase: quality + deploy + prod verification
│ ├── resolve/SKILL.md # /resolve orchestrator
│ ├── resolve-investigate/ # Phase: diagnosis + QA reproduction (+ REDIRECT to /build)
│ ├── resolve-verify/ # Phase: user reviews diagnosis + QA flows
│ ├── resolve-fix/ # Phase: autonomous fix + local QA
│ ├── resolve-certify/ # Phase: quality + deploy + production QA
│ └── deliberate/ # /deliberate - adversarial solution design
├── commands/ # Commands (invoked via /command)
│ └── gate.md # /gate - quality gate before PR
├── hooks/ # Lifecycle hooks (10 total)
│ ├── _lib.sh # Shared helpers
│ ├── build-stop-guard.sh # Prevents stop during active workflow
│ ├── build-continuity-hook.sh # Injects next action between phases
│ ├── build-skill-register.sh # Claims session ownership
│ ├── build-session-recovery.sh # Detects and resumes stalled workflows
│ ├── build-implement-stop.sh # Enforces verify.sh for agents
│ ├── ask-user-empty-guard.sh # Rejects empty AskUserQuestion responses
│ ├── pre-commit-gate.sh # Quality checks before git commit
│ ├── stop-quality-check.sh # Quality checks before session stop
│ ├── permission-denied-log.sh # Logs permission denials for review
│ └── pre-compact-save.sh # Preserves workflow state before auto-compaction
└── agents/ # 8 specialized agents
├── build-implementer.md
├── resolve-fixer.md
├── test-fixer.md
├── code-reviewer.md
├── code-simplifier.md
├── functional-validator.md
├── terraform-validator.md
└── memory-sync.mdSkills & Commands
| Name | Type | Trigger | Description |
| ------------- | ------- | ----------------------------------- | --------------------------------------------------------------------------------------------------- |
| /deliberate | Skill | Manual | Adversarial solution designer: challenges framing, simulates scenarios as temporal narratives |
| /build | Skill | "adicionar", "implementar", "criar" | Full feature workflow: understand -> implement -> certify. Accepts plan files (.md paths) |
| /resolve | Skill | "bug", "erro", "problema" | Bug resolution: investigate -> verify -> fix -> certify (auto-redirects feature requests to /build) |
| /gate | Command | Manual | Run quality agents before PR |
Workflow Chain
/deliberate (optional) Solution design: challenge framing, scenarios, refinement
|
/build Implementation: spec -> implement -> certify/resolve Autonomous bug fix: investigate -> verify -> fix -> certify
(Feature requests are auto-redirected to /build)Agents (Subagents)
| Agent | Model | Blocking | Purpose |
| ---------------------- | ----- | -------- | ------------------------------------------------------------------------------ |
| build-implementer | opus | yes | Autonomous implementation from spec, codes until verify.sh passes |
| resolve-fixer | opus | yes | Autonomous bug fix, codes until QA flows pass |
| code-reviewer | opus | yes | Security, types, bugs, AC gaps (diff-only scope, confidence-based auto-fix) |
| code-simplifier | opus | no | Clarity, DRY (rule-of-3 + knowledge-vs-char), patterns (NÃO-TOCAR error paths) |
| test-fixer | opus | yes | Runs tests, fixes failures, creates missing tests |
| functional-validator | opus | yes | Validates UI with Playwright (auto-triggered on .tsx/.css) |
| terraform-validator | opus | yes | Validates env vars and Terraform consistency |
| memory-sync | opus | no | Syncs knowledge to MCP Memory |
All agents emit a standardized trailing ---AGENT_RESULT--- block consumed by orchestrators (STATUS / ISSUES_FOUND / ISSUES_FIXED / BLOCKING). ISSUES_FIXED only counts when npx tsc --noEmit + npm run test actually verified the fix (fail-safe).
Hooks
| Hook | Event | Purpose |
| --------------------------- | --------------------- | ----------------------------------------------------- |
| build-stop-guard.sh | Stop | Blocks stop while workflow active |
| stop-quality-check.sh | Stop | Blocks stop if code changes have quality issues |
| build-continuity-hook.sh | PostToolUse (Skill) | Injects next Skill() call between phases |
| build-skill-register.sh | PreToolUse (Skill) | Claims session ownership for build/resolve sub-skills |
| pre-commit-gate.sh | PreToolUse (Bash) | Auto-format + type check + tests before git commit |
| build-implement-stop.sh | Stop (agent) | Enforces verify.sh for build-implementer agent |
| build-session-recovery.sh | SessionStart | Detects stalled workflows, offers resume |
| ask-user-empty-guard.sh | PostToolUse (AskUser) | Rejects empty/blank responses |
| permission-denied-log.sh | PermissionDenied | Logs denied tool calls for later review |
| pre-compact-save.sh | PreCompact | Preserves workflow state across auto-compaction |
Philosophy
The configuration enforces autonomous development:
| Principle | Meaning | | ----------------------------------- | ------------------------------------------------------------------- | | FAZER, nao perguntar | Agents fix issues automatically, don't ask for confirmation | | BUSCAR, nao pedir contexto | Use MCP Memory and codebase exploration, don't ask user for context | | Codigo sem teste = PR rejeitado | Tests are mandatory (blocking) | | Erros: corrigir e continuar | Fix errors automatically, don't stop workflow |
After Installation
1. Create Project CLAUDE.md (Optional but Recommended)
Create a CLAUDE.md in your project root with project-specific info:
# Project Name
## Commands
- `npm run dev` - Start dev server
- `npm run build` - Build
- `npm run test` - Run tests
## Structure
- `src/` - Source code
- `tests/` - Tests
## MCP Memory Namespace
Prefix: `myproject:`2. Add Custom Skills (Optional)
Create .claude/commands/your-skill.md for project-specific workflows.
Workflow Examples
Solution Design (/deliberate)
User: "/deliberate como resolver o problema de cache"
|
Claude triggers /deliberate
|
Move 1: Challenge the frame (hidden assumptions + REDIRECT gate for trivial/bug)
Move 2: Simulate 5+ scenarios as temporal narratives (Dia 1 -> Mes 6)
Move 3: Pre-mortem + collaborative refinement (max 3 rounds)
|
Saves deliberation with /build command readyFeature Development (/build)
User: "adiciona filtro de data na listagem"
|
Claude automatically triggers /build
|
build-understand -> Interview + spec + V4+ approval gate (plan files skip interview)
build-implement -> Autonomous implementation + verify.sh (V1-V3) + V4+ if present
build-certify -> Quality agents (reviewer-first in COMPLEX) + commit + deploy + prod V4+
|
DoneBug Resolution (/resolve)
User: "erro ao salvar formulario"
|
Claude automatically triggers /resolve
|
resolve-investigate -> Diagnosis + QA reproduction flows (REDIRECTs if feature request)
resolve-verify -> User reviews diagnosis + approves QA flows
resolve-fix -> Autonomous fix + regression test + local QA verification
resolve-certify -> Quality agents (simplifier-first in COMPLEX) + deploy + production QA
|
Done (trivial bugs skip directly from investigate)Customizing for Your Project
The certify skills automatically discover deploy and auth configuration from your project's CLAUDE.md. Add a ## Deploy section to enable production verification:
## Deploy
### Commands
- Backend: `bash scripts/deploy.sh`
- Verify: `bash scripts/verify.sh`
### Production Auth
- API: `X-API-Key` header with API_KEY from .env
- Browser: use `e2eLogin()` helper for browser tests
### Production Logs
- `bash scripts/logs.sh`Without this section, certify runs quality agents and commits but skips deploy and production verification.
Requirements
- Claude Code CLI (Opus 4.7 recommended; prompts are tuned for 4.7 literal-interpretation behaviour)
- MCP Memory server (optional, for knowledge persistence)
- Playwright MCP (optional, for functional validation)
- Sequential Thinking MCP (optional, for /deliberate)
- Context7 MCP (optional, for library documentation)
Development
Releasing a New Version
This project uses ~/.claude/ as the source of truth. To publish changes:
npm run releaseThis command will:
- Sync files from
~/.claude/toconfig/(excluding personal files) - Bump the patch version automatically
- Create a git commit and push
- Publish to npm
Files synced:
CLAUDE.md,ARCHITECTURE.mdskills/(build, resolve, deliberate workflows)commands/(gate)agents/(all 8 subagents)hooks/(10 lifecycle hooks)
Files excluded:
- Session data (
.workflow/plans/,.workflow/build/,.workflow/resolve/, etc.) - Audit artefacts (
.workflow/build-audit/,.workflow/resolve-audit/,.workflow/deliberate-audit/,.workflow/quality-audit/) - Personal files not present in source are simply not synced
License
MIT
