メニュー
Generate a hook, a handler that runs at a lifecycle event, across the host AI tools. Use when the user wants to create, scaffold, or refactor a hook, or automate an action at a lifecycle point. Not for other artifacts like skills or rules.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Initialize or refresh the project memory bank. Use when the user wants to set up or regenerate the project's memory files. Not for updating one memory file after it exists or editing a single rule directly.
Guide a project's journey through AIDD, from first setup to shipping a feature. Use when the user says onboard me, where do I start, or what to do next. Not for listing every installed surface.
Design and validate a new SaaS's architecture into an INSTALL.md via Q&A and stack comparison. Use when the user starts a project, chooses a stack, or picks an architecture pattern. Not for editing an existing stack or scaffolding code.
Route a request to generate a context artifact (skill, rule, agent, command, or hook) to its generator when the kind is unnamed. A named kind triggers its generator directly. Not for listing existing artifacts.
Generate a router-based skill across the host AI tools a project uses. Use when the user wants to create, scaffold, or refactor a skill, or turn a workflow into one. Not for other artifacts like rules, agents, commands, hooks.
Generate a coding rule that governs editor and agent behavior across the host AI tools. Use when the user wants to write, add, or refactor a rule, convention, or coding standard. Not for other artifacts like skills, agents, or hooks.
| name | 08-hook-generate |
| description | Generate a hook, a handler that runs at a lifecycle event, across the host AI tools. Use when the user wants to create, scaffold, or refactor a hook, or automate an action at a lifecycle point. Not for other artifacts like skills or rules. |
| argument-hint | capture-hook | write-hook | validate |
Builds one hook: an entry merged into the chosen scope for each supported tool, plus the backing script.
| # | Action | Role | Input |
|---|---|---|---|
| 01 | capture-hook | Clarify the moment, action, matcher, scope, tools | user request |
| 02 | write-hook | Merge the entry per tool, write the script | the captured spec |
| 03 | validate | Check the file, the merge, and the moment fit | files written |
Run the actions in order, 01 → 03, and run each action's ## Test before the next.
Before running an action, read its file in actions/, not only the table or assets.
references/hook-authoring.md: the contract (R1-R7), the lifecycle moments, and the handler, matcher, and exit-code model.references/tool-paths.md: per-tool support, moment-to-event names, file formats, scopes, and write targets.assets/hook-template.json: the entry scaffold.assets/hook-script-template.sh: the backing-script scaffold.