Cross-Platform Applicability

• Treat this skill as interface-principle guidance across web, iOS, Android, and desktop surfaces.
• Translate implementation snippets to platform-native primitives; do not copy web syntax literally into native stacks.

Mandatory Invocation

• Invoke this skill first for every UI/visual task.
• Pair with design-audit in the same turn.
• Add design-interaction-motion-craft only when motion, gesture, or transition behavior matters.

Related Skills

• design-audit: mandatory visual/accessibility quality checks
• design-interaction-motion-craft: motion behavior validation
• copywriting: marketing copy generation and rewrite support
• humanizer: remove AI-writing artifacts in UI copy

Integrated Product-Interface Protocol (from former design-interface)

• Default use-case: product interfaces (dashboards, admin tools, settings, operational UIs).
• If task is marketing-first rather than product-interface-first, keep this skill as entrypoint but bias into expressive frontend sections below.
• Before visual execution, make intent explicit:
  • user context (who, immediately previous task, next task)
  • primary verb (what must be completed)
  • experiential target (what this should feel like)
• If these are unknown in a high-risk direction change, ask; do not silently default.

Required pre-direction outputs (all four):

1. Domain: at least 5 domain concepts/metaphors/vocabulary items.
2. Color world: at least 5 colors grounded in the domain.
3. Signature: one structural/visual/interaction element unique to the product.
4. Default replacements: at least 3 common template defaults explicitly replaced.

Direction proposal must explicitly include:

• explored domain concepts
• chosen color world elements
• signature element
• replacements for each default

Suggestion protocol:

• Lead with recommendation and rationale, then request directional confirmation before large implementation divergence.
• Keep reasoning concrete: explain why this hierarchy/layout/material choice supports the primary user verb.

Pre-present checks (mandatory):

• Swap test: replacing fonts/layout with common defaults should materially harm identity.
• Squint test: hierarchy remains readable without harsh visual jumps.
• Signature test: signature is visible in at least 5 concrete UI locations.
• Token test: variable naming reflects product world, not generic naming.
• Purpose-without-name test: if product name is removed, intent should still be inferable from structure and language.

Craft foundations:

• Use subtle layering: surfaces should differ just enough to express hierarchy.
• Keep borders quiet but legible; avoid border-forward composition.
• Pick one depth strategy per screen family (borders-only, subtle shadows, or layered shadows), do not mix arbitrarily.
• Typography is structural; semantics and hierarchy outrank decoration.
• Controls and data require full state coverage: default, hover/focus/active/disabled, plus loading/empty/error/success for data flows.

Integrated Web Execution Guardrails (from former design-taste-frontend)

Use this block when implementing web UI code.

Baseline dials:

• DESIGN_VARIANCE=2
• MOTION_INTENSITY=6
• VISUAL_DENSITY=2

Architecture + dependency rules:

• Verify dependencies in package.json before importing third-party packages.
• Default to React/Next.js server-first composition; isolate interactive leaf components with 'use client'.
• Keep global state for real shared-state needs; use local state by default.
• Tailwind version lock: do not emit v4 syntax into v3 projects.

Layout + responsiveness hard constraints:

• Never use h-screen for full-height hero sections; use min-h-[100dvh].
• Prefer grid for multi-column structures; avoid fragile flex percentage math.
• Use stable container bounds (max-w-7xl or equivalent) and explicit breakpoint behavior.
• High-variance desktop layouts must collapse to strict single-column on small viewports.

Interaction + motion constraints:

• Ship full state cycles: loading, empty, error, success/confirmation.
• Use transform/opacity for animation; avoid layout-property animation.
• Isolate heavy perpetual motion in small client components; avoid parent re-render coupling.
• Use stagger orchestration intentionally; parent/children choreography must share one client tree.
• If MOTION_INTENSITY > 5, prefer Framer motion values over React render-loop state for continuous hover/physics effects.
• Do not mix GSAP/Three and Framer in the same component tree; isolate engine boundaries.

Performance constraints:

