UI Design

This skill produces distinctive, production-grade interfaces. It orchestrates a UI/UX-pro approach with deliberate taste: decide the design system first, then write code that expresses it.

Analogy: an architect does not start laying bricks. They draw the blueprint — materials, proportions, palette — and only then build. The design system is the blueprint.

Dependencies

This skill works standalone, but it is significantly stronger when the original design skills are installed. Before generating a design system, check what is available and delegate in this order:

1. ui-ux-pro-max available → invoke it to generate the full design system (palettes, styles, typography). It has the richest design database.
2. taste-skill available → apply it as a style layer on top of the system from step 1 (or on top of the embedded fallback).
3. Neither installed → use the embedded design principles in this skill as the fallback. They are kept below precisely for this case.

Always prefer the originals when present; fall back gracefully and silently when they are not. Never block on a missing dependency.

Workflow

Step 1 — Identify the product type

The product type drives the entire visual language. Classify first: fintech, edtech, e-commerce, SaaS, health, dev tool, social, creative, internal/dashboard, etc. A health app and a crypto exchange should never look the same.

Step 2 — Generate the design system BEFORE writing code

First, resolve the design system per the Dependencies order above:

• If ui-ux-pro-max is installed, let it produce the system, then optionally refine with taste-skill.
• If neither is installed, apply the embedded fallback below.

Embedded fallback — define and state these explicitly:

• Visual style — pick one with intent: glassmorphism, minimalism, brutalism, bento grid, neo-retro, editorial, etc. Justify it against the product type.
• Color palette — primary, secondary, neutrals, and semantic colors (success / warning / error / info). Defined as tokens, not ad-hoc hex.
• Typography — a heading font, a body font, and a mono font (for code/numbers). Avoid defaulting to Inter for everything.
• Spacing and border radius — a consistent scale (e.g. 4/8/12/16/24) and a radius decision (sharp, soft, or pill).
• Dark mode — decide yes or no up front; if yes, define the dark tokens now, not later.

Step 3 — Apply to the user's stack

Default stack: React + Vite + Tailwind + shadcn/ui. Supported alternatives: Next.js, Vue, Svelte, plain HTML + Tailwind. Ask which one if unknown; otherwise use the default and say so.

Step 4 — Tune the three design parameters

Expose and set these 1-10 dials, and let the user adjust:

• DESIGN_VARIANCE (1-10) — from centered, safe layouts (1) to asymmetric, expressive compositions (10).
• MOTION_INTENSITY (1-10) — from simple hover states (1) to scroll-driven and orchestrated animations (10).
• VISUAL_DENSITY (1-10) — from airy, spacious layouts (1) to compact, information-dense dashboards (10).

Dashboard mode: when building a dashboard, admin, or backoffice, bias VISUAL_DENSITY high (7-9), keep DESIGN_VARIANCE moderate (data clarity over expression), and prioritize legible tables, filters, empty/loading/error states, and scannable hierarchy.

Step 5 — Respect the forbidden anti-patterns

Never ship these:

• The AI default look: Inter + purple gradient + heavy rounded cards. It screams "generated." Avoid it.
• Magic colors: no raw hex values scattered in markup. Every color comes from the system tokens.
• Ignored states: never deliver a UI without designing the empty, loading, and error states. They are part of the work, not an afterthought.
• A screen that lies: never render "could not find out" as zero, empty or off. See Honest states below.

Honest states — three answers, not two

Every piece of data on screen is in one of three conditions, and each needs its own rendering:

The third is the one that gets dropped: a failed request becomes an empty list, and the interface states something false with full confidence — "0 of 5 online", "no team members", "nothing was changed". In one production app this pattern was fixed eight separate times before it became a rule.

Apply it to writes too:

• Confirm only what was confirmed. "Invitation sent" only if the provider said so.
• Show the time of the last successful sync instead of asserting the data is current.
• After a failed write to an external system, say "couldn't confirm", not "nothing changed" — the user will retry.
• Name the specific error for the specific case. "Link unavailable" for a 404 only; anything else is a connection problem.

Some defects only exist in the final artifact, so check the artifact: print styles that produce a blank page, a social image rendered with a fallback font, a font subset that silently falls back. A passing build says nothing about any of them.

Design tokens — structure them in three tiers

Don't scatter raw hex. Use a three-tier token architecture so rebrands and dark mode are one change, not a hundred:

1. Primitive — raw values (blue-500: #3b82f6).
2. Semantic — role aliases (color-primary, color-bg-surface, color-danger). Components reference only these, never primitives.
3. Component — optional per-component (button-bg).

In this stack, expose tokens as CSS custom properties wired into Tailwind v4's @theme block (--color-primary, --spacing-*, --radius-*) so utilities and tokens share one source. Theme (light/dark, multi-brand) by swapping CSS-variable values under [data-theme] / .dark — component classes stay identical. Name tokens by role, not appearance (color-danger, not color-red). Cover color, spacing, typography, radius, shadow, z-index, and motion duration/easing. Only reach for Style Dictionary if you must emit tokens to multiple platforms (web + iOS/Android/email); web-only, the Tailwind @theme path is enough.

Responsive design — mobile-first, always

• Author base styles for small screens; layer up with min-width / container queries. Never desktop-down.
• Prefer container queries (@container) over media queries for reusable components, so a card adapts to its slot, not the viewport.
• Fluid type/space with clamp(min, preferred-vw, max) instead of breakpoint-stepped sizes.
• Touch targets ≥ 44×44px (Apple) / 48×48px (Material), ≥ 8px apart.
• Handle notches with env(safe-area-inset-*) + viewport-fit=cover; pad sticky headers/footers.
• Use intrinsic layout primitives (Grid auto-fit/minmax, Flexbox) over manual breakpoints.

(For deeper accessibility, performance, or installable/offline behavior, hand off to the accessibility, frontend-performance, and pwa skills.)

Output

Produce ready-to-use components, not throwaway prototypes — wired to the design tokens, with all states handled.

Key landing components

When building landing or marketing pages, the standard component set is: hero, navbar, features, pricing, testimonials, CTA, footer. (For full landing structure and copy, the landing-page skill drives the flow and calls this skill for the visual system.)