Stats
Actions
Tags
From claude-workflow
Guides effective maintenance of CLAUDE.md files: adding lessons learned, updating conventions, restructuring instructions. Covers when to update/remove rules, structure templates, hierarchy, and size limits.
How this skill is triggered — by the user, by Claude, or both
Slash command
/claude-workflow:claude-md-maintenanceThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Keep CLAUDE.md files lean, accurate, and useful.
Keep CLAUDE.md files lean, accurate, and useful.
After mistakes or discoveries:
"Update CLAUDE.md so you don't make that mistake again"
This captures learnings before context resets.
Add rules when:
Remove rules when:
# Project Name
Brief purpose (1-2 lines).
## Key Commands
- `npm test` - run tests
- `npm run build` - production build
## Conventions
- Use X pattern for Y
- Always Z before committing
## Mistakes to Avoid
- Don't assume X (actually Y)
- Remember to check Z first
Two levels, both loaded:
| File | Scope | Use For |
|---|---|---|
~/.claude/CLAUDE.md | All projects | Personal preferences, global patterns |
.claude/CLAUDE.md | This repo | Project conventions, tech stack rules |
Project-level overrides global when conflicting.
Keep under 500 lines. Claude scans on every request.
Too long? Extract to references:
## API Patterns
See [api-patterns.md](docs/api-patterns.md) for details.
npx claudepluginhub spences10/claude-code-toolkit --plugin claude-workflowCreates and refactors CLAUDE.md files following best practices for size, structure, and content organization. Includes memory hierarchy, 3-tier documentation system, and conditional rules.
Provides best practices for creating, updating, and auditing CLAUDE.md files including constraints, commands, architecture overviews, and bloat reduction for projects.
Creates or updates CLAUDE.md following best practices: WHAT/WHY/HOW structure, 30-300 line limits, progressive disclosure with doc references, pointers over copies, verified commands.