• Keep decorative grain/noise off scrolling containers.
• Use strict z-index scales; avoid arbitrary z-index inflation.
• Ensure animation effects degrade safely under reduced-motion preferences.

Anti-generic enforcement (critical examples):

• Avoid AI fingerprint patterns: neon glows, purple/blue default gradient palettes, decorative gradient headline text, repetitive equal-card triplets, templated hero-metric blocks.
• Do not rely on emoji as interface icons.
• Avoid placeholder-data clichés (generic names, synthetic round numbers, fake startup naming).
• If using component libraries, customize tokens/radii/shadows to product identity; never ship untouched defaults.
• Avoid centered-template bias for higher-variance layouts (DESIGN_VARIANCE > 4): prefer split or asymmetric compositions.
• For dense dashboard contexts, avoid unnecessary card boxing; use spacing/dividers when elevation is not semantically needed.

Integrated UI/UX Corpus Workflow (from former design-ui-ux-pro)

Use corpus lookup when requirements are ambiguous, domain-specific, or stack-specific.

Required sequence:

1. Run design-system lookup first:

python3 skills/design/tools/uiux-corpus/scripts/search.py "<product> <industry> <keywords>" --design-system

2. Add domain lookups only as needed:

python3 skills/design/tools/uiux-corpus/scripts/search.py "<keyword>" --domain <domain> [-n <max_results>]

3. Add stack lookup (default html-tailwind):

python3 skills/design/tools/uiux-corpus/scripts/search.py "<keyword>" --stack html-tailwind

Persistence contract (when project doctrine should be retained):

python3 skills/design/tools/uiux-corpus/scripts/search.py "<query>" --design-system --persist -p "Project Name" [--page "dashboard"]

• Writes design-system/MASTER.md and optional design-system/pages/<page>.md.
• Retrieval precedence: page override file > master file.

Domain catalog:

• product, style, typography, color, landing, chart, ux, react, web, prompt

Stack catalog:

• html-tailwind (default), react, nextjs, vue, svelte, swiftui, react-native, flutter, shadcn, jetpack-compose

Priority order for fixes when tradeoffs exist:

1. Accessibility
2. Touch/interaction correctness
3. Performance
4. Layout/responsiveness
5. Typography/color system
6. Animation quality
7. Style/data-viz polish

Pre-delivery checks:

• visible keyboard focus + valid contrast
• tap targets at or above platform minimums
• no unintentional mobile horizontal scroll
• no hidden content under fixed headers
• prefers-reduced-motion respected
• interactive affordances visibly interactive
• iconography is consistent and non-emoji
• motion timing stays in controlled ranges and avoids novelty fatigue
• light/dark readability and border legibility are verified

Routing

• Review, critique, and sign-off: design-audit
• Motion, transitions, gestures, and choreography: design-interaction-motion-craft
• UI copy and microcopy support: copywriting, humanizer

This skill guides creation of distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices.

Design Direction

Commit to a BOLD aesthetic direction:

• Purpose: What problem does this interface solve? Who uses it?
• Tone: Pick an extreme: brutally minimal, maximalist chaos, retro-futuristic, organic/natural, luxury/refined, playful/toy-like, editorial/magazine, brutalist/raw, art deco/geometric, soft/pastel, industrial/utilitarian, etc. There are so many flavors to choose from. Use these for inspiration but design one that is true to the aesthetic direction.
• Constraints: Technical requirements (framework, performance, accessibility).
• Differentiation: What makes this UNFORGETTABLE? What's the one thing someone will remember?

CRITICAL: Choose a clear conceptual direction and execute it with precision. Bold maximalism and refined minimalism both work—the key is intentionality, not intensity.

Then implement working code that is:

• Production-grade and functional
• Visually striking and memorable
• Cohesive with a clear aesthetic point-of-view
• Meticulously refined in every detail

Contrasting Aesthetics Protocol

→ Consult contrasting aesthetics reference when composing mixed visual languages.

