If you mostly use chat models and you are trying to keep up with new AI tools, this is where you can lose the plot fast. You see Stitch, assume the upgrade is better prompting, and move on. The cost of that bad read is simple: you spend time, budget, and attention polishing prompt wording when the bigger lever sits somewhere else.
The useful shift in google-labs-code / stitch-skills is this: the first file in Stitch is DESIGN.md, because taste gets written there before it gets repeated in prompts. If you just saw the project and were about to scroll past, this is the line worth stopping for. A product update is worth your attention not because of how many features it lists, but because it changes your next decision.
Why does that matter for a beginner? Because chat-model habits teach you to stuff every request with more detail. More colors. More font directions. More theme adjectives. Stitch points the other way. In the public generate-design skill, the workflow is to check whether a design system already exists; if it does, the generation prompt should not keep restating colors, fonts, and theme.
The rest of the public files line up with that same idea. manage-design-system treats DESIGN.md as the shared source of truth. design-md is specifically about extracting a semantic design system from existing screens or code and writing it into DESIGN.md. Three separate skill files land on the same point: the style decision should live once, outside the prompt.
That is the contrarian part. The important asset is not the perfect prompt. The important asset is the reusable style decision sitting outside the prompt. Once the look lives in one place, you stop paying the same attention tax on every new screen.
There is a boundary here. This does not mean every rough sketch needs a fully built design system first. The safer read is narrower: when consistency matters, Stitch wants style rules written once and reused, not retyped screen by screen.
So the next move is practical. If you are only exploring, keep moving fast. If you are trying to make several pages feel like the same product, start with DESIGN.md before you start polishing prompts. Share this with the person who still thinks messy UI is mainly a prompt problem.