generate-ui-from-brand

Solid

Pipeline skill — turns a URL or DESIGN.md into a concrete UI structure with decisions already made. Extracts live design tokens, normalizes them into a semantic system, applies UX principles, and outputs an actionable UI spec. Use when building UI for an existing brand from scratch, auditing a design system, or refactoring visual inconsistency.

Web & Frontend 54 stars 9 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 87/100

Stars 20%
58
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# 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`. ``` { job_id } = get_design_tokens({ url }) { result } = get_job_status({ job_id }) // repeat until status === "completed" ``` Run these in sequence (each extraction launches a browser): ``` get_design_tokens, get_color_palette, get_typography, get_component_styles, get_spacing ``` **If Dembrandt MCP is not available, run CLI:** ```bash npx dembrandt <url> --design-md --crawl 3 ``` **If DESIGN.md already exists:** parse it directly — skip extraction. --- ## Step 2 — Normalize Tokens Do not use raw extracted values directly. Map them to a semantic system first. ### Colours Identify the role of each extracted colour: | Role | Token | How to identify | |---|---|---| | `color-primary` | Main brand colour | Used on primary buttons, links, key interactive elements | | `color-secondary` | Supporting brand colour | Used on secondary actions, accents | | `color-surface` | Background | Page or card background | | `color-surface-raised` | Elevated surface | Cards, panels, modals | | `color-border` | Border / divider | Input borders, separators | | `color-text` | Primary text | Body copy | | `color-...

Details

Author
dembrandt
Repository
dembrandt/dembrandt-skills
Created
4 months ago
Last Updated
yesterday
Language
JavaScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Web & Frontend Solid

dembrandt

Orchestrator for the full dembrandt UX pipeline. Routes a UI/UX task through six ordered stages — brand foundation → design tokens → layout → components → UX polish → accessibility gate — loading the right sub-skill at each stage. Use when the task spans multiple design concerns: "design review", "build UI", "audit interface", "from brand to UI". For single-concern tasks (e.g. "review my colour palette") go directly to the relevant sub-skill instead.

54 Updated yesterday
dembrandt
Web & Frontend Listed

designer

Generate a DESIGN.md design system for any project — for people with zero design knowledge. Use when the user starts UI work, says 'design', 'make it look good', 'designer', 'landing page for', 'design system', or mentions components, layouts, colors, fonts, or a site whose look they love.

0 Updated 2 weeks ago
Tariq-himself
Data & Documents Listed

extracting-design-md

Reverse-engineers a DESIGN.md (Google Labs format) from an already-built project — electing tokens from the surfaces the owner designates as reference rather than from whichever value is most frequent, shipping everything unconfirmed as `[provisional]`, and writing decisions per module under a `### Global` tier. Use whenever an existing codebase should adopt DESIGN.md, when UI values have multiplied (several grays, mixed radii, inconsistent buttons), when the owner says the UI looks inconsistent or "quedó desprolijo", when an app has too many surfaces for one flat list of decisions, or to re-audit drift after a migration batch — even if nobody says the word DESIGN.md.

0 Updated 3 weeks ago
bygama