API Reference

Complete reference for all commands, hooks, and agent definitions.

/do — Universal Workflow Entry Point

Single command interface for all workflows. Analyzes requirements and orchestrates expert agents through plan-build-improve cycles.

description: Universal entry point - delegates to appropriate workflow
argument-hint: <requirement>
allowed-tools: Read, Glob, Grep, Task, AskUserQuestion, TodoWrite

Domain Discovery

1. Read domains.md — match keywords and paths
2. Read domain-map.conf — match file path globs
3. Scan experts/ directory — check expertise.yaml
4. Fallback: generic build-agent or ask user

Patterns

Error Handling

• Plan fails — report error, exit
• User declines plan — save spec, exit gracefully
• Build fails — preserve spec, report error, skip review
• Review fails — log, skip improve, workflow succeeds
• Improve fails — log, workflow succeeds

Examples

/do "Add user auth endpoint"     # Pattern A
/do "How does caching work?"     # Pattern B
/do "Lint all files"             # Pattern C

/do-teams — Team-Based Parallel Execution

Spawns a team of specialist agents that work in parallel on multi-domain tasks.

description: Team-based parallel execution with agent teams coordination
argument-hint: <requirement>
allowed-tools: Read, Glob, Grep, Task, SendMessage, TeamCreate, TeamDelete, TaskCreate, TaskUpdate, TaskList, AskUserQuestion, TodoWrite

Patterns

Team Lifecycle

1. TeamCreate — establish team
2. TaskCreate — break into tasks with file ownership
3. Spawn teammates (all in one message for parallelism)
4. Monitor and coordinate
5. Shut down specialists
6. Spawn reviewer for cross-validation
7. Acknowledge expertise suggestions
8. TeamDelete + report

File Ownership Rule

Examples

/do-teams "Add auth with API and frontend"  # Implementation
/do-teams "Review security of auth flow"    # Council
/do-teams "Fix all failing tests"           # Parallel testing

/improve — Expertise Improvement Loop

Reviews recent git changes, extracts learnings, updates expertise.yaml files.

description: Review recent work and update domain expertise
argument-hint: [domain|all]
allowed-tools: Read, Glob, Grep, Edit, Bash, Task, TodoWrite

Usage

/improve           # Auto-detect from recent changes
/improve backend   # Only backend domain
/improve all       # All domains

Steps

1. Run git log --oneline -20 --name-only
2. Map changed files to domains via domains.md → domain-map.conf → session-domains.txt → experts/ scan
3. Spawn {domain}-improve-agent per affected domain (parallel)
4. Report updates

/cuite-init — Domain Bootstrapper

Scans your project, detects domains, and generates all configuration files.

description: Scan project and bootstrap domain structure
argument-hint: [--force]
allowed-tools: Read, Glob, Grep, Write, Edit, Bash, AskUserQuestion, TodoWrite

Steps

1. Detect existing setup (domains.md, experts/, domain-map.conf)
2. Scan project — language markers, directory structure, README
3. Propose 3-7 domains with name, description, keywords, paths, language, build/test
4. Generate: domains.md, domain-map.conf, experts/{domain}/ with tips.md + expertise.yaml
5. Update CLAUDE.md project structure table

Detection Patterns

**/Cargo.toml       # Rust
**/package.json     # JavaScript/TypeScript
**/go.mod           # Go
**/requirements.txt # Python
**/Dockerfile*      # DevOps
**/.github/workflows/ # CI/CD
**/helm/            # Kubernetes

/cuite-sync — Framework Sync Checker

Detects drift between the cuite subtree and project configuration.

description: Check and sync cuite framework with project configuration
argument-hint: [--apply]
allowed-tools: Read, Glob, Grep, Bash, Edit, Write, AskUserQuestion, TodoWrite

Checks

Issues Detected

scope-enforcement.sh

When: PreToolUse

Purpose: Enforces project boundaries, gates network egress against whitelist, blocks unsafe remote code execution, triggers supply chain verification for package installs.

Key behaviors:

• Blocks out-of-scope file edits
• Requires download-first for remote code
• Prints SUPPLY_CHAIN_CHECK for new packages

validate-intent.sh

When: PostToolUse

Purpose: Runs syntax checks on edited shell scripts. Logs edits by domain.

detect-injection.sh

When: PostToolUse (after WebFetch)

Purpose: Instructs Claude to review fetched web content for prompt injection. Suspicious domains added to blocked-domains.txt.

track-learnings.sh

When: PostToolUse

Purpose: Tracks which domains are touched during a session. Writes to .claude/.cache/session-domains.txt. Used by /improve for auto-detection.

inject-expertise.sh

When: SubagentStart

Purpose: Injects domain expertise into spawned agents. Matches agent name to domain keyword, injects tips.md first (compact), then expertise.yaml (deep knowledge).

session-context.sh

When: SessionStart

Purpose: Reports available domains, recent activity, and pending blacklist entries for user review.

Core Agents

Template Agents

5 templates at .claude/agents/templates/:

To create domain agents: copy templates to experts/{domain}/, replace {domain} placeholder.

Agent Registry

Format at .claude/agents/agent-registry.json:

• Lists all available agents
• Contains _domainAgentTemplate with {domain} placeholders
• Hooks use this for agent discovery
• Auto-populated by /cuite-init