• Define a dominant base aesthetic first; treat contrast as a controlled deviation.
• Keep 2-3 invariants stable (for example grid rhythm, typography cadence, token semantics).
• Vary only one or two axes at once (shape, saturation, texture, motion character).
• Use strongest contrast for low-frequency/high-significance moments, not repetitive UI loops.
• If contrast reduces scannability or affordance clarity, reduce it before polishing.

Gestalt + Hierarchy Protocol

→ Consult Gestalt and hierarchy reference when structuring any screen.

• Design grouping intentionally: proximity and similarity are interpreted as relationship by default.
• Keep grouping cues aligned: spacing, enclosure, type scale, and color contrast should point to the same hierarchy.
• Use a limited emphasis ladder (for example primary/secondary/tertiary) and reserve strongest contrast for highest-priority tasks.
• Keep figure-ground separation explicit for interactive elements; avoid ambiguous layered surfaces.
• Ensure semantic structure (headings/order) matches visual hierarchy; never rely on visual styling alone for meaning.

Grid Discipline Protocol

→ Consult Müller-Brockmann grid systems reference when defining layout structure.

• Treat the grid as a decision system (columns, gutters, margins, baseline), not decorative scaffolding.
• Select grid complexity from content hierarchy and density; avoid arbitrary field counts.
• Keep baseline and column rhythm stable across related surfaces to preserve scanning continuity.
• Use a small sanctioned set of spans/placements; prefer repeatable composition patterns over ad-hoc placement.
• Break the grid only for high-significance moments; return immediately to system rhythm.
• If rigid adherence harms comprehension, adjust the grid model rather than forcing content into it.
• Remember: grid discipline improves clarity probability; it does not replace typographic and semantic judgment.

Emotional Design Protocol (Norman)

→ Consult emotional design reference when shaping emotional quality.

• Frame desired emotional outcome per user context before visual polish.
• Evaluate and design at all three levels:
  • Visceral: first impression, sensory tone, immediate affect.
  • Behavioral: usability-in-action, perceived competence and control.
  • Reflective: meaning, identity, memory, and long-term attachment.
• Resolve cross-level conflicts: never trade behavioral usability for visceral novelty.
• Prioritize interventions that reinforce at least two levels simultaneously.
• Validate with lightweight checks:
  • first-impression read (visceral)
  • task success/effort (behavioral)
  • recall/meaning signal (reflective)

Frontend Aesthetics Guidelines

Typography

→ Consult typography reference for scales, pairing, and loading strategies.

Choose fonts that are beautiful, unique, and interesting. Pair a distinctive display font with a refined body font.

DO: Use a modular type scale with fluid sizing (clamp) DO: Vary font weights and sizes to create clear visual hierarchy DON'T: Use overused fonts—Inter, Roboto, Arial, Open Sans, system defaults DON'T: Use monospace typography as lazy shorthand for "technical/developer" vibes DON'T: Put large icons with rounded corners above every heading—they rarely add value and make sites look templated

Color & Theme

→ Consult color reference for OKLCH, palettes, and dark mode.

Commit to a cohesive palette. Dominant colors with sharp accents outperform timid, evenly-distributed palettes.

