Agent skill

UI Style Format

by MadAppGang in MadAppGang/claude-code

UI design style file format specification with reference image support.

MITAuto-check passedFrontend & Design

Install UI Style Format

skills CLI
$ npx skills add MadAppGang/claude-code --skill ui-style-format -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install MadAppGang/claude-code ui-style-format --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/MadAppGang/claude-code.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/dev/skills/design/ui-style-format .claude/skills/ui-style-format && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ui-style-format
GitHub stars
285
Token cost
~1.2k tokens
SKILL.md length
401 words
Files
1
Skills in repo
69
Repo updated
First seen
Licence
MIT

At a glance

UI design style file format specification with reference image support.

  • Works in 4 steps: Read .claude/design-style.md with Read… → Split by ## headers → Parse tables using Markdown table regex → …
  • Parsing project design styles
  • SKILL.md covers Overview, File Structure, design-style.md Schema and Reference Images Integration, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

UI Style Format is an agent skill from MadAppGang/claude-code. UI design style file format specification with reference image support. Defines the schema for .claude/design-style.md and .claude/design-references/. Use when creating, validating, or parsing project design styles.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering UI design. The repository describes itself as: claude code plugins marketplace. The licence is MIT.

When your agent uses it

  • Parsing project design styles
  • Tasks that involve UI design

Example prompts

  • “/ui-style-format”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Read .claude/design-style.md with Read tool
  2. Split by ## headers
  3. Parse tables using Markdown table regex
  4. Extract key-value pairs from tables

What it can do on your machine

Read from SKILL.md and the folder at commit 6097ad4. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

UI Style Format loads about 1.2k tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 401 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~58
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from MadAppGang/claude-code at commit 6097ad4, republished under its MIT licence (© MadAppGang). 401 words, ~1,173 tokens.

