One-click install
npx skills add https://github.com/Delqhi-Projects/ZOE-Solar-Accounting-OCR --skill writing-hookify-rules-delqhi-projects
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Writing Hookify Rules
Source: https://github.com/Delqhi-Projects/ZOE-Solar-Accounting-OCR/tree/main/.claude/PLUGINS/marketplaces/claude-code-plugins/plugins/hookify/skills/writing-rules
Command: npx skills add https://github.com/Delqhi-Projects/ZOE-Solar-Accounting-OCR --skill writing-hookify-rules-delqhi-projects

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? Hookify rules enable teams to formalize how Claude responds to prompts by describing trigger patterns, events, and messages in Markdown frontmatter files stored under .claude/.

## Core Features & Use Cases

  • Define rules that watch for specific prompts or edits, specify when to trigger messages, and specify actions like warnings or blocks.
  • Store rules in .claude/hookify.{rule-name}.local.md for project-scoped governance and easy collaboration.
  • Use across development, review, and deployment workflows to enforce consistent prompt hygiene and guidance.

### Quick Start Create a new rule by adding a file named .claude/hookify.{descriptive-name}.local.md with proper frontmatter and a sample message.

Frequently Asked Questions about Writing Hookify Rules

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

FAQPage Schema
How do I create custom markdown rules to trigger warnings for specific Claude prompts?

To create custom markdown rules for Claude prompts, define trigger patterns, events, and messages in Markdown frontmatter. Store these files as .claude/hookify.{rule-name}.local.md to enforce consistent prompt hygiene and guidance across project workflows.

What frontmatter fields are required to define Hookify rules for Claude interactions?

Defining Hookify rules requires frontmatter fields including name, enabled, event, and pattern. Optional conditions can also be specified alongside guidance on message content and formatting to govern how Claude responds to triggers.

Can I use YAML frontmatter in local markdown files to block specific edits during code review?

Yes, you can use YAML frontmatter in local markdown files to specify trigger patterns and events that block specific edits. Store rules in .claude/hookify.{rule-name}.local.md to apply project-scoped governance during development and review workflows.

What is the best way to manage project-scoped prompt governance rules for AI coding assistants?

The best way to manage project-scoped prompt governance is storing rule files under .claude/ as .claude/hookify.{rule-name}.local.md. This approach enables team collaboration and enforces consistent guidance across development, review, and deployment workflows.

Do I need dependencies or external components to start writing Hookify rules?

No dependencies or external components are needed to start writing Hookify rules. You simply create a new markdown file with proper frontmatter and a sample message to define how rules govern Claude interactions through trigger patterns and events.