From vibe-extras
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.
npx claudepluginhub doodledood/claude-code-plugins --plugin vibe-extrasThis skill uses the workspace's default tool permissions.
Update my CLAUDE.md based on: $ARGUMENTS
Updates, refreshes, optimizes, and cleans up CLAUDE.md by exploring codebase, removing stale content, and restructuring for scannability. Use when docs are out of sync.
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.
Guides writing effective CLAUDE.md files with best practices on constraints, commands, exclusions, subdirectory rules, and auditing for projects.
Share bugs, ideas, or general feedback.
Update my CLAUDE.md based on: $ARGUMENTS
Current CLAUDE.md: @CLAUDE.md
Make targeted updates based on my request. Only explore codebase if essential info is missing.
If my request conflicts with best practices below, still make the update but note the tradeoff.
Best Practices (CLAUDE.md is the highest-leverage config point):
Structure - Cover these if creating/missing critical sections:
Length (LLMs follow ~150 instructions reliably; system uses ~50):
Progressive Disclosure - For complex projects, create separate docs and reference them:
docs/testing.md, docs/architecture.md, docs/conventions.md
Then in CLAUDE.md: "See docs/testing.md for test patterns"
Prefer pointers over copies - Use file:line references instead of pasting code snippets (avoids staleness).
Do: Universal instructions | Imperative language | Verified commands | Reference (don't copy) README
Don't:
Bad: Always use camelCase. Document with JSDoc.
Good: npm test # Required before PR
Verify: <300 lines, no style rules, universal instructions, commands tested.