A standardized Claude Code environment for the team: shared rules, enforced commit gates, wired MCP servers, and a few bespoke skills tuned to their stack, so output is consistent regardless of who is driving.
The team adopted Claude Code independently and each person runs it their own way, so quality swings between people and repos and the tool's leverage is mostly untapped.
Left unaddressed: No shared rules, so conventions drift between repos; No commit gates, so mistakes land before review; Recurring tasks re-explained from scratch every time; New hires rebuild their setup by trial and error.
A standardized Claude Code environment for the team: shared rules, enforced commit gates, wired MCP servers, and a few bespoke skills tuned to their stack, so output is consistent regardless of who is driving.
We'll work in short, transparent iterations, sharing progress regularly and adjusting scope as we learn.
This proposal covers a one-time claude code team setup (config, rules, gates, mcp, custom skills).