Claude.md: Repo Patterns
A popular post outlined repo structuring patterns for AI‑assisted coding — 'repo memory', skills/hooks folders, and progressive docs — designed to make AI behave like a senior engineer in your project. The pattern aims to turn ad‑hoc prompts into reproducible, team‑scale automation around code and docs. (x.com)
Public community collections now host ready-made CLAUDE.md templates and skill examples, including the "awesome-claude-md" and "awesome-claude-skills" repositories on GitHub. (github.com) Anthropic’s official docs state CLAUDE.md files are read at the start of every Claude Code session and are complemented by an auto‑memory system, while skills are packaged as SKILL.md inside skills directories that the agent discovers on demand. (code.claude.com) A recurring, battle‑tested repo pattern is a three‑tier layout: a root CLAUDE.md for project‑level rules,.claude/skills/<name>/SKILL.md for task‑specific procedures, and deeper agent guides under docs/ for progressive disclosure; practitioners recommend keeping the root file concise (commonly under 100 lines). (groff.dev) Community and vendor guides explicitly recommend “progressive disclosure” — load only the skill or doc necessary for a task to avoid context bloat — and warn that every extra line in CLAUDE.md consumes tokens and costs money, so linters and external tooling are suggested for style enforcement. (claudecn.com) Claude Code’s GitLab integration can convert issue prompts into ready merge requests and commit AI‑generated changes via CI jobs, enabling the pipeline pattern of prompt → automated MR → human review. (code.claude.com) Production usage shows teams shipping packaged skill sets and automation repos — examples include a 30‑skill.NET plugin and an automation repo for skill lifecycle management — and MCP servers that community posts claim can cut token usage dramatically (one MCP listing advertises a 97% token reduction). (github.com) Operational guidance on scope and secrecy recommends placing team CLAUDE.md at /project/CLAUDE.md and keeping personal overrides in /project/.claude or local config to avoid committing sensitive or noisy instructions to shared git history. (andyjakubowski.com)
