ワンクリックでManusで任意のスキルを実行

hook-authoring

スター6

フォーク0

更新日2026年4月27日 01:42

Reference for authoring or debugging Kadmon Harness hook scripts (`.claude/hooks/scripts/*.js`). Covers Plugin-Mode Runtime Resolution (ADR-010 Phase 1) — how lifecycle hooks (session-start, session-end-all, pre-compact-save) resolve `dist/scripts/lib/*.js` via `KADMON_RUNTIME_ROOT` in plugin mode versus the 3-level walk in local-dev mode — and Windows compatibility deep detail (`${HOOK_CMD_PREFIX}`, plugin cache path, hooks.json generator). USE WHEN editing a lifecycle hook (session-start, session-end-all, pre-compact-save). USE WHEN debugging KADMON_RUNTIME_ROOT or dist/ resolution. USE WHEN editing `.claude-plugin/hooks.json`. USE WHEN troubleshooting Windows hook PATH or plugin-cache path issues. USE WHEN modifying `scripts/generate-plugin-hooks.ts` or `ensure-dist.js`. Make sure to load this skill whenever the user mentions hook plugin runtime, plugin mode resolution, lifecycle hook dist resolution, hook command prefix, or Windows hook PATH — even without saying "hook-authoring". Do NOT skip this skill i

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

Kadmon7

Kadmon7/kadmon-harness

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Hook Authoring Reference

Authoritative reference for the runtime resolution and platform-compatibility contract of Kadmon Harness hooks. Content here was previously inlined in .claude/rules/common/hooks.md and moved to on-demand loading 2026-04-26 to reduce auto-load footprint (see plan at ~/.claude/plans/se-puede-algo-entre-sunny-crayon.md).

The full 22-hook catalog and 9 shared-modules table live in .claude/hooks/CATALOG.md (non-auto-loaded, read on-demand per ADR-035). The exit-code table, performance budgets, safety rules, and Windows compatibility short rules remain in .claude/rules/common/hooks.md (auto-loaded). This skill covers only the deep runtime/platform mechanics.

Plugin-Mode Runtime Resolution (ADR-010 Phase 1)

