Skill

Stitch Design Taste

leonxlnx

Writes the brief rather than the build: a design document some other generator reads, each rule phrased the way that tool understands while still pinning exact colours, sizes and behaviours. The output is a file that governs screens made later, and it targets Google's screen generator specifically.

A situation it fits

A team generates their screens in Google Stitch. Every batch comes back generic in the same handful of ways, and re-typing the same corrections into the prompt each time has stopped being funny. They want one file in the repo that every future generation is held to, written so the generator itself can act on it.

Stitch Design Taste. The deliverable is a governing document rather than a screen: it writes the brief, phrasing each rule the way that generator reads them while still pinning exact colours, sizes and behaviours, and Google's screen generator is the tool it targets. The most tempting wrong answer is design-consultation, which would propose the design system such a file has to contain - its trap is that it stops at the proposal, and the proposal is not the artefact the generator consumes on every future run. design-review critiques and repairs an interface that exists, and here the screens do not exist yet. design-shotgun hands back several variants to react to, which multiplies the output rather than governing it.

Skills it gets confused with

These share a family with Stitch Design Taste, which is another way of saying they are the ones you might reach for by mistake.

Knowing what Stitch Design Taste does is the easy half. Telling it apart from the others under time pressure is the game.

Today's session

Stitch Design Taste is part of leonxlnx/taste-skill. Licence: MIT. The description above was written for this game, not taken from the skill.