Tips // Claude in practice

Tips for working better with Claude

One short tip at a time, with an example you can copy. Move through them at random or search for what you need.

Claude CodeIntermediateClaude Code

Teams on Claude Code: a common baseline and one champion per area

If every dev configures Claude Code their own way, the config scatters; start with a shared baseline and enable one champion per team first.

The baseline is a project CLAUDE.md, an agreed set of tools/MCP servers and a permissions posture, all versioned and reviewable. Then enable one champion per area, give them two weeks to turn a real workflow (e.g. code review assistance) into something that works, and have them run a session for their first group of peers. That way the rollout goes out in waves and does not depend on you for every question.

Example
Rollout plan for 4 teams:
1. Repo with CLAUDE.md + permissions + agreed MCP.
2. 1 champion per team, 2 weeks on a real workflow.
3. 45-minute session from the champion with 5 peers.
4. Only then, expand in waves.
#teams#rollout#claude-md#adoption