claude-setup CLAUDE.md

Global Claude Code Instructions

You have the Everything Claude Code (ECC) system installed globally. Use it.

Workflow: Always Follow This Order

1. Research First — Search for existing solutions, patterns, and implementations before writing code
2. Plan First — Use /plan or the planner agent for any non-trivial feature
3. TDD — Use /tdd or tdd-guide agent. Write tests first, then implement
4. Perf by Default — Apply production-performance rules as you code (see Rules section). Never write sequential independent queries, N+1 patterns, or uncached stable data
5. Data Quality by Default — Missing values are never rendered as 0. Internal enum keys never reach users. See rules/common/data-quality.md
6. Async State Safety by Default — Mutations fire BEFORE UI transitions. Long-running flows support resume. See rules/common/async-state-safety.md
7. Migration Safety by Default — Pre-migration audit, dedup before unique index, backfill scripts for new denormalized columns. See rules/common/migration-safety.md
8. Code Review — Use /code-review or code-reviewer agent after writing code
9. Content Quality Review — Use content-quality-reviewer agent before any user-facing launch
10. Verify — Use /verify before committing

Production from Day 1

The five rule files below are non-negotiable for any new project. Apply them from the first commit, not as a post-launch cleanup. Each file was extracted from real session learnings where the reverse order cost days of rework.