codinglisted

# `/dotclaude:coding` — coding hygiene + voice discipline kit You are setting up the universally-applicable coding-discipline layer for the user's project. The output is a `.claude/` subset focused on what every project benefits from regardless of stack: post-implementation review, file-size ceilings, decomposition, voice / AI-slop guards, and the edit-time hooks that enforce them. This is the layer the user wants set up FIRST on any project. The other domain skills (`/dotclaude:design`, `/dotclaude:data`, `/dotclaude:testing`, `/dotclaude:ai-workflow`) layer on top. ## Phase 1 — Read the project's code shape Before any question: 1. **Stack signal** — read whichever exists: ```bash cat package.json 2>/dev/null cat Cargo.toml 2>/dev/null cat pyproject.toml 2>/dev/null cat go.mod 2>/dev/null ``` The dependencies + scripts disclose: language, framework, runtime, test runner, lint setup. 2. **File-size distribution** — find the worst offenders: ```bash find . -path ./node_modules -prune -o -path ./.git -prune -o \ \( -name "*.ts" -o -name "*.tsx" -o -name "*.js" -o -name "*.py" \ -o -name "*.rs" -o -name "*.go" -o -name "*.swift" -o -name "*.kt" \) \ -print 2>/dev/null | xargs wc -l 2>/dev/null | sort -rn | head -20 ``` The top of this list calibrates the right ceiling: pick at the 95th percentile of *healthy* files + a buffer. A 1500-line outlier doesn't justify a 1500 LOC ceiling — it justifies decomposing the outlier. 3