dev-conventionslisted

# Dev Conventions — the shelved binder **Why this exists:** these files lived in `~/.claude/rules/common/` and rode every session of every project as always-on context (~2,467 words) — mostly generic convention the model already carries. Relocated here, they cost nothing until a task opens a page. Content is RELOCATED, not deleted — `mv` back to `~/.claude/rules/common/` reverses the move entirely. (Provenance and the evidence trail live in git and the paper-contrast investigation record.) ## When to open which page | Reference | Open when | |---|---| | `references/code-review.md` | running or preparing a code review; severity levels, checklists | | `references/security.md` | auth, user input, queries, secrets, crypto — before writing or reviewing | | `references/testing.md` | choosing test strategy or coverage posture for a project without its own rules | | `references/coding-style.md` | style questions a project's own conventions don't answer (immutability, file size, nesting) | | `references/git-workflow.md` | commit message format, PR workflow, branching questions | | `references/development-workflow.md` | the research-first feature pipeline (gh search → docs → registries) | | `references/agents.md` | delegation/orchestration choices; NOTE: roster is partially stale (tdd-guide, doc-updater, rust-reviewer may not exist) | | `references/patterns.md` | repository pattern / API envelope questions | | `references/hooks.md` | hook-type or auto-accept questions; two operation