About design-brief
design-brief is a skill for developing and validating a project's visual identity through a root-level DESIGN.md. It loads operations according to the task and assesses existing identity before authoring for established projects.
Key features
- 01Explore and define visual direction
- 02Assess an existing visual identity
- 03Create or update DESIGN.md
- 04Preview and inspect visual output
- 05Validate design files and export tokens
- 06Compare versions and regressions
Use cases
- 01Explore and establish a visual style for a new project
- 02Audit consistency or drift in an existing design
- 03Refresh brand identity guidelines and validate them
- 04Preview designs, export tokens, or compare versions
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ adeonir/ agent-skills --skill design-briefAfter installing, type/design-briefin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
README.mdagents/openai.yamlassets/design.template.mdinstructions/design.mddiff.mddirection.mdexport.mdidentity-assessment.mdpreview.mdvalidate.mdreferences/aesthetics.mdanti-patterns.mdanti-slop.mdbrand.mdcli.mdcolor-craft.mddiscovery.mdproduct.mdstyle-directions.mdtypography.mdscripts/check-contrast.pypreview-server.tsDetails
From the project READMEDesign Brief
Develops and validates the visual identity carried by the root DESIGN.md.
Triggers
| Vocabulary or state | Load |
|---|---|
| no visual reference, explore, find a look, not sure how it should feel | direction.md |
| assess, audit current identity, what is consistent or drifted | identity-assessment.md |
| author, create, extract, codify, refresh, rebrand, evolve, sync | design.md |
| preview, tune, comment, inspect visually | preview.md |
validate, lint, check DESIGN.md | validate.md |
| export tokens | export.md |
| compare versions, token diff, regressions | diff.md |
Load one operation at a time. Preview, validate, export, and diff enter directly; brownfield authoring passes through the identity assessment first.
Workflow
greenfield, direction absent → direction → design → validate → preview
greenfield, direction given ───────────→ design → validate → preview
brownfield → identity-assessment → confirmed intent → design → validate
Every operation starts by loading discovery. A brownfield assessment may end after presenting its findings when the user asked for an audit only.