claude-code-guidelisted

# Claude Code Hooks Configure Claude Code's native hook and extension surface without inventing unsupported guarantees or a universal hook format. ## Essentials - **Pin the surface** - Record the documentation snapshot and observed `claude --version` result before selecting a guarantee. - **Map event semantics** - Translate requested behavior through the versioned capability matrix, never by event-name similarity. - **Preserve handler differences** - Command, HTTP, MCP-tool, prompt, and agent handlers have event-specific support and output behavior. - **Assume parallel matching** - Make handlers reentrant and do not expect a denial to cancel sibling side effects. - **Respect settings authority** - Managed, user, project, local, plugin, and component hooks have native precedence and trust rules. - **Onboard transactionally** - Preview exact settings/plugin changes, permissions, data flow, verification, disable, and rollback before apply. - **Keep hooks focused** - Give each handler one native event contract and one explicit responsibility. ## Gotchas - Agent handlers are experimental; do not select them when the requested control requires a verified blocking guarantee. - Exit code `2` is the blocking signal for most blocking events; exit code `1` is normally a non-blocking error. - There is no standalone `.claude/hooks.json`; standalone hooks live under the `hooks` key in a settings file. - All matching handlers run in parallel, so a blocking result does not undo a siblin