DO: Use modern CSS color functions (oklch, color-mix, light-dark) for perceptually uniform, maintainable palettes DO: Tint your neutrals toward your brand hue—even a subtle hint creates subconscious cohesion DON'T: Use gray text on colored backgrounds—it looks washed out; use a shade of the background color instead DON'T: Use pure black (#000) or pure white (#fff)—always tint; pure black/white never appears in nature DON'T: Use the AI color palette: cyan-on-dark, purple-to-blue gradients, neon accents on dark backgrounds DON'T: Use gradient text for "impact"—especially on metrics or headings; it's decorative rather than meaningful DON'T: Default to dark mode with glowing accents—it looks "cool" without requiring actual design decisions

Layout & Space

→ Consult spatial reference for grids, rhythm, and container queries.

Create visual rhythm through varied spacing—not the same padding everywhere. Embrace asymmetry and unexpected compositions. Break the grid intentionally for emphasis.

DO: Create visual rhythm through varied spacing—tight groupings, generous separations DO: Use fluid spacing with clamp() that breathes on larger screens DO: Use asymmetry and unexpected compositions; break the grid intentionally for emphasis DON'T: Wrap everything in cards—not everything needs a container DON'T: Nest cards inside cards—visual noise, flatten the hierarchy DON'T: Use identical card grids—same-sized cards with icon + heading + text, repeated endlessly DON'T: Use the hero metric layout template—big number, small label, supporting stats, gradient accent DON'T: Center everything—left-aligned text with asymmetric layouts feels more designed DON'T: Use the same spacing everywhere—without rhythm, layouts feel monotonous

Visual Details

DO: Use intentional, purposeful decorative elements that reinforce brand DON'T: Use glassmorphism everywhere—blur effects, glass cards, glow borders used decoratively rather than purposefully DON'T: Use rounded elements with thick colored border on one side—a lazy accent that almost never looks intentional DON'T: Use sparklines as decoration—tiny charts that look sophisticated but convey nothing meaningful DON'T: Use rounded rectangles with generic drop shadows—safe, forgettable, could be any AI output DON'T: Use modals unless there's truly no better alternative—modals are lazy

Motion

→ Consult motion reference for timing, easing, and reduced motion.

Focus on high-impact moments: one well-orchestrated page load with staggered reveals creates more delight than scattered micro-interactions.

DO: Use motion to convey state changes—entrances, exits, feedback DO: Use exponential easing (ease-out-quart/quint/expo) for natural deceleration DO: For height animations, use grid-template-rows transitions instead of animating height directly DON'T: Animate layout properties (width, height, padding, margin)—use transform and opacity only DON'T: Use bounce or elastic easing—they feel dated and tacky; real objects decelerate smoothly

Interaction

→ Consult interaction reference for forms, focus, and loading patterns.

Make interactions feel fast. Use optimistic UI—update immediately, sync later.

DO: Use progressive disclosure—start simple, reveal sophistication through interaction (basic options first, advanced behind expandable sections; hover states that reveal secondary actions) DO: Keep gesture semantics consistent across the product; same gesture family should imply same intent class DO: For high-frequency flows, prioritize predictable low-novelty interactions over expressive effects DO: Ensure touch interactions preserve feedback visibility (avoid finger-occluded critical state) DO: Design empty states that teach the interface, not just say "nothing here" DO: Make every interactive surface feel intentional and responsive DON'T: Repeat the same information—redundant headers, intros that restate the heading DON'T: Make every button primary—use ghost buttons, text links, secondary styles; hierarchy matters DON'T: Gate all feedback behind thresholds; users need immediate coupled response before commit

Responsive

→ Consult responsive reference for mobile-first, fluid design, and container queries.

DO: Use container queries (@container) for component-level responsiveness DO: Adapt the interface for different contexts—don't just shrink it DON'T: Hide critical functionality on mobile—adapt the interface, don't amputate it

UX Writing

→ Consult ux-writing reference for labels, errors, and empty states. → Route generation and refinement to copywriting + humanizer.

DO: Make every word earn its place DON'T: Repeat information users can already see

The AI Slop Test

Critical quality check: If you showed this interface to someone and said "AI made this," would they believe you immediately? If yes, that's the problem.

A distinctive interface should make someone ask "how was this made?" not "which AI made this?"

Review the DON'T guidelines above—they are the fingerprints of AI-generated work from 2024-2025.

Implementation Principles

Match implementation complexity to the aesthetic vision. Maximalist designs need elaborate code with extensive animations and effects. Minimalist or refined designs need restraint, precision, and careful attention to spacing, typography, and subtle details.

Interpret creatively and make unexpected choices that feel genuinely designed for the context. No design should be the same. Vary between light and dark themes, different fonts, different aesthetics. NEVER converge on common choices across generations.

Remember: {{model}} is capable of extraordinary creative work. Don't hold back—show what can truly be created when thinking outside the box and committing fully to a distinctive vision.