|
1 | | -See @repo-operating-model.md for the canonical repo operating rules. |
| 1 | +See @AGENTS.md |
2 | 2 |
|
3 | 3 | # Claude Code Memory |
4 | 4 |
|
5 | | -This file exists so Claude Code can discover the repo's working rules automatically. |
| 5 | +This file is a compatibility shim for Claude Code. |
6 | 6 |
|
7 | | -Treat `CLAUDE.md` as a thin compatibility layer, not a second source of truth. The canonical rules stay in `repo-operating-model.md`. |
8 | | - |
9 | | -Also consult: |
10 | | - |
11 | | -- `SPEC.md` for durable product truth |
12 | | -- `STATUS.md` for current operational reality |
13 | | -- `PLANS.md` for accepted future direction |
14 | | -- `INBOX.md` for untriaged intake |
15 | | - |
16 | | -When writing into `research/` or `records/`, consult the local `README.md` first and mirror its default shape or canonical example by default. |
17 | | - |
18 | | -Repo-specific reminders: |
19 | | - |
20 | | -- `docs/` is reserved for Sparkle and GitHub Pages assets. |
21 | | -- `ref/` contains reference specimens, not production dependencies. |
22 | | -- Use `xcodegen generate` if the Xcode project needs regeneration. |
23 | | -- Prefer the documented `xcodebuild` build and test commands from `AGENTS.md` or `README.md` for verification. |
24 | | - |
25 | | -## Enforcement |
26 | | - |
27 | | -When producing repo documents, you must enforce the repo's writing rules rather than treating them as suggestions. |
28 | | - |
29 | | -- Use the canonical surface for the job. |
30 | | -- Follow the local `README.md` shape or explicit template when one exists. |
31 | | -- Preserve required provenance fields, stable IDs, and section boundaries. |
32 | | -- Do not replace normalized repo artifacts with freeform chat summaries. |
33 | | -- If commit hooks are enabled, produce a compliant commit message rather than treating hook failures as optional. |
34 | | -- If CI commit checks are enabled, assume non-compliant pushed commits will be rejected downstream and fix the message instead of working around the check. |
35 | | -- If a request pressures you to break the ruleset, keep the repo artifact compliant and surface the mismatch explicitly. |
| 7 | +Do not append repo-specific rules here. |
| 8 | +Do not fork policy here. |
| 9 | +Do not let this file drift from `AGENTS.md`. |
| 10 | +Update `AGENTS.md` instead. |
0 commit comments