Download SKILL.mdSave it as .claude/skills/ui-style-format/SKILL.md (or your agent's skills folder).
name
ui-style-format
description
UI design style file format specification with reference image support. Defines the schema for .claude/design-style.md and .claude/design-references/. Use when creating, validating, or parsing project design styles.
version
1.0.0

UI Style Format Specification

Overview

The UI Style system provides a standardized way to define project design preferences that the ui agent uses during design reviews. It supports both text-based style definitions and visual reference images.

File Structure

{project}/
  .claude/
    design-style.md              # Main style configuration
    design-references/           # Visual reference images
      {image}.png                # PNG or JPG screenshots
      MANIFEST.md                # Optional metadata

design-style.md Schema

Required Sections
SectionPurpose
HeaderVersion, dates, base reference
Reference ImagesLinks to visual references (v2.0+)
Brand ColorsColor palette with light/dark modes
TypographyFonts and type scale
SpacingBase unit and scale
Component PatternsButton, input, card styles
Design RulesDO and DON'T guidelines
Optional Sections
SectionPurpose
Reference URLsExternal style guides
Style HistoryChange log
MANIFEST.mdDetailed image descriptions

Reference Images Integration

Storage Location

All reference images MUST be stored in .claude/design-references/.

Supported Formats
FormatExtensionRecommended Use
PNG.pngScreenshots, UI components
JPEG.jpg, .jpegPhotos, complex imagery
WebP.webpModern alternative to PNG/JPEG
Image Table Format

In the style file, reference images are listed in a table:

markdown
## Reference Images

| Image | Description | Captured | Mode |
|-------|-------------|----------|------|
| hero-section.png | Homepage hero | 2026-01-08 | light |
Usage Guidelines Section

Each image should have usage notes:

markdown
### Usage Guidelines

- **hero-section.png**: Reference for hero layout, gradient, CTA placement

Parsing the Style File

Section Extraction
  1. Read .claude/design-style.md with Read tool
  2. Split by ## headers
  3. Parse tables using Markdown table regex
  4. Extract key-value pairs from tables
Reference Image Resolution
Image Name -> .claude/design-references/{image_name}

Example:

hero-section.png -> .claude/design-references/hero-section.png
Validation Checklist

Before using a style file, validate:

  1. File exists at .claude/design-style.md
  2. Required sections present
  3. Referenced images exist in .claude/design-references/
  4. Colors are valid hex codes
  5. Spacing values are numbers

Integration with ui Agent

Show full SKILL.md (169 more words)Show less
Style-Aware Review Flow

When the ui agent performs a review:

  1. Load Style: Read .claude/design-style.md
  2. Load References: List .claude/design-references/
  3. Match Components: Find relevant reference images for review target
  4. Comparative Analysis: Pass reference image + target to Gemini
  5. Validate Tokens: Check colors, typography, spacing against style
Gemini Prompt with References
Compare this implementation screenshot against the project design reference.

**Reference Image**: .claude/design-references/hero-section.png
**Implementation**: screenshots/current-hero.png

**Style Tokens** (from .claude/design-style.md):
- Primary Color: #2563EB
- Font: Inter 16px
- Spacing: 4px base

**Validate**:
1. Layout matches reference
2. Colors match defined palette
3. Typography follows scale
4. Spacing uses defined tokens

Version Compatibility

VersionFeatures
1.xText-only style (legacy)
2.xReference images + text style

Version 2.x is backward compatible - the ui agent handles missing ## Reference Images section gracefully.

Best Practices

Capturing Reference Images
  1. Consistent viewport: Use same browser width (e.g., 1440px)
  2. Clean state: No modals, tooltips unless intentional
  3. Both modes: Capture light and dark variants
  4. Component isolation: Crop to relevant area
Writing Usage Guidelines

Be specific about what each image demonstrates:

Good: "Reference for button padding (12px), border-radius (8px), and hover state" Bad: "Button reference"

Updating Styles

When UI changes:

  1. Capture new screenshot
  2. Replace old image (same name) or add new
  3. Update Reference Images table
  4. Add entry to Style History

© MadAppGang, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/dev/skills/design/ui-style-format of MadAppGang/claude-code.

Open the folder on GitHubat commit 6097ad4

Compare with similar skills

UI Style Format next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

UI Style Format compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
UI Style Format this skillMadAppGang/claude-code285—~1.2kAutomated safety check: PassMIT
UI StylingOhh-889/skyroc79513 repos~2.5kAutomated safety check: PassMIT
LobeHub Interactive Prototypelobehub/lobehub83k—~1.6kAutomated safety check: PassCustom licence
Make Interfaces Feel Bettersamuelclay/NewsBlur7.6k10 repos~1.5kAutomated safety check: PassMIT
UI UX Pro MaxZxBing0066/pixel-converter18113 repos~2.6kAutomated safety check: NotesBSD-2-Clause
Design Dnazanwei/design-dna1.9k1 repos~2.1kAutomated safety check: PassMIT

Similar skills

  • UI Styling

    Ohh-889/skyroc

    Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs.

    795 GitHub starsUsed in 13 repos~2.5k tokens
    Frontend & DesignAuto-check passed
  • Builds single-file interactive HTML prototypes rendered with the real LobeHub UI components and written as production-style React, so they can later be split into files.

    83k GitHub stars~1.6k tokensUpdated today
    Frontend & DesignAuto-check passed
  • Make Interfaces Feel Better

    samuelclay/NewsBlur

    Design engineering principles for making interfaces feel polished.

    7.6k GitHub starsUsed in 10 repos~1.5k tokens
    Frontend & DesignAuto-check passed
  • UI UX Pro Max

    ZxBing0066/pixel-converter

    UI/UX design intelligence with searchable database. An agent skill from ZxBing0066/pixel-converter.

    181 GitHub starsUsed in 13 repos~2.6k tokens
    Frontend & DesignAuto-check: notes
  • Design Dna

    zanwei/design-dna

    Extract, define, and apply design DNA across three dimensions: design system (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL, 3D, particles, shaders, scroll effects…

    1.9k GitHub starsUsed in 1 repo~2.1k tokens
    Frontend & DesignAuto-check passed
  • Figma Design to Code

    warpdotdev/warp

    Turns a Figma frame or component into production code that matches the design, using the Figma MCP server and the project's own design system.

    65k GitHub starsUsed in 4 repos~2.9k tokens
    Frontend & DesignAuto-check passed

More from MadAppGang/claude-code

All 69 skills in this repo
  • Content Brief

    MadAppGang/claude-code

    Content brief template and creation methodology for SEO-optimized content.

    285 GitHub starsUsed in 1 repo~959 tokens
    Auto-check passed
  • Context Detection

    MadAppGang/claude-code

    A skill your agent uses when detecting project technology stack from files/configs/directory structure, auto-loading framework-specific skills, or analyzing multi-stack fullstack projects (e.g…

    285 GitHub stars~5.4k tokensUpdated 6 mo ago
    Auto-check passed
  • Content Optimizer

    MadAppGang/claude-code

    On-page SEO optimization techniques including keyword density, meta tags, heading structure, and readability.

    285 GitHub starsUsed in 1 repo~694 tokens
    Auto-check passed
  • Keyword Cluster Builder

    MadAppGang/claude-code

    Techniques for expanding seed keywords and clustering by topic and intent.

    285 GitHub starsUsed in 1 repo~674 tokens
    Auto-check passed
  • Serp Analysis

    MadAppGang/claude-code

    SERP analysis techniques for intent classification, feature identification, and competitive intelligence.

    285 GitHub starsUsed in 1 repo~1k tokens
    Auto-check passed
  • Agent Coordination Discipline

    MadAppGang/claude-code

    A skill your agent uses when deciding whether to launch an agent, selecting which agent to use, or coordinating multiple agents.

    285 GitHub stars~3.8k tokensUpdated 6 mo ago
    Auto-check passed

Questions about UI Style Format

What does UI Style Format do?

UI design style file format specification with reference image support. UI Style Format is an agent skill from MadAppGang/claude-code. UI design style file format specification with reference image support.

When should I use UI Style Format?

UI Style Format fits situations like: parsing project design styles; tasks that involve UI design.

How do I install UI Style Format in Claude Code?

Run `npx skills add MadAppGang/claude-code --skill ui-style-format -a claude-code`. Or copy the skill folder (plugins/dev/skills/design/ui-style-format in MadAppGang/claude-code) into .claude/skills/ui-style-format in your project. Claude Code loads it when a task matches its description.

How do I install UI Style Format in Codex?

Run `npx skills add MadAppGang/claude-code --skill ui-style-format -a codex`. Or copy the skill folder (plugins/dev/skills/design/ui-style-format in MadAppGang/claude-code) into .agents/skills/ui-style-format in your project. Codex loads it when a task matches its description.

Can I use UI Style Format in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add MadAppGang/claude-code --skill ui-style-format -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ui-style-format, .gemini/skills/ui-style-format, .github/skills/ui-style-format and .opencode/skills/ui-style-format in your project.

What does UI Style Format need to run?

SKILL.md names no scripts, command-line tools or credentials: UI Style Format is instructions for the agent only.

Does UI Style Format access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is UI Style Format safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does UI Style Format use?

UI Style Format is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does UI Style Format use?

About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to UI Style Format?

Skills that share tags, products or a category with UI Style Format: UI Styling (Ohh-889/skyroc, 795 stars), LobeHub Interactive Prototype (lobehub/lobehub, 83k stars), Make Interfaces Feel Better (samuelclay/NewsBlur, 7.6k stars) and UI UX Pro Max (ZxBing0066/pixel-converter, 181 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains UI Style Format?

MadAppGang (a GitHub organization) maintains it in MadAppGang/claude-code, which has 285 GitHub stars. The repository holds 69 skills in this directory. The repository was last updated on March 15, 2026.

Source: MadAppGang/claude-code on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.