Individual skill
generate-ui-from-brand
Pipeline from a URL or DESIGN.md to tokens, decisions and a UI spec. Use when building UI for an existing brand, auditing a design system or fixing visual inconsistency.
skills/generate-ui-from-brand/SKILL.md
Source commit 8f78f13f74a2356326d0c3c21bc63e5624e6a457
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 192
- Repository last updated
- Nov 1, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- accessibility Repository topic
- agent-skills Repository topic
- claude-code-skills Repository topic
- claude-skills Repository topic
- cursor-skills Repository topic
- design-system Repository topic
- design-tokens Repository topic
- enterprise-ux Repository topic
- skills-sh Repository topic
- typography Repository topic
- design Derived category
- design-interface Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# generate-ui-from-brand
**Type:** Pipeline / Orchestrator
**Input:** URL or existing DESIGN.md
**Output:** Actionable UI spec with decisions made
---
## Step 1 — Extract
**If a URL is provided and Dembrandt MCP is available:**
All MCP extraction tools are async — they return a `job_id` immediately. Poll `get_job_status` until `status` is `"completed"`, then read `result`.
