Writing Hookify Rules

To guard prompts, create Hookify rules using YAML frontmatter with required fields: name, enabled, event, and pattern. Store these markdown files in .claude/hookify.{rule-name}.local.md to monitor inputs and display contextual messages when patterns match.

Hookify rules can target Bash, File, Stop, Prompt, or All events. You specify the target event in the YAML frontmatter to trigger contextual markdown messages when matching patterns occur during those specific actions.

Create a Hookify rule with the event set to File, define your API_KEY pattern in the YAML frontmatter, and write a markdown message body with the warning. Save it as .claude/hookify.{rule-name}.local.md to surface guidance during risky edits.

Yes, Hookify supports an advanced format with multi-condition rules. Beyond basic fields, you can use conditions, file_path, new_text, and pattern fields together to precisely match and prevent risky edits before they occur.

Yes, Hookify supports storing rules in project-wide equivalent files alongside .claude/hookify.{rule-name}.local.md files. This allows you to enforce consistent guardrails and prompt safety policies across an entire project.

The minimum required YAML frontmatter fields are name, enabled, event, and pattern. You can then add an optional markdown message body to guide users with actionable feedback when the pattern matches.