UI/UX Pro Max Skill

Why use it

Key features

Typography scales with vertical rhythm
Color systems with semantic tokens, dark mode, accessibility
Spacing scale + grid patterns
Motion guidelines (durations, easings, when to animate)
Platform patterns: web, iOS HIG, Material 3, macOS
Accessibility checklist (WCAG 2.2 AA defaults)

Live Demo

What it looks like in practice

ready

Install

Author repository · Claude Skills documentation

Use Cases

Real-world ways to use UI/UX Pro Max Skill

Fix the 'AI-generated UI' look in an existing app

👤 Devs whose Claude-built UI looks generic ⏱ ~60 min intermediate

When to use: Your shadcn output works but looks off-the-shelf.

Flow

Diagnose

Use UI/UX Pro Max. Audit the design system in /src/ui — type, spacing, color tokens. Score each.✓ Copied

→ Per-axis scorecard with concrete issues
Set tokens

Recommend a 4-step type scale + 4-step spacing scale aligned to 4px grid.✓ Copied

→ Token table
Apply

Update tokens.css and rerun. Diff what changed in the rendered look.✓ Copied

→ Tighter typography, consistent rhythm

Outcome: UI that doesn't scream 'I was made in 5 minutes'.

Pitfalls

Over-tokenizing — every value becomes a variable — Variables for repeated tokens; literals are fine for one-offs

Design a mobile screen that follows iOS HIG

👤 Devs building cross-platform apps ⏱ ~45 min intermediate

When to use: You have an iOS surface and want it to feel native, not cross-platform-soup.

Flow

Spec

Design a settings screen for iOS — group cells, navigation, light/dark, accessibility callouts. Reference HIG.✓ Copied

→ Spec with HIG references
Implement

Translate to SwiftUI. Use system fonts, semantic colors, dynamic type.✓ Copied

→ SwiftUI code that looks system-native

Outcome: Screen passes the 'looks native' eyeball test.

Pitfalls

Hardcoded colors break dark mode — Use system semantic colors; the skill enforces this

Run an accessibility audit on a component

👤 Devs prepping for a11y compliance ⏱ ~30 min intermediate

When to use: You need WCAG 2.2 AA on a critical flow.

Flow

Audit

Audit /components/Form.tsx against WCAG 2.2 AA. Find issues with contrast, labels, focus order.✓ Copied

→ Issue list with severity
Fix

Apply fixes. Verify with screen-reader semantic outline.✓ Copied

→ Issue list shrinks; semantic outline reads cleanly

Outcome: Component that passes auditor + actual user testing.

Pitfalls

Auto-fixes break visual layout — Re-render after each fix; visual regression check

Combine with: filesystem

Combinations

Pair with other MCPs for X10 leverage

ui-ux-pro-max-skill + open-design-skill

Design system + brand-grade reference systems

Use UI/UX Pro Max for fundamentals + open-design for brand styles.✓ Copied

ui-ux-pro-max-skill + filesystem

Apply token changes across the codebase

Update tokens.css and propagate; run audit.✓ Copied

Tools

What this MCP exposes

Tool	Inputs	When to call	Cost
design_audit	scope: directory or component	Initial assessment	tokens
tokens_recommend	constraints (brand, platform)	Setting up a design system	tokens
a11y_check	component path	Compliance pass	tokens

Cost & Limits

What this costs to run

API quota: N/A
Tokens per call: Heavy on first audit; lighter for follow-ups
Monetary: Free
Tip: Audit per-component, not whole app at once

Security

Permissions, secrets, blast radius

Minimum scopes: Read project files

Credential storage: None

Data egress: None

Troubleshooting

Common errors and fixes

Recommendations clash with brand guidelines

Provide brand constraints upfront; skill respects them

Skill triggers too aggressively

Scope by directory or invoke explicitly

Alternatives