Your project CLAUDE.md holds the team's naming conventions plus a 15-step release procedure that is used about twice a month. Developers complain that every session carries the release steps, even for unrelated work. What is the best change?

Answer: A — Move the release procedure into a skill and keep the naming conventions in CLAUDE.md

CLAUDE.md is always loaded, so it should hold universal standards like naming conventions. A task-specific workflow like a release procedure belongs in a skill that loads only when someone invokes it. (B) makes universal standards depend on someone remembering to invoke them. (C) stops the procedure being shared and still loads it in every session for those users. (D) still loads it everywhere.