agentleFS
alebgl77alebgl77/claude-inc/skills/ui-ux-pro-max/SKILL.md

ui-ux-pro-max

Skill21 starsChanged 4 months agoMITView on GitHub

Builds an end-to-end UI system for a product — design tokens (color scale, type scale, spacing, radii, shadows), a component inventory covering every interaction state, a layout grid, and WCAG contrast checks — emitted as CSS variables plus a component spec doc. Use when the user says "set up a design system", "create design tokens", "make my app consistent", "define the visual foundation", or before any build that spans more than one screen.

177 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use stock_analysis, ckm:design-system and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Liang-MHSkill

    stock_analysis

    获取 A 股、基金和港股的实时行情和技术分析数据

    Also in 5 projects that use this

  • klauswgSkill

    ckm:design-system

    Token architecture, component specifications, and slide generation. Three-layer tokens (primitive→semantic→component), CSS variables, spacing/typography scales, component specs, strategic slide creation. Use for design tokens, systematic design, brand-compliant presentations.

    Also in 24 projects that use this

  • seikaikyoSkill

    banner-design

    Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with optional generated or supplied visuals. Actions: design, create, generate banner. Platforms: Facebook, Twitter/X, LinkedIn, YouTube, Instagram, Google Display, website hero, print. Styles: minimalist, gradient, bold typography, photo-based, illustrated, geometric, retro, glassmorphism, 3D, neon, duotone, editorial, collage.

    Also in 38 projects that use this

  • dav-niu474Skill

    aminer-data-search

    使用 AMiner 开放平台 API 进行学术数据查询与分析。当用户需要查询学者信息、论文详情、机构数据、期刊内容或专利信息时使用此 skill。 触发场景:提到 AMiner、学术数据查询、查论文/学者/机构/期刊/专利、学术问答搜索、引用分析、科研机构分析、学者画像、论文引用链、期刊投稿分析等。 支持 6 大组合工作流(学者全景分析、论文深度挖掘、机构研究力分析、期刊论文监控、学术智能问答、专利链分析)以及 28 个独立 API 的直接调用。 即使用户只说"帮我查一下 XXX 学者"或"找找关于 XXX 的论文",也应主动使用此 skill。

    Also in 4 projects that use this

  • dav-niu474Skill

    auto-target-tracker

    自动目标进度追踪器。在对话中检测到目标相关图片(笔记、进度、截图、记录)时,自动调用 VLM 识别关键信息并记录到目标日记。适用于学习管理、健身追踪、工作进度、习惯养成、创作记录等所有目标管理场景。

    Also in 4 projects that use this

  • +7 more from dav-niu474

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 166 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run the contrast pass: Every text/background pair must hit WCAG AA — 4.5:1 body, 3:1 large text and UI borders.

    line 36
  2. Very specific:

    Emit deliverables: Write tokens.css and COMPONENTS.md.

    line 38

“Common” is measured: kept by at least 6 in 10 of the 166 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

UI UX Pro Max — Design Lead

"Full UI/UX system"

When to use

  • A product is about to be built or rebuilt and needs its foundation first — "set up the design system for our app".
  • Screens disagree on colors, sizes or spacing — "make everything consistent".
  • Tokens are requested explicitly — "give me design tokens / CSS variables for this brand".
  • A component library is planned — "spec our buttons, inputs and cards with all their states".
  • Downstream skills (frontend-design, web-artifacts) need a system to consume.

Workflow

  1. Interrogate the product. Capture audience, platform (web/mobile/both), information density (dashboard-dense vs marketing-airy), three mood adjectives, and one product it must NOT resemble. If a BRAND.md exists, inherit its palette and type — never invent parallel ones.
  2. Build the color system. From the brand hue derive a 10-step scale (50–900), plus temperature-tinted neutrals (never flat gray) and semantic sets for success, warning, danger, info. Then map role tokens onto steps: --color-surface, --color-text, --color-accent.
  3. Set the type scale. Two families max (display + text). Pick a modular ratio — 1.2 for dense products, 1.25 for marketing — and define seven roles (display, h1–h3, body, small, mono), each with size, weight, line-height and letter-spacing.
  4. Define space, radius, elevation. Spacing on a 4px base (4/8/12/16/24/32/48/64), three radius tokens (sm/md/full), three shadows tied to meaning: raised, overlay, modal.
  5. Inventory components. List every component the product needs. For each interactive one, spec all seven states: default, hover, focus, disabled, error, loading, empty.
  6. Fix the layout grid. 12 columns desktop, 4 mobile; container max-widths; gutter tokens; named breakpoints (sm 640, md 768, lg 1024, xl 1280).
  7. Run the contrast pass. Every text/background pair must hit WCAG AA — 4.5:1 body, 3:1 large text and UI borders. Repair failures by shifting scale steps, never by one-off hex tweaks.
  8. Emit deliverables. Write tokens.css and COMPONENTS.md. No token may exist in one file and not the other.

Output format

/* tokens.css — generated by ui-ux-pro-max */
:root {
  /* color scale */
  --teal-50: #f0fdfa;  /* ...steps 100-800... */  --teal-900: #134e4a;
  /* color roles — components reference ONLY these */
  --color-surface: var(--gray-50);
  --color-text: var(--gray-900);
  --color-accent: var(--teal-600);
  --color-danger: var(--red-600);
  /* type */
  --font-display: "Fraunces", Georgia, serif;
  --font-text: "Inter", system-ui, sans-serif;
  --text-h1: 600 2.44rem/1.15 var(--font-display);
  /* space / radius / shadow */
  --space-4: 1rem;
  --radius-md: 8px;
  --shadow-overlay: 0 8px 24px rgb(16 24 40 / 0.12);
}
# COMPONENTS.md (excerpt)
## Text input — text | search | password
| State | Spec |
|---|---|
| default | border --gray-300, bg --color-surface, radius --radius-md |
| hover | border --gray-400 |
| focus | 2px ring --teal-400, border --teal-600 |
| disabled | bg --gray-100, text --gray-400, cursor not-allowed |
| error | border --red-600, 13px message in --red-700 below |
| loading | right-slot spinner during async validation |
| empty | placeholder in --gray-500 — a hint, never the label |

Quality bar

  • Every text/background pair passes WCAG AA (4.5:1 body, 3:1 large text and UI borders)
  • Components reference role tokens only — no raw hex, no naked scale steps
  • Every interactive component specs all seven states, including loading and empty
  • Two type families max; every size sits on the declared modular scale
  • All spacing divisible by 4 — zero magic numbers anywhere
  • tokens.css and COMPONENTS.md agree perfectly — no orphan tokens in either direction

Example

Invocation: "Set up the UI system for a B2B analytics dashboard — dense but calm, and it must not look like Linear."

Produces: tokens.css (~70 variables: slate-tinted neutrals, a teal accent scale, 1.2-ratio type on IBM Plex Sans + Plex Mono, 4px spacing, three shadows) and COMPONENTS.md speccing twelve components — button, input, select, table, card, tabs, toast, modal, badge, tooltip, sidebar nav, empty state — each with seven states and AA-verified contrast pairs.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.