From dead-rules-audit
Show the CLAUDE.md compliance scorecard — which rules Claude actually follows vs ignores
How this skill is triggered — by the user, by Claude, or both
Slash command
/dead-rules-audit:scorecardThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
!`node "${CLAUDE_SKILL_DIR}/../../dead-rules-audit.js" --render 2>/dev/null || node "${CLAUDE_PLUGIN_ROOT}/dead-rules-audit.js" --render`
!node "${CLAUDE_SKILL_DIR}/../../dead-rules-audit.js" --render 2>/dev/null || node "${CLAUDE_PLUGIN_ROOT}/dead-rules-audit.js" --render
The card above is a worst-first audit of your CLAUDE.md rules, aggregated across
your recent sessions: how often each rule was relevant to an edit, how often it was
violated, its heuristic compliance %, and a ⚠ promote→hook flag for rules Claude
chronically ignores. It is produced by the dead-rules-audit hook, which records
as you work.
Briefly call out the 1–3 worst offenders and, for any rule flagged
promote→hook, suggest making it deterministic — a PreToolUse/PostToolUse hook or
a lint rule — instead of relying on Claude to remember it. Keep it short; do not
re-run any commands.
npx claudepluginhub karanb192/claude-code-hooks --plugin dead-rules-auditGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.