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.
npx claudepluginhub spences10/claude-code-toolkit --plugin claude-workflowThis skill uses the workspace's default tool permissions.
Keep CLAUDE.md files lean, accurate, and useful.
Creates and refactors CLAUDE.md files for Claude Code projects, enforcing best practices for size, structure, memory hierarchy, modular rules, and path-specific loading.
Guides writing effective CLAUDE.md files with best practices on constraints, commands, exclusions, subdirectory rules, and auditing 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.
Share bugs, ideas, or general feedback.
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.