Writing Hookify Rules

Hookify rules use markdown frontmatter to define event types, pattern-matching conditions, and guidance messages for Claude interactions. They monitor bash commands, file edits, stops, and prompts to enforce standardized guardrails.

Hookify rules can target bash, file, stop, and prompt events. You specify the event type in the frontmatter to monitor specific Claude interactions and apply pattern-based conditions to trigger guidance messages.

Yes, advanced hookify rule formats support multi-condition rules with various field operators. This allows you to combine multiple pattern-matching conditions to create complex monitoring logic for Claude interactions.

The best way to structure a hookify rule file is using frontmatter-driven templates with required fields like name, enabled, event, pattern, and conditions, followed by a guidance message body in the markdown content below the frontmatter.

No external dependencies are required to deploy local hookify rules. You create markdown files with proper frontmatter fields and guidance messages directly in your project root at .claude/hookify.{name}.local.md to start monitoring Claude events.

Hookify rules may not trigger if frontmatter fields like event type, enabled status, or pattern conditions are incorrectly specified. Verify that your event typing matches prompt events and conditions use valid field operators for pattern-matching.