Generates a new hook configuration for a Claude Code lifecycle event, with correct JSON schema, handler type, and exit code behavior grounded in the docs corpus.

Hard Rules

<RULES> - **NEVER** create hooks with invalid event names — only events from the 22-event list in hook-events-reference.md are valid - **NEVER** use broad matchers (`"*"`) for blocking hooks — overly broad matchers block too many operations - **NEVER** hardcode secrets in command strings — use environment variables (e.g., `$MY_SECRET`) - **EVERY** hook must use the correct handler type for its purpose: `command` for deterministic checks, `http` for external endpoints, `prompt` or `agent` only when judgment is needed - **EVERY** hook must use a handler type supported by the selected event — verify this against the handler support matrix in `hook-events-reference.md` - **EVERY** `command` hook must document the decision path used by the script: exit `2` + stderr for blocking, or exit `0` with JSON decision output when applicable - **EVERY** hook configuration must produce valid JSON before writing </RULES>

Process

Preflight Check

Check if hooks already exist for the target event in:

Generates a new hook configuration for a Claude Code lifecycle event, with correct JSON schema, handler type, and exit code behavior grounded in the docs corpus.

Hard Rules

Process

Preflight Check

Check if hooks already exist for the target event in:

Create Hook

Hard Rules

Process

Preflight Check

Create Hook

Hard Rules

Process

Preflight Check

Phase 1: Codebase Analysis

Phase 2: Generate Hook

Phase 3: Self-Validation

Phase 4: Present and Write

Notion

Prose

Coding Agent (bash-first)

Continuous Learning

Security Review

Widget Generator