- 14 slash-commands in .claude/commands/ for /project:* invocation - Model routing: Haiku (mine, evaluate), Sonnet (orchestrate, refine, tests, skeptic, perf, fix, release), Opus (analyze, implement, security, optimize-prompts), Sonnet (pipeline orchestrator) - .claude/rules/global.md — shared coding standards - .claude/logs/efficiency_score.json — agent scoring store - README updated with Claude Code usage section and command table Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
1.2 KiB
1.2 KiB
APAW Global Rules — Claude Code Adaptation
Code Quality
- Write clean, idiomatic code matching project conventions
- No premature optimization — make it work first, then measure
- Handle errors explicitly — no empty catch blocks, no silent failures
- Validate only at system boundaries (user input, external APIs)
- Prefer single-word variable names where context is clear (
pid>processIdentifier) - Early return over nested conditionals
constby default,letonly when mutation is needed
Output Style
- Lead with the result, not the reasoning
- Be terse — omit preamble and filler
- Use file:line references when pointing to specific code
- Use markdown tables for comparisons, checklists for action items
Agent Handoff Protocol
Every agent command ends with one of:
-> NEXT: [command]— pass to next agent-> BLOCKED: [reason]— escalate to user-> DONE— task complete, no further action
Model Selection Rationale
| Model | When to use |
|---|---|
claude-haiku-4-5-20251001 |
Fast scans, scoring, grep-style lookups |
claude-sonnet-4-6 |
Most tasks: review, tests, routing, fixes |
claude-opus-4-6 |
Deep design, complex implementation, security |