The landing page represents all nineteen skills.
Each skill has a named cell, and the page demonstrates the relevant controls and recovery paths without claiming that a marker is model execution.
v0.1 · shippingthe design system is the changelog
What shipped.
A tastecheck sample built as a release log: the same product story, structured as a reverse-chronological feed of what the pack actually changed — most of it in the last two days.
Built by the pack it documents · Works with Claude Code · Codex · Gemini · Cursor · MIT
the log
Every change is a checkable contract.
Newest first. Each entry is a real thing that shipped — not a roadmap, not a promise.
Six samples, six real structures.
The gallery stopped being recolors of one skeleton. Each system leads with substance in a layout native to it: a spec-sheet ledger, a modular grid, a color-block wall, a tessellated bento, soft clusters, and this release log.
The gate auditor became automatable.
It now exposes a structured result a browser-driving runner reads directly — the evidence appears with no manual paste. A pure-Node regression and a real-browser fixture guard the auditor itself.
A runnable ship-gate auditor.
A pasteable console auditor for the cold-load tells a self-reported table misses: hidden defeated by CSS, errors before input, content stuck at opacity zero, the indigo gradient. Plus two rules — budget for the gate from minute one, and reveal-on-scroll must never hide content from a no-JS reader.
The deslop audit grew a structural plane.
The SaaS-skeleton, uniform-grid and metronomic-rhythm checks moved into the runnable self-check, so the structural tells run on every pass — not buried in a reference file the model never opens.
The gate outranks polish.
In budget-limited runs, reserve capacity for the gate before optional extras — and if it genuinely cannot run, say so. Never imply it ran when it did not.
A cross-model audit started all of it.
One brief, seven models. The grep-able surface tells held everywhere; the structural plane is where weaker models leak and their own gates miss it. Every entry above traces back to this run.
what it proves
A green check is necessary. Never sufficient.
This log isn't a feature list — it's the record of a pack being held to its own standard, and sometimes failing it.
- Checks that run, not vibes. Every rule is a value, a count, a yes/no — and the gate auditor's printed output is the evidence, not a claim.
- The structural plane is judgment work. The cross-model run proved smaller models pass the surface and ship the skeleton; so did dogfooding this very pack.
- Taste is the only moat. The same product story, rendered through a committed system, reads as a distinct product — this page included.
install
One command. Then just build.
Links the canonical skills and mirrors them into detected agent homes.
$ git clone https://github.com/KyaniteLabs/tastecheck
$ ./tastecheck/install.sh
$ ./tastecheck/install.sh