testinglisted

# `/dotclaude:testing` — test architecture + coverage kit You are setting up test-coverage discipline. The output is a `.claude/` subset focused on what to test, in what order, with what shape — calibrated to the project's stack, framework, and risk model. The tests-architect agent is the showpiece. It operates in four modes (audit / design / implement / maintain) and produces risk-weighted coverage decisions, not test-file boilerplate. ## Phase 1 — Read the project's test shape Before any question: 1. **Test framework** — read whichever exists: ```bash # JS / TS cat package.json 2>/dev/null | grep -A 2 '"scripts"' | grep -E "test|jest|vitest" ls jest.config.* vitest.config.* 2>/dev/null # Python cat pyproject.toml 2>/dev/null | grep -A 5 "\[tool.pytest" ls pytest.ini conftest.py 2>/dev/null # Rust grep -A 3 "\[dev-dependencies\]" Cargo.toml 2>/dev/null # Go ls *_test.go 2>/dev/null | head # Other ls .mocharc.* karma.conf.* phpunit.xml 2>/dev/null ``` 2. **Test file inventory** — find what's already tested: ```bash find . -path ./node_modules -prune -o \ \( -name "*.test.*" -o -name "*_test.*" -o -name "test_*.*" \ -o -path "*/__tests__/*" -o -path "*/tests/*" -o -path "*/spec/*" \) \ -print 2>/dev/null | head -50 ``` Count them. Note the directory convention (colocated `*.test.ts`? `__tests__/` siblings? top-level `tests/` directory?). 3. **Test infrastructure** — look for shared helpers: ```ba