writing-hookify-rules

To write Claude Hookify rules, create a markdown file at .claude/hookify.{name}.local.md using YAML frontmatter to define pattern-matching conditions for bash, file, stop, or prompt events, then add a guideline message body for warnings.

Hookify rules are used for AI safety by monitoring user interactions to surface warnings or blocks, preventing credential leakage, enforcing style checks, and guiding safe prompts during tool interactions in Claude workflows.

Set up a simple Hookify rule by creating a new .claude/hookify.{name}.local.md file with proper YAML frontmatter defining the event trigger and a guideline message body, then test it by triggering a sample event.

Yes, you can use pattern matching to block dangerous actions by applying both simple and advanced Hookify rule formats that monitor bash, file, stop, and prompt events, rendering warning messages or blocks when conditions match.

Simple Hookify rules define basic event triggers in frontmatter, while advanced rules support complex conditions for bash, file, stop, and prompt events, enabling predictable, rule-based responses and focused messaging during tool interactions.

Test Hookify rules by triggering a sample event that matches the pattern-matching conditions defined in your .claude/hookify.{name}.local.md file, verifying that the expected warning or block message renders correctly.