reviewing-cc-config

# Claude Code Configuration Review Review configuration against context engineering principles derived from Anthropic's "Effective Context Engineering for AI Agents" and "Best Practices for Claude Code." Track these 5 phases. Keep work scoped to ONLY these review targets and keep agent prompts/output compact: 1. Discover and inventory configuration 2. Measure context budget impact 3. Review against rubric (parallel agents) 4. Aggregate and present findings ## Phase 1: Discovery Scan for all Claude Code configuration components. Check BOTH standard layout and plugin layout (cc-thingz style). Findings must cite concrete file paths or configuration locations such as `CLAUDE.md`, `.claude/settings.json`, `.claude/skills/<name>/SKILL.md`, `plugins/<plugin>/skills/<name>/SKILL.md`, `plugins/<plugin>/hooks/<hook>.sh`, or `.claude-plugin/marketplace.json`. ### Standard layout ```bash # Glob these patterns in parallel CLAUDE.md CLAUDE.local.md .claude/CLAUDE.md .claude/settings.json .claude/settings.local.json .claude/skills/*/SKILL.md .claude/agents/*.md .claude/commands/**/*.md # Also check parent dirs (monorepo) and home ~/.claude/CLAUDE.md ../CLAUDE.md ``` ### Plugin layout (if `plugins/` or `.claude-plugin/` exists) ```bash plugins/*/skills/*/SKILL.md plugins/*/agents/**/*.md plugins/*/hooks/*.sh plugins/*/commands/**/*.md .claude-plugin/marketplace.json ``` ### Hooks and MCP servers Extract hook script paths from settings.json `hooks` field. Read each script. Extract ...