agentleFS
Sign inStart free
choupiyangchoupiyang/ZAI_SKILLS/ui-ux-pro-max/SKILL.md

ui-ux-pro-max

Skill13 starsChanged 7 months agoMITView on GitHub

UI/UX design intelligence and implementation guidance for building polished interfaces. Use when the user asks for UI design, UX flows, information architecture, visual style direction, design systems/tokens, component specs, copy/microcopy, accessibility, or to generate/critique/refine frontend UI (HTML/CSS/JS, React, Next.js, Vue, Svelte, Tailwind). Includes workflows for (1) generating new UI layouts and styling, (2) improving existing UI/UX, (3) producing design-system tokens and component guidelines, and (4) turning UX recommendations into concrete code changes.

We split this skill into the rules it gives an agent

10 rules. 0 are common, 7 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 163 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow these steps to deliver high-quality UI/UX output with minimal back-and-forth.

    line 6
  2. Distinctive:

    Ask only what you must to avoid wrong work:

    line 9
  3. Distinctive:

    If the user says "全部都要" (design + UX + code + design system), treat it as four deliverables and ship in that order.

    line 15
  4. Distinctive:

    Always be concrete: name components, states, spacing, typography, and interactions.

    line 18
  5. Very specific:

    Design intelligence data: Read from skills/ui-ux-pro-max/assets/data/ when you need palettes, patterns, or UI/UX heuristics.

    line 28
  6. Very specific:

    Upstream reference: If you need more phrasing/examples, consult skills/ui-ux-pro-max/references/upstream-skill-content.md.

    line 29
  7. Distinctive:

    If you need to quickly generate tokens and page-specific overrides, use the bundled script:

    line 32
  8. Distinctive:

    Prefer running it when the user wants a structured token output (ASCII-friendly).

    line 38
  9. Distinctive:

    Default to ASCII-only tokens/variables unless the project already uses Unicode.

    line 41
  10. Very specific:

    Always cover: empty/loading/error, keyboard navigation, focus states, contrast.

    line 43

“Common” is measured: kept by at least 6 in 10 of the 163 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

Follow these steps to deliver high-quality UI/UX output with minimal back-and-forth.

1) Triage

Ask only what you must to avoid wrong work:

  • Target platform: web / iOS / Android / desktop
  • Stack (if code changes): React/Next/Vue/Svelte, CSS/Tailwind, component library
  • Goal and constraints: conversion, speed, brand vibe, accessibility level (WCAG AA?)
  • What you have: screenshot, Figma, repo, URL, user journey

If the user says "全部都要" (design + UX + code + design system), treat it as four deliverables and ship in that order.

2) Produce Deliverables (pick what fits)

Always be concrete: name components, states, spacing, typography, and interactions.

  • UI concept + layout: Provide a clear visual direction, grid, typography, color system, key screens/sections.
  • UX flow: Map the user journey, critical paths, error/empty/loading states, edge cases.
  • Design system: Tokens (color/typography/spacing/radius/shadow), component rules, accessibility notes.
  • Implementation plan: Exact file-level edits, component breakdown, and acceptance criteria.

3) Use Bundled Assets

This skill bundles data you can cite for inspiration/standards.

  • Design intelligence data: Read from skills/ui-ux-pro-max/assets/data/ when you need palettes, patterns, or UI/UX heuristics.
  • Upstream reference: If you need more phrasing/examples, consult skills/ui-ux-pro-max/references/upstream-skill-content.md.

4) Optional Script (Design System Generator)

If you need to quickly generate tokens and page-specific overrides, use the bundled script:

python3 skills/ui-ux-pro-max/scripts/design_system.py --help

Prefer running it when the user wants a structured token output (ASCII-friendly).

Output Standards

  • Default to ASCII-only tokens/variables unless the project already uses Unicode.
  • Include: spacing scale, type scale, 2-3 font pair options, color tokens, component states.
  • Always cover: empty/loading/error, keyboard navigation, focus states, contrast.

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.

Reviews can't be read right now.

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.

Check your setup, free