Convert a documented rule you keep breaking into an immediate personal guard

Confirm a documented rule is actually being violated before authoring a fast, local, personal guard against it -- not the plugin-wide, code-reviewed hook a shipped enforcement policy needs.

Also usesclaude-plugins-official

self-assess-lint-audit is explicitly read-only and never auto-fixes a violation it finds -- that's deliberate, and it leaves a gap for whoever keeps tripping the same rule. hookify fills exactly that gap, but at a different scope and strength than make-strategy-enforced-not-documented: a .claude/*.local.md rule is gitignored, personal, and immediate, and its own dispatcher fails open on error, unlike the fail-closed doctrine a plugin-shipped hook has to meet. Use this recipe for a contributor's own habit; use the cupertino/plugin-dev recipe when the rule needs to hold for everyone who installs the plugin.

Start here

One prompt to start

I keep breaking this documented rule -- confirm it's actually being violated in the code first, not just assumed, and then turn it into a fast, personal hookify guard that warns me the next time I do it, rather than the plugin-wide reviewed hook a shipped policy would need.

Needsself-assess, hookify

Beats

Run these in order. Each prompt is copy-pasteable straight into Claude Code.

1. self-assess:self-assess-lint-auditalso in 1 other recipe

   • Audit a repo against its own documented conventions

   Extracts discrete, checkable rules from CLAUDE.md (falling back from house-rules.md, which this repo doesn't have, and labeling every rule "CLAUDE.md (best-effort)") and dispatches convention-auditor to confirm real violations by reading the code -- never invents a rule the doc doesn't state, and by its own stated scope never auto-fixes what it finds.

   Run this beat on its own

   extract the discrete, checkable rules this repo's CLAUDE.md states, and confirm which ones are actually being violated in the code

2. hookify:hookify

   Turns one confirmed, repeatedly-broken rule into a live regex-pattern guard in `.claude/hookify.<name>.local.md` -- active on the very next tool use, no restart -- the fast personal counterpart to the plugin-wide, reviewed hook `make-strategy-enforced-not-documented` builds.

   Run this beat on its own

   I keep forgetting the rrt-over-raw-git rule -- warn me immediately, right now, the next time I run a bare git commit or push in this repo

Worked example

Grounded in — why this beat order is trustworthy

CLAUDE.md's own rule "Prefer rrt over raw git for repo-level operations" is exactly the shape of rule a contributor could keep forgetting; hookify's own hooks.json wires real `type: "command"` hooks for PreToolUse/PostToolUse/Stop/UserPromptSubmit, but its `pretooluse.py` fails OPEN on any exception ("allow operation and log error"), the opposite of this repo's fail-closed doctrine for shipped enforcement -- so a hookify rule is a fast personal nudge, not a substitute for the fail-closed plugin hook the other recipe produces.

Do / Don't

• ✓Confirm the rule is actually being violated in the code before authoring any guard against it -- never invent a rule the doc doesn't state.
• ✓Use a hookify local guard for a rule you personally keep breaking -- it's live on the very next tool use, no restart.
• ✓Treat the hookify guard as a personal nudge, not a substitute for a fail-closed, plugin-wide hook.

• ×Don't author a personal guard for a rule that hasn't been confirmed as an actual, repeated violation.
• ×Don't treat a hookify rule as equivalent to a shipped enforcement hook -- hookify's own dispatcher fails open on exception, the opposite of this repo's fail-closed doctrine for shipped enforcement.
• ×Don't expect self-assess-lint-audit to auto-fix what it finds -- it's explicitly read-only by its own stated scope.