tasting

Taste your own cooking: the moment you finish making something, check it with the very skills this repo ships before you serve it.

Goal

A reminder buried in docs ("remember to verify") won't reliably fire in a fresh session. tasting makes the recursive self-improvement loop a triggered habit: right after any create or change, run our own skills on the result so quality doesn't ride on the author's biased in-session judgment. It orchestrates; the individual skills do the work.

Workflow

1. Spot the trigger: you just created or changed an artifact or skill and are about to call it done, commit, or hand it off.
2. Cold-read it — run shower on the artifact (fresh-eyes comprehension / handoff check).
3. Check consistency — run ssotchk across the repo for anything the change duplicated or contradicted; ssotize if it found scatter.
4. Tidy — re0 the changed docs so the result reads as a clean v0, not a patch over a draft.
5. Apply the findings here, then serve it.

Rules