County IT wants every teammate to receive the same Claude coding conventions automatically. Where should shared conventions live?
Select an answer to reveal the explanation.
Short Explanation
Shared county conventions belong in project CLAUDE.md in git—clone the repo, get the rules. Not locked on one laptop or whispered in Slack.
Full Explanation
Shared coding conventions that every teammate must receive automatically belong in project-level CLAUDE.md so version control distributes them to all clones. County IT should commit those conventions to the repo rather than trapping them on one laptop or in private channels.
Why the correct option works: project CLAUDE.md is part of the clone. New staff, contractors, and CI-adjacent workflows that load project config see the same rules. That is the distribution mechanism for civic team standards.
Why the other three fail by concept: keeping conventions only in one laptop’s user CLAUDE.md never committed to the repo recreates the missed-standards failure mode. Private Slack DMs that new contractors cannot access are not durable, searchable project config for Claude. Undocumented tribal knowledge during hallway conversations only fails both humans and agents.
Exam caveat: project-level is for shared mandatory conventions; user-level remains fine for personal editor taste. Operational check: commit conventions to project CLAUDE.md, clone on a clean machine as a new teammate would, and confirm the conventions are present without Slack or hallway access. County onboarding time collapses when conventions are cloneable: project CLAUDE.md turns standards into infrastructure instead of lore. After committing, mention the file in the team README so humans and agents both know where mandatory conventions live.