Hooks Manager

Configure Claude Code, Codex, and Cursor hooks as event-driven commands or prompts. Use hooks for validation, logging, formatting, notifications, context injection, and bounded completion checks. Treat platform syntax and capabilities as distinct; do not copy a Claude configuration into Codex or Cursor without adapting it.

Quick workflow

1. Identify the target platform and load references/router.md.
2. Load the platform reference: claude-code.md, codex.md, or cursor.md.
3. Identify the scope and file path for that platform.
4. Select a supported lifecycle event and adapt the shared payload/decision contract.
5. Choose a command hook for deterministic shell logic, or a prompt hook when natural-language reasoning is required and the platform supports it.
6. Validate the native config and run the platform-specific smoke check.

Claude-shaped example