Parse design briefs into DESIGN.md with resolved design tokens.
npx skills add https://github.com/az9713/open-design-tutorial --skill design-brief-az9713
Please help me install this Agent Skill. Skill: design-brief Source: https://github.com/az9713/open-design-tutorial/tree/main/skills/design-brief Command: npx skills add https://github.com/az9713/open-design-tutorial --skill design-brief-az9713
Parse a structured design brief written in I-Lang protocol format into a concrete DESIGN.md. Eliminates ambiguity from vague requests by requiring explicit dimensions and a standardized design token resolution.
Provide a structured design brief in I-Lang or describe it in natural language, and I will generate a DESIGN.md with resolved tokens and a preview.
High-intent search queries and answers about installing and using this skill.
You can turn a design brief into concrete tokens by parsing it into a DESIGN.md file. The skill resolves tokens across 8 dimensions: palette, accent, typography, display, layout, mood, density, and exclusions, validating and defaulting any unspecified values.
Yes, you can generate a design specification from natural language descriptions. The skill parses both natural language and I-Lang structured briefs, applying token resolution rules to output a standardized DESIGN.md file.
To resolve missing dimensions in a design system brief, the skill validates the input and applies default values. It ensures all formatting in the resulting DESIGN.md comes from fully resolved tokens across the 8 specified design dimensions.
I-Lang structured brief parsing supports visual previews by generating a brief-preview.html file. This allows designers to visually verify the resolved tokens before handing off the DESIGN.md specifications to the design team.
The best way to hand off design specs is to generate a ready-to-author DESIGN.md with resolved color, typography, layout, and component guidance. This eliminates ambiguity from vague requests by requiring explicit dimensions and standardized tokens.
A limitation when parsing I-Lang briefs is that formatting strictly depends on resolved tokens; if a dimension is unspecified, it defaults automatically. The output is constrained to the 8 design dimensions defined within the token resolution rules.
jamesrochabrunGenerate Markdown design briefs with defined sections from structured inputs.
markky21Build scalable design systems with Tailwind CSS v4 and design tokens.
anonymouswhite07Generate DESIGN.md specifications for Google Stitch from design taste rules.
Maccio-huangParse I-Lang design briefs into design specifications and HTML previews.
