dev-hooks

Use when you want hard, independent, adversarial critique of an idea, plan, design, draft, proposal, pitch, or landing page — especially when you suspect the default response is too agreeable or sycophantic and you want real pushback before committing. Triggers on "poke holes in this", "what am I missing", "be brutal", "convince me this is wrong", or any decision that benefits from several expert angles at once.

Use when about to claim something is done, fixed, working, passing, or ready to ship; when a change has only been eyeballed or pattern-matched rather than actually run; or when the user says "but for real", "for real this time", "don't guess", or "did you actually test it". Triggers on premature success claims, unverified fixes, and hand-waving instead of inspecting the real code.

Use before committing to a non-trivial plan, design, architecture, migration, launch, or irreversible decision — especially when momentum or optimism is high and nobody has named what could go wrong. Triggers when you're about to start executing a plan, when stakes are high or the decision is hard to reverse, or when the user asks to stress-test, pressure-test, or sanity-check an approach. Not for generating ideas (that's brainstorming).

This skill should be used when writing or revising web content, product copy, AI-generated responses, docs, or long-form text where clarity, scannability, and comprehension matter.

Use before returning a draft, answer, plan, or code change you're unsure about, or when the user asks how confident you are, how good it is, or to grade/score/critique your own work. Triggers when claims may be overstated, when output quality is uncertain, or when you want to catch weak spots before the user does rather than after.

15 hooks across 3 events