Hook Rules

Generic, brand-neutral engineering capability; sourced playbooks in references//knowledge/. [DOC]

TL;DR

A hookify rule is a markdown file with YAML frontmatter that watches for a pattern and shows a message when it matches. Rules live at .claude/hookify.{name}.local.md. This is higher-level than a raw settings.json hook — for raw hooks blocks, use hook-creator [EXPLICIT]

When to use

• Use for the hook rules capability. [EXPLICIT]
• NOT for adjacent domains — route to the matching skill. [INFERENCE]

Sub-capabilities (resource map)

Deep, evidence-tagged playbooks — open the one the task needs (ICM Layer 3, on-demand). [INFERENCE]

Procedure

1. Resolve the sub-capability; open the matching references/ playbook. [EXPLICIT]
2. Apply its decision tables; pick the strategy explicitly. [EXPLICIT]
3. Validate against the Quality Criteria and tag every claim. [EXPLICIT]

Quality Criteria

• Sub-capability resolved to one playbook. [INFERENCE]
• Claims evidence-tagged. [EXPLICIT]

Contract

• Aceptación: capability resolved to its reference playbook, applied, validated, evidence-tagged. [EXPLICIT]
• Límites: scoped to this capability; deep procedure in references/. [EXPLICIT]
• Casos borde: ambiguous/insufficient input → request clarification before proceeding. [EXPLICIT]
• Supuestos: access to project artifacts (code, docs, configs). [SUPUESTO]
• Trade-off: depth in references keeps the SKILL.md stage contract lean (ICM). [EXPLICIT]

Packet

Capas del packet, cargables bajo demanda (disciplina ICM: una capa por vez, nunca todas juntas): references/ guías de profundidad (cargar UNA por etapa) · knowledge/ cuerpo de conocimiento · prompts/ prompts listos · examples/ salida de ejemplo · agents/ subagentes del packet · templates/ plantilla de output · scripts/ automatización local · assets/ recursos estáticos.