writing-rules

## Table of Contents - [Overview](#overview) - [Quick Start](#quick-start) - [Rule File Format](#rule-file-format) - [Frontmatter Fields](#frontmatter-fields) - [Event Types](#event-types) - [Advanced Conditions](#advanced-conditions) - [Operators](#operators) - [Field Reference](#field-reference) - [Pattern Writing](#pattern-writing) - [Regex Basics](#regex-basics) - [Examples](#examples) - [Test Patterns](#test-patterns) - [Example Rules](#example-rules) - [Block Destructive Commands](#block-destructive-commands) - [Warn About Debug Code](#warn-about-debug-code) - [Require Tests](#require-tests) - [Protect Production Files](#protect-production-files) - [Management](#management) - [Related Skills](#related-skills) - [Best Practices](#best-practices) # Hookify Rule Writing Guide ## When To Use - Creating behavioral rules to prevent unwanted actions - Defining persistent guardrails for Claude Code sessions ## When NOT To Use - Complex multi-step workflows - use agents instead - One-time operations that do not need persistent behavioral rules ## Overview Hookify rules are markdown files with YAML frontmatter that define patterns to watch for and messages to show when those patterns match. Rules are stored in `.claude/hookify.{rule-name}.local.md` files. ## Quick Start Create `.claude/hookify.dangerous-rm.local.md`: ```yaml --- name: dangerous-rm enabled: true event: bash pattern: rm\s+-rf action: block --- 🛑 **Dangerous rm command detected!** This command could ...