From design-docs
Review CLAUDE.md files for quality, efficiency, and structure. Use when auditing LLM context files, checking documentation organization, preparing for context optimization, or ensuring lean imperative instructions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/design-docs:context-reviewThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Reviews CLAUDE.md and child CLAUDE.md files to ensure they provide
Reviews CLAUDE.md and child CLAUDE.md files to ensure they provide efficient, focused context for AI assistants without token waste.
This skill analyzes CLAUDE.md files against quality standards defined in
.claude/design/design.config.json and the LLM Context Agent design document.
It checks line counts, content structure, design doc pointers, and
identifies opportunities for improvement.
Read .claude/design/design.config.json to understand quality standards:
Search for CLAUDE.md files in the repository:
CLAUDE.md or CLAUDE.local.md{module}/CLAUDE.md for each moduleFor each CLAUDE.md file found:
Line Count Check:
Content Structure Check:
Design Doc Pointer Check:
@./.claude/design/module/doc.mdHierarchy Check:
Create a comprehensive review report with:
Summary:
Issues by File:
Group by severity (high, medium, low):
Recommendations:
Actionable suggestions:
Example Issue:
### High Priority
CLAUDE.md: 687 lines (limit: 500, 37% over)
- "Testing" section is very detailed (120 lines) → move to design doc
- "Architecture" duplicates content in pkgs/my-package/CLAUDE.md
- Missing pointer to `.claude/design/my-package/architecture.md`
Recommendation:
1. Create `.claude/design/project/testing-strategy.md` for testing details
2. Add pointer: "For testing details → @./.claude/design/project/testing-strategy.md"
3. Remove architecture duplication, keep only pointer to package CLAUDE.md
Calculate and report:
Generate markdown report with structure:
# CLAUDE.md Review Report
**Date:** YYYY-MM-DD
**Repository:** {name}
**Type:** {monorepo|single-package}
## Summary
- CLAUDE.md files: X
- Average line count: Y
- Files over limit: Z
- Overall efficiency: N%
## Issues Found
### High Priority
[List of high-priority issues with file locations and recommendations]
### Medium Priority
[List of medium-priority issues]
### Low Priority
[List of low-priority issues]
## Recommendations
1. [Specific actionable recommendation]
2. [Specific actionable recommendation]
...
## Quality Metrics
- Efficiency Score: X%
- Pointer Coverage: Y%
- Hierarchy Health: Z%
- Duplication Level: N%
## Next Steps
[Suggested order of operations to address issues]
Monorepo:
Review both root CLAUDE.md and package-level files. Check for appropriate delegation between root and children.
No design docs yet:
If .claude/design/ doesn't exist, note that design documentation system
should be set up first.
CLAUDE.local.md:
These override CLAUDE.md and should follow same standards. Review both if present, noting which takes precedence.
A good review report:
npx claudepluginhub spencerbeggs/bot --plugin design-docsFetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Applies a firm's KYC/AML rules grid to parsed onboarding records: assigns risk rating, checks required documents, outputs rule outcomes with citations, and routes for escalation.
Generates daily or weekly digests of activity from connected sources (chat, email, docs, tasks, CRM), highlighting action items, decisions, mentions, and project updates.