aaraujo666

ClaudeCodeSetup — AI skill for Claude Code

AI community

How a Claude Code setup run like a small engineering team works: hooks, tracker, model routing, memory, MCP servers.

How to install ClaudeCodeSetup

This entry records only its repository, not the path inside it, so there is no exact command to give. Open aaraujo666/ClaudeCodeSetup and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What ClaudeCodeSetup does

How a Claude Code setup run like a small engineering team works: hooks, tracker, model routing, memory, MCP servers.

Alternatives in AI

Ante — Ghost in your shell 1.9k ★
Nocturne Memory — A lightweight, rollbackable, and visual Long-Term Memory Server for MCP Agents 1.3k ★
HarnessKit — More than a skill manager — manage skills, MCP servers, plugins, hooks, CLIs, configs, memory & rules across e 416 ★

README

Claude Code, run like a small engineering team

Most people use Claude Code as a smarter autocomplete: open a session, describe a problem, accept what it does, repeat. That leaves most of the value on the table. This repository documents the setup I use instead. It treats Claude Code as a small engineering team with guardrails: rules are enforced by hooks rather than hoped for in prose, a tracker with a state machine decides what is ready and what is done, the main session orchestrates while cheaper subagents do the work, a cheap decision model handles judgments, memory is a typed and dated knowledge base, and every domain I work in gets its own MCP server with the rules built in.

Author: Anthony Araujo, a programmer of 45 years.

In the 60 days to 2026-10-21 this setup closed 1,160 issues across 15 projects, with about 3,590 hours of estimated skilled-developer effort logged against them. That is an effort estimate, not a stopwatch reading (see [the issue workflow](docs/04-issue-workflow.md) for what the number means). The point is not the number. The point is that I spent that time deciding what was ready, what was done, and which tradeoff to take, and very little of it supervising keystrokes.

The shape of it

flowchart TB
    H["Human: decides what is ready and what is done"]
    subgraph RULES["Layer 1: rules"]
        CM["CLAUDE.md: short, points to detail"]
        HK["Hooks: PreToolUse deny, PostToolUse validate, SessionStart report, Stop nudge"]
    end
    ORCH["Layer 2: orchestrator (main thread, never edits code)"]
    subgraph AGENTS["Layer 3: subagents by model tier"]
        QF["quick-fix, drafter, researcher (cheap tier)"]
        CD["coder, doc-analyst (middle tier)"]
        HP["hard-problem (strongest tier)"]
    end
    JEV["Jev: typed judgments only, never writes"]
    MCP["Layer 4: domain MCP servers with the workflow inside"]
    TRK["Layer 5: tracker, the system of record (status state machine)"]
    MEM["Layer 6: memory (typ