stitch-design-taste

To generate a design language prompt for Stitch and avoid generic UI, you encode your visual rules into a DESIGN.md file. This file codifies atmosphere, color palette, typography, motion, and anti-patterns into precise tokens that Stitch consumes to render screens with repeatable visual consistency.

A DESIGN.md file is a machine-readable prompt that controls screen generation by mapping visual language into exact hex values and token definitions. It conforms to an output model detailing sections for color, typography, motion, and anti-patterns, ensuring precision and consistency across generated interfaces.

You create a design system prompt with exact hex values and typography rules by providing a high-level project brief covering atmosphere, color, and motion. The system processes this brief to output a DESIGN.md featuring a single accent color, exact hex values, and scoped token values for repeatable rendering.

Yes, you can use this to enforce cross-product visual consistency and define motion philosophy. The generated DESIGN.md codifies layout principles, component stylings, and motion philosophy into machine-readable tokens, ensuring that multiple products maintain the exact same visual atmosphere and design language.

To generate a DESIGN.md for your design system, you need to provide a project brief describing your desired atmosphere, color palette, typography, and motion. The system requires no additional dependencies, using your brief to produce a ready-to-use file with exact token values and anti-patterns.

Your Stitch UI generation looks ambiguous and lacks visual consistency because it lacks a precise, reusable design language. By encoding your visual rules into a DESIGN.md with exact hex values, typography scopes, and anti-patterns, you provide Stitch with the machine-readable tokens needed to generate precise screens.