hookify-rules

Define hook-based rule patterns with YAML frontmatter in .claude/hookify.* files.

4|7|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/arbisoft/ai-skillforge --skill hookify-rules-arbisoft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hookify-rules
Source: https://github.com/arbisoft/ai-skillforge/tree/main/Claude/skills/hookify-rules
Command: npx skills add https://github.com/arbisoft/ai-skillforge --skill hookify-rules-arbisoft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hookify rules enable defining structured, frontmatter markdown rules that watch for patterns and trigger contextual messages during Claude interactions, helping enforce safety, consistency, and guidance.

Core Features & Use Cases

  • Define .claude/hookify.{rule-name}.local.md rules with YAML frontmatter to specify name, enabled, event, and pattern.
  • Attach actionable messages to pattern matches to guide user behavior and prevent unsafe actions.
  • Use cases include warning on sensitive commands, blocking risky edits, and providing inline prompts for safer alternatives.

Quick Start

Create a new file at .claude/hookify.{descriptive-name}.local.md with a frontmatter specifying name, enabled, event, and pattern, followed by a guidance message.

Frequently Asked Questions about hookify-rules

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define custom rules to enforce guardrails during Claude interactions?

You define custom rules for Claude by creating markdown files with YAML frontmatter that specify a name, enabled status, event, and pattern, which triggers contextual messages when pattern matches occur.

How do YAML frontmatter patterns work for triggering hook-based messages?

YAML frontmatter patterns work by specifying matching criteria in the frontmatter block of a markdown rule file, watching for those patterns during conversation and triggering attached guidance messages when matches are found.

What is the best way to warn users before they execute sensitive commands in Claude?

The best way to warn users about sensitive commands is to define a hook-based rule with a pattern matching those commands, attaching an actionable message that guides the user toward safer alternatives before execution.

Can I block risky file edits using frontmatter rules in Claude?

Yes, you can block risky file edits by creating a local markdown rule file with YAML frontmatter that specifies the edit event and the risky pattern, attaching a message that prevents the unsafe action.

Where should hookify rule files be stored to ensure they are loaded correctly?

Rule files must be stored in the .claude directory using the naming convention hookify.{rule-name}.local.md, ensuring Claude can locate and load the YAML frontmatter configurations during interactions.

Do I need any external dependencies to create and enforce hook-based rules?

No external dependencies are required to create and enforce hook-based rules, as the system relies entirely on local markdown files with YAML frontmatter to define patterns and trigger contextual messages.