skills.rest
AvaTar-ArTs
AvaTar-ArTsCOMMUNITY
Explore all skills by this author →
GitHub

writing-hookify-rules

Create hookify rules in markdown files to trigger contextual guidance on code edits.

Updated May 11, 2026
Search Tags:#automation#markdown#frontmatter#rules#hookify#pattern-matching
One-click install
npx skills add https://github.com/AvaTar-ArTs/my-supremepowers --skill writing-hookify-rules-avatar-arts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-hookify-rules
Source: https://github.com/AvaTar-ArTs/my-supremepowers/tree/main/hookify/2cd88e7947b7/skills/writing-rules
Command: npx skills add https://github.com/AvaTar-ArTs/my-supremepowers --skill writing-hookify-rules-avatar-arts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hookify rules define patterns to watch for and messages to show when those patterns match, enabling automated guidance during code edits. Rules live in .claude/hookify.{rule-name}.local.md.

Core Features & Use Cases

  • Create and manage hookify rules that trigger contextual messages during editor actions.
  • Support single-pattern and multi-condition rules with optional fields like enabled, event, and pattern.
  • Provide a clear message body that guides users on how to fix or proceed when a pattern matches, with examples for common scenarios.

Quick Start

Create a new hookify rule by adding a file named .claude/hookify.{name}.local.md with a frontmatter block and a simple pattern, then tailor the message to your needs.

Frequently Asked Questions about writing-hookify-rules

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

FAQPage Schema
How do I trigger contextual guidance messages when specific patterns match in code edits?▼

Hookify rules trigger contextual guidance by matching patterns during code edits. You define a pattern in the frontmatter of a markdown rule file, and when that pattern matches, a user-facing message body displays instructions on how to proceed or fix issues.

What is the file structure for defining hookify rules in markdown?▼

Hookify rules are stored as markdown files under .claude/hookify.{descriptive-name}.local.md. Each file contains a frontmatter block with fields like name, enabled, event, pattern, and optional conditions, followed by a markdown body delivering the guidance message.

Can I use multiple conditions in a single hookify rule?▼

Yes, hookify rules support multi-condition logic alongside single-pattern matching. You can use the required pattern field and optional conditions in the frontmatter to refine when the rule triggers, ensuring the contextual message only appears for specific code edit scenarios.

How do I enable or disable an automation rule without deleting the file?▼

You can toggle an automation rule by setting the enabled field in the frontmatter block. This boolean field controls whether the hookify rule is active, allowing you to temporarily suspend pattern matching and guidance messages without removing the markdown file.

What events can I target with hookify pattern matching rules?▼

Hookify rules use an event field in the frontmatter to specify the editor action that triggers the pattern matching. By defining the event and pattern, the rule monitors code edits and displays the message body guidance when the specified conditions are met.

Related Skills

Explore More Software Engineering Skills→
angrybeaglesangrybeagles

writing-hookify-rules

Define and manage Hookify rules in .claude/hookify.{name}.local.md files.

Community
Basic
dotnetdotnet
14.8k

make-instructions

Generate .instructions.md files with YAML frontmatter for Copilot in VS Code.

Official
Basic
anthropicsanthropics
33.3k

Writing Hookify Rules

Create Hookify rule definitions with YAML frontmatter and markdown bodies.

Official
Intermediate
TheBushidoCollectiveTheBushidoCollective
187

markdownlint-integration

Automate markdownlint-based quality checks across development workflows.

Official
Intermediate