authoring-hooks

Restate the correction as a rule, pick the primitive (block=True hook for enforcement, gate for stop checks, nudge for advice), then write a .claude/hooks/<slug>.py file with the narrowest condition, a message quoting the correction, and inline tests. Verify with uvx --isolated capt-hook test.

gate and nudge are one-shot advisories that throttle after a few fires, so they never enforce. An always-on guard for safety or correctness must use hook(..., block=True) or block_command, which fires on every matching event.

Amend the existing hook file rather than writing a new one: tighten the condition with structural predicates like Runs or a CommandSchema, add a skip_if carve-out, or demote block to Warn. Always add a regression test asserting the misfiring input now returns Allow().

Every event is already registered by the plugin, so a hook file that raises at import errors on every event and wedges the session. Running uvx --isolated capt-hook test proves the module imports, conditions match, and messages render before dispatch.

A whole style guide should not be hand-written as lint or hook rules. The authoring skill delegates that case to the captain-hook:translating-styleguides skill, which owns rule atomization and the style.py enforcement report.