writing-hookify-rules

Markdown rules to monitor Claude interactions are defined by creating local files at .claude/hookify.{name}.local.md with fields like name, enabled, event, pattern, conditions, and messages to guard tool use.

Hookify rules can apply to bash, file, prompt, and stop events during Claude workflows, allowing you to monitor interactions and trigger precise, actionable messages when patterns or conditions are matched.

Multi-condition rules for Claude security patterns are created by adding optional conditions fields alongside pattern and message metadata in your markdown file, enabling complex matching logic for sensitive data or dangerous prompts.

No external dependencies are required to enforce hookify rules across bash and file events; rules are stored as local markdown files and applied automatically during tool use within the Claude environment.

The best way to guide users toward safe prompts is defining declarative markdown rules with frontmatter metadata and precise messages, which automatically warn or block interactions based on matched patterns.

Yes, you can disable a specific hookify rule without deleting the markdown file by setting the enabled field in the rule's frontmatter metadata to false, stopping its application during Claude interactions.