writing-hookify-rules

You define custom linting rules for Claude by creating hookify rule files with YAML frontmatter specifying the name, enabled state, event type, and watch patterns. This governs Claude's behavior across bash, file edits, prompts, and stop events.

A hookify rule is a structured markdown file with YAML frontmatter that specifies watch patterns and user-facing messages to govern Claude's behavior. It reduces prompt drift and repetitive governance tasks by enforcing pattern-based interactions.

Yes, hookify rules support regex patterns across bash, file, stop, and prompt events. You can define single-pattern rules directly or use a conditions block to configure multi-condition patterns for complex governance scenarios.

Create a new .claude/hookify.{name}.local.md file in your project root with the required YAML frontmatter fields like name, enabled, event, and pattern. Test the rule by triggering a sample event that matches your specified watch patterns.

Pattern-based hookify rules rely on matching regex patterns for bash, file, prompt, and stop events. Complex governance logic may require multi-condition blocks, and rules must be individually enabled in frontmatter to function within the specified event scope.

Hookify rules support reusable templates for alerting, blocking, or guiding actions across bash, file edits, prompts, and stop events. Optional conditions and actions fields in the frontmatter enable advanced behavior beyond simple pattern matching.