These files show how a short CLAUDE.md can look for different stacks without turning into a long internal policy document.
Included examples:
frontend/CLAUDE.mdinternal-tooling/CLAUDE.mdnode/CLAUDE.mdpython/CLAUDE.mdgo/CLAUDE.md
Suggested companions:
frontendexample plus.claude/skills/frontend-change-checklist/andposttool-frontend-quality-context.mjsinternal-toolingexample plus.claude/skills/internal-tooling-checklist/andposttool-internal-tooling-context.mjsnodeexample plus.claude/skills/node-change-checklist/andposttool-node-quality-context.mjspythonexample plus.claude/skills/python-change-checklist/andposttool-python-quality-context.mjsgoexample plus.claude/skills/go-change-checklist/andposttool-go-quality-context.mjs
Use them in one of two ways:
Pick the closest file and adapt it into your project root:
cp examples/node/CLAUDE.md /path/to/your-project/CLAUDE.mdThis is usually better when you already have:
- team review rules
- test expectations
- architecture notes
Keep the final file short. The examples are meant to supply stack defaults, not replace project memory.