A team's Claude Code results vary, and each person has built private workflows. What spreads the best practice?
Why C is the answer
Shared project skills and a CLAUDE.md, kept in the repository
Skills and CLAUDE.md in the repo travel with the code and go through review, so improvements reach everyone.
In detail
- Skills and CLAUDE.md in the repository travel with the code.
- They go through review, so improvements reach everyone.
- Start with the workflows people already rely on.
Use case
An illustrative scenario, not a real incident.
One engineer has a great test-writing workflow, but nobody else uses it. As a skill in the repository, it reaches the whole team and improves through review.
See it in different ways
mindmap
root((Repository))
CLAUDE.md
Conventions
Skills
Common workflows
Settings
Shared rulesflowchart LR S0["Private workflow"] --> S1["Skill in the repository"] --> S2["Code review"] --> S3["Whole team uses it"]
Key point: Put good workflows in the repository.
Why the other options are wrong
- A. A rule that everyone must use exactly the same prompts by hand
- Manual prompts rely on memory, and they stop people improving them.
- B. A longer onboarding document stored outside of the repository
- A document outside the repository goes stale, and it is not loaded.
- D. A monthly meeting where each developer describes what they do
- Talking about workflows does not make them shared or repeatable.