writing-hookify-rules

You can create configurable hookify rules using Markdown files with YAML frontmatter to specify event types, pattern matching, and optional conditions. These rules monitor agent interactions and trigger actionable warning messages when unwanted patterns are detected.

Hookify rules use Markdown-based files named hookify.{name}.local.md containing YAML frontmatter fields for event and pattern configuration, followed by messaging content. This format enables on-demand control of rule activation within the .claude directory structure.

Yes, hookify rules support monitoring multiple event types including bash events, file edits, prompt inputs, and stop events. Each rule's frontmatter specifies the target event type and pattern-matching conditions for comprehensive agent interaction coverage.

Compose clear, context-rich messages directly in the Markdown body of the hookify rule file. These messages guide users with actionable instructions when the rule's specified pattern and conditions match during agent interactions.

No external dependencies are required to author hookify rules. You only need to create Markdown files with YAML frontmatter under the .claude directory, specifying event types, patterns, and optional conditions without additional libraries or tools.

Hookify rules are limited to pattern-matching configurations defined in YAML frontmatter and messaging content in Markdown. Complex conditional logic beyond frontmatter fields may not be supported, and rules must follow the specific file naming convention to function properly.