Claude Code Configuration: Don’t Aim for Perfection Upfront—Grow It With Your Team’s Needs
Claude Code’s setup shouldn’t be a one-time task; instead, it evolves from repeated project friction, using CLAUDE.md for persistent context and Skills...
When teams first adopt Claude Code, a common mistake is trying to configure all extensions—CLAUDE.md, Skills, MCP, subagents, hooks, and plugins—right at the start. The idea that a full setup turns Claude into an instant senior engineer is tempting, but it often slows projects down in practice.
Anthropic positions Claude Code’s extension layer not as a pre-packaged toolkit but as engineering infrastructure that grows gradually through project challenges. Just like traditional teams don’t build full SRE or release platforms upfront (they evolve them from issues), Claude’s setup follows the same logic.
Official guidelines give clear triggers for adding extensions: If Claude makes the same mistake twice (e.g., wrong build command), add it to CLAUDE.md. Repeated task prompts become Skills. Frequent cross-system data copying calls for an MCP server. Inefficient symbol navigation needs code intelligence plugins, and so on.
CLAUDE.md is persistent context loaded at each session start. It should only include what Claude needs every time—build commands, coding standards, project structure, or test rules. For an SAP UI5/Fiori project, this could mean UI5 version 1.71, build command "npm run build", OData model naming rules, and formatter logic location. Anthropic recommends keeping it under 200 lines to avoid context bloat.
Skills handle repeatable tasks not needed in every session. Defined in SKILL.md, they’re called on demand (e.g., /release-check). For SAP Fiori, a release check Skill might include unit tests, UI5 build, manifest.json verification, and mock URL checks. Skills only load when used, so no extra context cost.
Effective Claude Code setup isn’t designed—it’s forced by repeated friction. Teams should start simple and iterate based on real needs, ensuring each extension adds value without overcomplicating the system.
Sources
- Original article by Feng Qingyang (Huashan Sword School) on 51CTO Blog: https://blog.51cto.com/abap/14823438