generate-ui-from-brand

Convert a URL or DESIGN.md into a structured UI specification with design tokens.

Updated May 24, 2026
One-click install
npx skills add https://github.com/yonetim258852/ozgur-os --skill generate-ui-from-brand
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-ui-from-brand
Source: https://github.com/yonetim258852/ozgur-os/tree/main/.claude/skills/generate-ui-from-brand
Command: npx skills add https://github.com/yonetim258852/ozgur-os --skill generate-ui-from-brand

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates turning a live brand URL or a DESIGN.md into a ready-to-implement UI specification, extracting tokens and aligning them into a semantic design system for consistent UI outcomes.

Core Features & Use Cases

  • Extract live design tokens from a URL or DESIGN.md and normalize them into a semantic token system.
  • Output an actionable UI spec with token decisions, UX rules, and component structure.
  • Use for auditing an existing brand design system, refactoring visuals, or aligning cross-product interfaces.

Quick Start

Generate a UI spec by providing the brand URL or DESIGN.md; the pipeline will extract, normalize, and output a ready-to-apply UI spec with tokens and component map.

Frequently Asked Questions about generate-ui-from-brand

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract design tokens from a website URL?

To extract design tokens from a website URL, the pipeline analyzes the live site to pull raw styling values and normalizes them into a semantic token system. It automatically outputs a structured UI specification with color, typography, and spacing mappings.

What is a UI specification generated from a DESIGN.md file?

A UI specification generated from a DESIGN.md is a concrete blueprint containing semantic design tokens, UX rules, and component structures. It translates raw documentation into an actionable design system ready for implementation and visual refactoring.

How do I audit an existing brand design system for UI consistency?

Auditing a brand design system for UI consistency requires extracting live design tokens and validating them against established UX rules. This process normalizes raw values into semantic tokens to align cross-product interfaces and output a concrete UI spec.

Do I need a DESIGN.md file to generate a UI spec, or can I use a live URL?

You do not need a DESIGN.md file exclusively; you can use a live URL to generate a UI spec. The pipeline accepts either input to extract, normalize, and map design tokens into a structured component system.

When do I need to normalize raw design tokens into a semantic system?

You need to normalize raw design tokens into a semantic system during brand refreshes, design audits, or UI refactoring. This ensures consistent visual outcomes by mapping extracted values into a unified design system across products.

What is the best way to align cross-product interfaces during a brand refresh?

The best way to align cross-product interfaces during a brand refresh is generating a concrete UI specification from a URL or DESIGN.md. This normalizes styling into semantic design tokens and applies UX rules for consistent implementation.