Lifecycle hooks (session-start, session-end-all, pre-compact-save) import from dist/scripts/lib/*.js at runtime.
Local-dev mode: ensure-dist.js#resolveRootDir() walks 3 levels up from import.meta.url to find the repo root.
Plugin mode: .claude-plugin/hooks.json sets KADMON_RUNTIME_ROOT=${CLAUDE_PLUGIN_DATA} via the generated command prefix, so resolveRootDir() points at the plugin cache (~/.claude/plugins/cache/kadmon-harness/...). Required — the plugin cache directory does NOT have a predictable depth, so the relative walk would fail.
MUST leave KADMON_RUNTIME_ROOT unset in local dev — the 3-level walk works from repo layout.
Changing the hook install location (moving dist/ or the canonical root symlinks) requires updating ensure-dist.js#resolveRootDir() and the hooks.json generator in scripts/generate-plugin-hooks.ts.

Windows Compatibility (deep detail)

All 22 registered hooks run via ${HOOK_CMD_PREFIX} in .claude-plugin/hooks.json, which injects the Node.js PATH and KADMON_RUNTIME_ROOT in plugin mode (ADR-010 Phase 1). In local-dev mode the repo-root prefix is resolved via ensure-dist.js#resolveRootDir().

The two short rules that remain in rules/common/hooks.md (KADMON_DISABLED_HOOKS env var support, parseStdin() helper) are mid-task essentials and stay there.

When to consult this skill

Adding a new lifecycle hook (must resolve dist/ correctly in both modes)
Renaming or moving dist/, the canonical root symlinks, or changing the plugin cache layout
Debugging "module not found" errors from a hook in plugin mode but not local-dev mode (or vice versa)
Editing scripts/generate-plugin-hooks.ts (the hooks.json generator) — its output must keep the ${HOOK_CMD_PREFIX} contract intact
Troubleshooting hook execution on Windows where PATH or plugin cache path resolution fails

Source rule file: .claude/rules/common/hooks.md — sections moved here 2026-04-26 to reduce auto-load footprint. See plan at ~/.claude/plans/se-puede-algo-entre-sunny-crayon.md for context.

このリポジトリの他の Skills

同じリポジトリ

kontinuum

Kadmon7/kadmon-harness

Freeze the task list and project state to disk when a session ends, and thaw it back when the next one starts — the cryo-mirror of /kompact. /kompact compacts the context window *within* one session (you stay, its summary lives on in-thread); kontinuum crosses a hard session boundary — a /exit into a brand-new session in a fresh process, where the conversation thread breaks and an on-disk note is the only channel that survives. One trigger, two modes auto-detected by whether SESSION-HANDOFF.md exists at the repo root: FREEZE / SAVE (write the note on the way out, anchored to the exact commit sha) or THAW / RESTORE (git pull --ff-only FIRST, print a drift report of what landed while the session was frozen, reconcile WORK_COORDINATION.md claims when the repo has one, re-pin the OPEN tasks, print the summary, delete the note only once the restore succeeded). Use this skill whenever the user is about to /exit and start a new session, or says "kontinuum", "freeze the session", "congela la sesion antes de salir", "

2026-07-196

sprint

Kadmon7/kadmon-harness

Track lifecycle for multi-developer parallel work coordinated through WORK_COORDINATION.md. Two modes — /sprint claims a track + branches from main against the Next planned table; /sprint close runs the verification gate, opens a PR with a structured body, auto-merges when eligible, then post-merge syncs WORK_COORDINATION and flips the plan-NNN frontmatter status. Use this skill whenever someone says start plan, claim track, open track, ship plan, close plan, ready for PR, post-merge sync, flip track done, sprint close, or partial ship — even when they do not name the skill. First use in a project: instantiate WORK_COORDINATION.template.md (same directory) at the repo root.

2026-07-176

agent-authoring

Kadmon7/kadmon-harness

Reference contract for creating, editing, or reviewing Kadmon Harness agent files (`.claude/agents/*.md`). Covers the mandatory/recommended/optional section taxonomy, the opus-vs-sonnet model decision tree, K-first naming convention, anti-patterns enforced by `/medik` Check

2026-07-166

hebrew-native-copy

Kadmon7/kadmon-harness

Rewrite Hebrew marketing, landing, and UI copy so it reads as native Israeli writing instead of machine-translated Hebrew. Fixes the two things that instantly mark Hebrew copy as translated: gendered second-person address (the default-masculine אתה trap that excludes half your customers) and literal English calques. Produces a native-quality, gender-safe, professional-warm draft. Use this whenever writing, reviewing, localizing, or polishing ANY customer-facing Hebrew — a landing page, hero copy, a marketing site, UI microcopy, a bot or voice persona, ad or WhatsApp copy — and especially when the Hebrew was translated from English/Spanish, when someone says the Hebrew "sounds translated / stiff / generic / off", when it mixes masculine and plural address inconsistently, or when you need Hebrew that works for both male and female readers. Trigger even if the user only says "fix the Hebrew" or "make the Hebrew sound native". It raises the floor to ~native; it does not replace a final native-speaker glance on sh

2026-07-156

copy-deslop

Kadmon7/kadmon-harness

De-slop marketing, UX, and landing copy: strip the "tells" that make prose read as AI-generated (em-dash overuse, "not just X but Y", rule-of-three triads, slop vocabulary like seamlessly / robust / elevate / unlock / delve, hedging, and generic openers) and tighten it to concrete, human, on-brand writing. Use this whenever polishing or reviewing ANY customer-facing prose — landing pages, hero copy, marketing sites, product emails, UX microcopy, app-store descriptions, ad copy, social posts — and especially when the user says "make this sound human", "less AI", "punchier", "tighter", "this feels generic", or "clean up the copy", even if they never say the word "de-slop". Works per-language (English, Spanish, and others). It is a quality-and-voice tool, NOT an AI-detector-evasion tool.

2026-07-156

token-budget-advisor

Kadmon7/kadmon-harness

Offer the user an explicit choice of response depth (25% / 50% / 75% / 100%) before answering, with token estimates based on prompt complexity. Use this skill whenever the user says "token budget", "token count", "response length", "answer depth", "short version", "tldr", "brief answer", "detailed answer", "exhaustive answer", "cuántos tokens", "ahorrar tokens", "respuesta corta", "dame la versión corta", "responde al 50%", or clearly asks to control how much context/response to consume. Do NOT trigger when "token" refers to auth/JWT/payment tokens, when the user has already set a depth this session (maintain it silently), or when the answer is trivially one line.

2026-07-146

name	hook-authoring
description	Reference for authoring or debugging Kadmon Harness hook scripts (`.claude/hooks/scripts/.js`). Covers Plugin-Mode Runtime Resolution (ADR-010 Phase 1) — how lifecycle hooks (session-start, session-end-all, pre-compact-save) resolve `dist/scripts/lib/.js` via `KADMON_RUNTIME_ROOT` in plugin mode versus the 3-level walk in local-dev mode — and Windows compatibility deep detail (`${HOOK_CMD_PREFIX}`, plugin cache path, hooks.json generator). USE WHEN editing a lifecycle hook (session-start, session-end-all, pre-compact-save). USE WHEN debugging KADMON_RUNTIME_ROOT or dist/ resolution. USE WHEN editing `.claude-plugin/hooks.json`. USE WHEN troubleshooting Windows hook PATH or plugin-cache path issues. USE WHEN modifying `scripts/generate-plugin-hooks.ts` or `ensure-dist.js`. Make sure to load this skill whenever the user mentions hook plugin runtime, plugin mode resolution, lifecycle hook dist resolution, hook command prefix, or Windows hook PATH — even without saying "hook-authoring". Do NOT skip this skill if the task touches hook installation location, the plugin cache directory layout, or how hooks find compiled TypeScript at runtime.
requires_tools	[]

Hook Authoring Reference

Plugin-Mode Runtime Resolution (ADR-010 Phase 1)

Lifecycle hooks (session-start, session-end-all, pre-compact-save) import from dist/scripts/lib/*.js at runtime.
Local-dev mode: ensure-dist.js#resolveRootDir() walks 3 levels up from import.meta.url to find the repo root.
Plugin mode: .claude-plugin/hooks.json sets KADMON_RUNTIME_ROOT=${CLAUDE_PLUGIN_DATA} via the generated command prefix, so resolveRootDir() points at the plugin cache (~/.claude/plugins/cache/kadmon-harness/...). Required — the plugin cache directory does NOT have a predictable depth, so the relative walk would fail.
MUST leave KADMON_RUNTIME_ROOT unset in local dev — the 3-level walk works from repo layout.
Changing the hook install location (moving dist/ or the canonical root symlinks) requires updating ensure-dist.js#resolveRootDir() and the hooks.json generator in scripts/generate-plugin-hooks.ts.

Windows Compatibility (deep detail)

All 22 registered hooks run via ${HOOK_CMD_PREFIX} in .claude-plugin/hooks.json, which injects the Node.js PATH and KADMON_RUNTIME_ROOT in plugin mode (ADR-010 Phase 1). In local-dev mode the repo-root prefix is resolved via ensure-dist.js#resolveRootDir().

The two short rules that remain in rules/common/hooks.md (KADMON_DISABLED_HOOKS env var support, parseStdin() helper) are mid-task essentials and stay there.

When to consult this skill

Adding a new lifecycle hook (must resolve dist/ correctly in both modes)
Renaming or moving dist/, the canonical root symlinks, or changing the plugin cache layout
Debugging "module not found" errors from a hook in plugin mode but not local-dev mode (or vice versa)
Editing scripts/generate-plugin-hooks.ts (the hooks.json generator) — its output must keep the ${HOOK_CMD_PREFIX} contract intact
Troubleshooting hook execution on Windows where PATH or plugin cache path resolution fails

Source rule file: .claude/rules/common/hooks.md — sections moved here 2026-04-26 to reduce auto-load footprint. See plan at ~/.claude/plans/se-puede-algo-entre-sunny-crayon.md for context.