agentleFS
HeyvhuangHeyvhuang/ship-faster/skills/tool-ui-ux-pro-max/SKILL.md

tool-ui-ux-pro-max

Skill337 starsChanged 10 months agoMITView on GitHub

Use when you need concrete UI/UX inputs (palette, typography, landing patterns, UX/a11y constraints) to drive design or review. Searchable UI/UX design intelligence (styles, palettes, typography, landing patterns, charts, UX/a11y guidelines + stack best practices) backed by CSV + a Python search script. Triggers: UIUX/uiux, UI/UX, UX design, UI design, design system, design spec, color palette, typography, layout, animation, accessibility/a11y, component styling. Actions: search, recommend, review, improve UI.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use it to quickly retrieve concrete inputs (palette tokens, typography pairings, UX constraints, stack-specific implementation notes) that …

    line 10
  2. Distinctive:

    Ensure Python is available:

    line 17
  3. Distinctive:

    When asked to design / improve UI, do this:

    line 42
  4. Distinctive:

    Search domains (pick 1–3 results per domain, then synthesize):

    line 50
  5. Distinctive:

    Search by stack to ground decisions in implementation constraints:

    line 59

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Tool: UI/UX Pro Max (Searchable Design Intelligence)

This is a lookup tool, not a page generator.

Use it to quickly retrieve concrete inputs (palette tokens, typography pairings, UX constraints, stack-specific implementation notes) that can be synthesized into:

  • design-system.md
  • a UI refactor plan / acceptance criteria
  • review checklists for “looks good but feels broken” issues

Prerequisites

Ensure Python is available:

python3 --version || python --version

Core command

Domain search:

python3 ~/.claude/skills/tool-ui-ux-pro-max/scripts/search.py "<query>" --domain <domain> [-n <max_results>]

Stack search:

python3 ~/.claude/skills/tool-ui-ux-pro-max/scripts/search.py "<query>" --stack <stack> [-n <max_results>]

Available stacks: html-tailwind, react, nextjs, vue, svelte, swiftui, react-native, flutter

Recommended workflow

When asked to design / improve UI, do this:

  1. Identify these inputs:
  • Product type: SaaS / e-commerce / content / tool / dashboard / landing
  • Tone keywords: minimal / premium / playful / warm / corporate / technical / bold
  • Industry: healthcare / fintech / education / consumer / …
  • Stack: React / Next.js / … (default to html-tailwind if unspecified)
  1. Search domains (pick 1–3 results per domain, then synthesize):
  1. product — product type → style direction
  2. style — style details (color/shape/motion/complexity)
  3. typography — heading/body pairing (includes Google Fonts + CSS import)
  4. color — palette tokens (primary/secondary/CTA/background/text/border)
  5. landing — landing structure (section order + CTA placement)
  6. chart — chart recommendations (dashboards)
  7. ux — UX + a11y rules and anti-patterns
  1. Search by stack to ground decisions in implementation constraints:
python3 ~/.claude/skills/tool-ui-ux-pro-max/scripts/search.py "responsive layout" --stack nextjs

Domain reference

DomainUse forExample keywords
productStyle direction by product typesaas, ecommerce, portfolio, healthcare
styleUI style concepts & implementation hintsminimalism, brutalism, glassmorphism
typographyFont pairings + import instructionselegant, playful, professional
colorPalette tokens (Hex)saas, ecommerce, fintech
landingLanding structure & CTA strategyhero, testimonial, pricing
chartChart type selectiontrend, comparison, funnel
uxUX/a11y rules & anti-patternsaccessibility, animation, navigation
promptPrompt / technical keywords(style name)

Example (beauty / wellness landing)

python3 ~/.claude/skills/tool-ui-ux-pro-max/scripts/search.py "beauty spa wellness service" --domain product
python3 ~/.claude/skills/tool-ui-ux-pro-max/scripts/search.py "elegant minimal soft" --domain style
python3 ~/.claude/skills/tool-ui-ux-pro-max/scripts/search.py "elegant luxury" --domain typography
python3 ~/.claude/skills/tool-ui-ux-pro-max/scripts/search.py "beauty spa wellness" --domain color
python3 ~/.claude/skills/tool-ui-ux-pro-max/scripts/search.py "hero-centric social-proof" --domain landing
python3 ~/.claude/skills/tool-ui-ux-pro-max/scripts/search.py "accessibility" --domain ux
python3 ~/.claude/skills/tool-ui-ux-pro-max/scripts/search.py "animation" --domain ux
python3 ~/.claude/skills/tool-ui-ux-pro-max/scripts/search.py "responsive layout" --stack html-tailwind

Then: turn palette + typography + motion constraints + component rules into design-system.md, and convert the checklist below into acceptance criteria.

Common professional UI rules (quick scan)

Icons & visuals

RuleDoDon’t
No emoji iconsUse a consistent SVG icon set (Heroicons/Lucide/Simple Icons)Mix emoji/icons randomly
Stable hover statesUse color/opacity/shadow transitionsUse transforms that cause layout shift
Correct brand logosUse official SVG sourcesGuess logos or use inconsistent variants
Consistent sizingNormalize icon sizing (e.g., 24×24)Mix different viewBox/sizes

Interaction

RuleDoDon’t
Pointer cursorAdd cursor-pointer to clickable surfacesLeave clickable surfaces without affordance
Clear feedbackChange border/shadow/color on hoverMake hover states indistinguishable
Reasonable transitions150–300ms, consistentInstant changes or sluggish >500ms

Layout

RuleDoDon’t
Spacing from edgesLeave room for floating navsStick UI to viewport edges
Avoid hidden contentAccount for fixed headersLet content sit behind fixed bars
Consistent containersKeep one container width systemUse multiple container widths randomly

Pre-delivery checklist (use as acceptance criteria)

Visual quality

  • No emoji used as UI icons
  • Icons are from a consistent icon set
  • Brand logos are correct (not guessed)
  • Hover states do not cause layout shift
  • Color usage follows a token system (avoid scattered raw hex values)

Interaction

  • All clickable surfaces have cursor-pointer
  • Hover/focus states provide clear feedback
  • Transitions are consistent (150–300ms)
  • Keyboard focus is visible

Layout & responsive

  • Works at 320px / 768px / 1024px / 1440px
  • No horizontal scroll on mobile
  • Fixed elements do not cover content

Accessibility (a11y)

  • Images have alt text
  • Form inputs have labels
  • Color is not the only indicator
  • Respects prefers-reduced-motion

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.