addit-harness

Use when the user makes or records a significant architectural or technical decision — choosing a framework, database, protocol, pattern, or trade-off ("we decided to use X instead of Y because..."), or explicitly asks to write an ADR. Captures the decision as a structured MADR-format Architecture Decision Record in docs/adr/.

Scan the current TS/React project's existing UI layer and write .claude/design-conventions.md — a project-specific visual design convention file that rules/typescript.md loads before UI work. Use when starting UI work in an existing project, when design conventions have drifted, or when --refresh is passed to merge in new patterns.

Scan the current Go repo and write .claude/go-conventions.md — a project-specific convention file that rules/go.md loads on every session instead of re-scanning the codebase from scratch. Use when starting work in a new Go repo, when conventions have drifted, or when --refresh is passed to merge in new patterns.

Use when the user wants to save, export, or persist a plan (or any diagram-rich design doc shown in the CLI) to a markdown file so it can be opened and viewed with rendered mermaid diagrams. The terminal can't render mermaid; this writes the plan to docs/plans/ (or a temp scratch file) for viewing in an IDE preview or on GitHub.

Use once, right after installing the addit-harness Claude Code plugin, to place the parts a plugin can't carry natively (CLAUDE.md, AGENTS.md, path-scoped rules/, references/, settings.json) into ~/.claude or the current project. Also use to re-sync after a plugin update, or to switch between global and project scope.

Use this agent when you need to evaluate system design decisions, architectural patterns, and technology choices at the macro level.

Expert backend architect specializing in scalable API design, microservices architecture, and distributed systems. Masters REST/GraphQL/gRPC APIs, event-driven architectures, service mesh patterns, and modern backend frameworks. Handles service boundary definition, inter-service communication, resilience patterns, and observability. Use for up-front DESIGN of new backend services or APIs (contracts, boundaries, trade-offs) — produces design docs and guidance, not the implementation. To WRITE the code, use backend-developer (or frontend-developer for UI).

Use this agent to IMPLEMENT backend features and fixes in code once the design/approach is clear. A senior backend engineer and software craftsman that writes, structures, tests, and verifies code in Go, Java/Spring, and TypeScript/Bun, following this setup's vendored conventions. Use PROACTIVELY for backend implementation/coding tasks. For up-front architecture/API design use backend-architect; for UI work use frontend-developer; for review use code-reviewer.

Expert cloud architect specializing in AWS/Azure/GCP/OCI/DigitalOcean multi-cloud infrastructure design, advanced IaC (Terraform/OpenTofu/CDK), FinOps cost optimization, and modern architectural patterns. Masters serverless, microservices, Kubernetes, edge/network security (Cloudflare WAF/DDoS/Zero Trust and hyperscaler-native equivalents), cloud security posture (GuardDuty/Security Hub, Defender for Cloud, Security Command Center), compliance, and disaster recovery. Handles both up-front DESIGN of new infrastructure and REVIEW of existing infrastructure (cost, security, reliability audits). Use PROACTIVELY for cloud architecture, cost optimization, migration planning, multi-cloud strategies, or auditing existing infra. To WRITE and VERIFY the actual Terraform/Kubernetes/Docker code, use devops-engineer.

Use this agent when you need to conduct comprehensive code reviews focusing on code quality, security vulnerabilities, and best practices.

Use when the user makes or records a significant architectural or technical decision — choosing a framework, database, protocol, pattern, or trade-off ("we decided to use X instead of Y because..."), or explicitly asks to write an ADR. Captures the decision as a structured MADR-format Architecture Decision Record in docs/adr/.

Scan the current TS/React project's existing UI layer and write .claude/design-conventions.md — a project-specific visual design convention file that rules/typescript.md loads before UI work. Use when starting UI work in an existing project, when design conventions have drifted, or when --refresh is passed to merge in new patterns.

Scan the current Go repo and write .claude/go-conventions.md — a project-specific convention file that rules/go.md loads on every session instead of re-scanning the codebase from scratch. Use when starting work in a new Go repo, when conventions have drifted, or when --refresh is passed to merge in new patterns.

Use when the user wants to save, export, or persist a plan (or any diagram-rich design doc shown in the CLI) to a markdown file so it can be opened and viewed with rendered mermaid diagrams. The terminal can't render mermaid; this writes the plan to docs/plans/ (or a temp scratch file) for viewing in an IDE preview or on GitHub.

Use once, right after installing the addit-harness Claude Code plugin, to place the parts a plugin can't carry natively (CLAUDE.md, AGENTS.md, path-scoped rules/, references/, settings.json) into ~/.claude or the current project. Also use to re-sync after a plugin update, or to switch between global and project scope.

1 hook across 1 event