What problem does it solve? Claude Code hook configurations fail silently when written with the legacy flat schema, wrong event names, or handler types that an event does not support. This Skill designs and repairs hooks so they run deterministically at lifecycle events without relying on the model to remember a rule. ## Core Features & Use Cases - Schema-correct hook design: Emits the nested matcher-entry structure (event key → matcher entries → inner hooks array) with current case-sensitive event names and one of the five handler types: command, http, mcp_tool, prompt, or agent. - Policy-aware boundaries: Keeps permission rules as the baseline authority; hooks can tighten with deny decisions but never bypass settings or managed deny rules. - Portability and validation: Uses ${CLAUDE_PROJECT_DIR} and ${CLAUDE_PLUGIN_ROOT} placeholders, documents MCP connection timing, and validates with the bundled policy and validate_hooks.py. - Use Case: Block Write/Edit under a protected client directory with a PreToolUse command hook, guard a slash command with UserPromptExpansion, and send PostToolUse audit events to an MCP server, all in one validated configuration. ## Quick Start Ask the assistant to design a PreToolUse hook that blocks writes to a protected path using the current Claude Code hook schema.
