Consult existing Kauri decisions before planning or implementing changes. Use BEFORE making architectural choices, changing conventions, picking libraries, or modifying files that might be covered by a recorded decision.
Record a project decision using Kauri. Use when you've chosen an architectural pattern, library, convention, boundary, or resolved a trade-off.
Check if recorded Kauri decisions are stale. Use when assessing code changes, reviewing decisions, or when a staleness warning was raised by a hook.
Draft a Kauri decision for human review before recording it. This skill should be used proactively — when the user makes, confirms, or rejects a non-trivial choice (picking a library, rejecting an approach, choosing an architecture, resolving a trade-off, establishing a convention), invoke this skill to draft a decision for their approval. Signals include "let's go with X", "let's use X", "X is better", rejecting an alternative after discussion, or choosing between trade-offs. Do NOT propose for trivial choices, temporary workarounds, or single-line fixes.
Review recent code changes against Kauri decisions. Use after implementing changes, before committing, during PR review, or when asked "does this look right?" to verify consistency with recorded decisions.