The Deterministic CLAUDE.md Pack [templates and hooks that Claude can't ignore]
A CLAUDE.md is context. It is read on every turn, and it persuades, but it does not guarantee anything. A long enough file buries the rule that matters and the model misses it. You find out in production.A hook is different. It runs on a tool event, and if it blocks, the action does not happen. There is no probability gradient. "Never edit migrations" becomes a guard that actually fires, not a sentence you hope the model reads.This pack is the enforcement half of that idea. It gives you five Claude Code hooks that block the deterministic mistakes: destructive shell commands, writes to protected files, committed secrets, off-format commit messages. Plus three CLAUDE.md templates that keep the prose tight and push those rules into the hooks where they belong.Every hook is tested. The pack ships with the exact test cases used to verify it, and it is tested against a specific Claude Code version (v2.1.159) so you know what it was checked on. The hooks are plain bash with one dependency (jq), they use portable patterns that run on stock macOS as well as Linux, and they are short enough to read in a couple of minutes, which you should, because hooks are code that runs on your machine.It pairs with the free claudemd-audit skill. The free skill tells you which of your CLAUDE.md rules are deterministic-eligible. This pack enforces them. Free finds, paid fixes.Free skill: https://github.com/blacksundev/claudemd-auditWho it is for: Anyone running Claude Code on a real codebase who has watched it do something a CLAUDE.md rule told it not to. Teams who want a guardrail that does not depend on the model reading line 1,400 of an instruction file. People shrinking an oversized CLAUDE.md and moving the deterministic rules out of prose. What you get: Five tested hooks: block-dangerous-commands, protect-paths, scan-secrets, conventional-commits, format-on-save. Three CLAUDE.md templates: Python, Node/TypeScript, and a generic baseline. A settings snippet you paste straight into .claude/settings.json. A README and a one-page START-HERE with a three-step install. A PDF guide that explains the idea, every hook, the install, and two safety warnings worth reading before you trust hooks from anyone. Honest notes:These are guardrails, not a security product. They block the common, costly mistakes. They are not a sandbox and not a malware scanner.The patterns are meant to be edited. The README shows you where.Tested against Claude Code v2.1.159. The mechanics these hooks rely on (exit codes, event matchers) have been stable across 2.1.x, but Claude Code changes often, so always read a hook before you trust it and re-check after a major update.
Get it → blacksundev.gumroad.com