design-brief

Turn a design request into an unambiguous, concrete specification. Vague instructions like "make it professional" or "keep it clean" mean different things to different people, so this workflow forces every request to resolve eight orthogonal dimensions: color palette, accent color, body typography, display typography, layout model, mood, density, and constraints. The dimensions were distilled from analysis of the 71 design systems bundled with Open Design, and mood and density were added specifically because they are the most common sources of ambiguity in natural-language briefs.

Input arrives in one of two forms. A structured I-Lang brief lists dimensions directly, or a natural-language description is converted to that structured form using a phrase-to-dimension mapping table; for example "dark mode" maps to a monochrome dark palette and "lots of whitespace" maps to spacious density. Any dimension the user leaves unspecified is filled with a sensible default.

The vocabulary is deliberately closed: each symbolic value resolves to concrete design tokens, including specific background, surface, text, and accent hex colors, named fonts with weights and sizes, and section-spacing and padding values. If a request uses a value outside the table, such as an unrecognized palette name, the process stops and asks for clarification rather than guessing. The primary output is a DESIGN.md file capturing the resolved specification, alongside a secondary brief-preview.html visual preview. Concerns intentionally excluded from the brief level, such as animation timing, responsive strategy, and accessibility contrast, are enforced downstream by individual template skills, though the generated spec still includes sensible breakpoint defaults for downstream consumption.