claude-multi-agent-architecture: base project settings. Safe-by-default permissions, real executable hooks, no secrets. Per-agent model and tool scoping live in .claude/agents/ .md frontmatter. Personal and machine-specific overrides go in settings.local.json (gitignored). The Stop verification-gate hook is wired.
Design RESTful APIs with consistent conventions for resource URLs, response shapes, HTTP semantics, versioning, and security across every service in the project.
Backend development skill for microservices following Clean Architecture, CQRS with a transactional outbox, the repository/use-case pattern, and a Testing-Trophy strategy.
Switch Claude to telegraphic compressed-prose mode to reduce token usage in long sessions. Drops filler, articles where unambiguous, courtesy words, and meta-commentary. Preserves code, paths, identifiers, negations, numbers exactly. Use when context window pressure matters or the developer asks for terse mode. Do not…
A generator-plus-critic loop that improves output against an explicit rubric before acceptance. Use when you have clear acceptance criteria and iteration measurably helps (specs, prompts, important docs, tricky implementations). Includes a seed eval set for regression-testing prompt and rule changes.
Coordinate complex development tasks using hierarchical agent teams with supervisors, prompt writers, debuggers, and work recorders. Encodes the TDD-with-agents protocol, premature-completion red flags, and cross-agent file-race avoidance.
The Explore to Plan to Code to Commit workflow for any non-trivial change. Forces understanding and an explicit plan before edits, with a one-sentence skip heuristic for trivial work. Use when starting a feature, a refactor, or any change whose steps are not obvious. Pairs with plan mode.
Run the multi-wave Software Engineering Review Board (SERB) over a proposed plan before execution. A read-only board of specialist agents gathers ground truth, critiques from architecture/testing/security/devops/quality lenses, then synthesizes a refined, executable plan with a go/no-go. Use for high-stakes or…
Test-Driven Development workflow for implementing features with tests first; enforces the two-commit audit trail (failing-test commit, then green commit) and shows-your-work verification for agent-driven work.
Transform development sessions into compelling engineering stories that capture not just what happened, but why it mattered and what was learned. Covers journal discipline, session templates (planning, bug hunt, feature build, multi-agent orchestration), and the mandatory end-of-day deliverable summary.
Instructions for mnzralee/claude-multi-agent-architecture, covering quick start (every session), common commands, when rules conflict, multi-agent orchestration and reasoning effort.