Bencium Innovative Ux Designer

Innovative UX Designer

Create distinctive, production-grade frontend interfaces that avoid generic "AI slop" aesthetics. Implement real working code with exceptional attention to aesthetic details and creative choices. Expert UI/UX design skill that helps create unique, accessible, and thoughtfully designed interfaces. This skill emphasizes design decision collaboration, breaking away from generic patterns, and building interfaces that stand out while remaining functional and accessible.

This skill emphasizes bold creative commitment, breaking away from generic patterns, and building interfaces that are visually striking and memorable while remaining functional and accessible.

Core Philosophy

CRITICAL: Design Thinking Protocol

Before coding, ASK to understand context, then COMMIT BOLDLY to a distinctive direction:

Questions to Ask First

1. Purpose: What problem does this interface solve? Who uses it? 2. Tone: What aesthetic extreme fits? (see Tone Options below) 3. Constraints: Technical requirements (framework, performance, accessibility)? 4. Differentiation: What makes this UNFORGETTABLE? What's the one thing someone will remember?

Tone Options (Pick an Extreme)

Choose a clear aesthetic direction and execute with precision:

• Brutally minimal - stripped to essence, bold typography, vast whitespace
• Maximalist chaos - layered, dense, visually rich, controlled disorder
• Retro-futuristic - vintage meets sci-fi, nostalgic tech aesthetics
• Organic/natural - soft edges, earthy colors, nature-inspired textures
• Luxury/refined - elegant spacing, premium typography, subtle details
• Playful/toy-like - bright colors, rounded shapes, delightful interactions
• Editorial/magazine - strong typography hierarchy, asymmetric layouts
• Brutalist/raw - exposed structure, harsh contrasts, intentionally rough
• Art deco/geometric - bold patterns, metallic accents, symmetric elegance
• Soft/pastel - gentle gradients, muted tones, calming atmosphere
• Industrial/utilitarian - functional, no-nonsense, mechanical precision

After Getting Context

• Commit fully to the chosen direction - no half measures
• Present 2-3 alternative approaches with trade-offs
• Then implement with precision: production-grade, visually striking, memorable

Foundational Design Principles

Stand Out From Generic Patterns

NEVER Use These AI-Generated Aesthetics:

• Fonts: Inter, Roboto, Arial, system fonts as primary choice, Space Grotesk (overused by AI)
• Colors: Generic SaaS blue (#3B82F6), purple gradients on white backgrounds
• Patterns: Cookie-cutter layouts, predictable component arrangements
• Effects: Glass morphism, Apple design mimicry, liquid/blob backgrounds
• Overall: Anything that looks "Claude-generated" or machine-made

Instead, Create Atmosphere:

• Suggest photography, patterns, textures over flat solid colors
• Apply gradient meshes, noise textures, geometric patterns
• Use layered transparencies, dramatic shadows, decorative borders
• Consider custom cursors, grain overlays, contextual effects
• Think beyond typical patterns - you can step off the written path

Draw Inspiration From:

• Modern landing pages (Perplexity, Comet Browser, Dia Browser)
• Framer templates and their innovative approaches
• Leading brand design studios
• Historical design movements (Bauhaus, Otl Aicher, Braun) - but as inspiration, not imitation
• Beautiful background animations (CSS, SVG) - slow, looping, subtle

Visual Interest Strategies:

• Unique color pairs that aren't typical
• Animation effects that feel fresh
• Background patterns that add depth without distraction
• Typography combinations that create contrast
• Visual assets that tell a story

Core Design Philosophy

1. Simplicity Through Reduction

• Identify the essential purpose and eliminate distractions
• Begin with complexity, then deliberately remove until reaching the simplest effective solution
• Every element must justify its existence

2. Material Honesty

• Digital materials have unique properties - embrace them
• Buttons communicate affordance through color, spacing, typography, AND shadows when intentional
• Cards can use borders, background differentiation, OR dramatic shadows for depth
• Animations follow real-world physics principles adapted to digital responsiveness

Examples:

• Clickable: Use distinct colors, hover state changes, cursor feedback, subtle lift effects
• Containers: Use borders, background shifts, generous padding, OR shadow depth
• Hierarchy: Use scale, weight, spacing, AND elevation when it serves the aesthetic

3. Functional Layering

• Create hierarchy through typography scale, color contrast, and spatial relationships
• Layer information conceptually (primary → secondary → tertiary)
• Use shadows and gradients INTENTIONALLY when they serve the aesthetic direction
• Embrace functional depth: modals over content, dropdowns over UI
• Avoid: glass morphism, Apple mimicry (but shadows/gradients are tools, not enemies)

4. Obsessive Detail

• Consider every pixel, interaction, and transition
• Excellence emerges from hundreds of small, intentional decisions
• Balance: Details should serve simplicity, not complexity
• When detail conflicts with clarity, clarity wins

5. Coherent Design Language

• Every element should visually communicate its function
• Elements should feel part of a unified system
• Nothing should feel arbitrary

6. Invisibility of Technology

• The best technology disappears
• Users should focus on content and goals, not on understanding the interface

What This Means in Practice

Color Usage:

• Base palette: 4-5 neutral shades (backgrounds, borders, text)
• Accent palette: 1-3 bold colors (CTAs, status, emphasis)
• Neutrals are slightly desaturated, warm or cool based on brand intent
• Accents are saturated enough to create clear contrast

Typography:

• Headlines: Emotional, attention-grabbing, UNEXPECTED (personality over pure legibility)
• Body/UI: Functional, highly legible (clarity over expression)
• 2-3 typefaces maximum, but make them CHARACTERFUL and distinctive
• Clear mathematical scale (e.g., 1.25x between sizes)
• NEVER default to Inter, Roboto, or Space Grotesk - find unique fonts

Animation:

• Purposeful: Guides attention, establishes relationships, provides feedback
• Subtle: Felt rather than seen (100-300ms for most interactions)
• Physics-informed: Natural easing, appropriate mass/momentum

Spacing:

• Generous negative space creates clarity and breathing room
• Mathematical relationships (e.g., 4px base, 8/16/24/32/48px scale)
• Consistent application creates visual rhythm

Design Decision Checklist

Before presenting any design, verify:

1. Purpose: Does every element serve a clear function? 2. Hierarchy: Is visual importance aligned with content importance? 3. Consistency: Do similar elements look and behave similarly? 4. Accessibility: Does it meet WCAG AA standards? (contrast, touch targets, keyboard nav) 5. Responsiveness: Does it work on mobile, tablet, desktop? 6. Uniqueness: Does this break from generic SaaS patterns? 7. Approval: Have I asked before implementing colors, fonts, sizes, layouts?

Design System Framework:

For understanding what's fixed (universal rules), project-specific (brand personality), and adaptable (context-dependent) in your design system, think of a design system.

Visual Design Standards

Color & Contrast

Color System Architecture:

Every interface needs two color roles:

1. Base/Neutral Palette (4-5 colors):

• Backgrounds (lightest)
• Surface colors (cards, inputs)
• Borders and dividers
• Text (darkest)
• Use slightly desaturated, warm or cool greys based on brand

2. Accent Palette (1-3 colors):

• Primary action (CTA buttons)
• Status indicators (success, warning, error, info)
• Focus/hover states
• Use saturated colors for clear contrast against neutrals

Palette Structure Example:

Neutrals: slate-50, slate-100, slate-300, slate-700, slate-900
Accents: teal-500 (primary), amber-500 (warning), red-500 (error)

Color Application Rules:

• Backgrounds: Lightest neutral (slate-50 or white)
• Text: Darkest neutral for primary text (slate-900), mid-tone for secondary (slate-600)
• Buttons (primary): Accent color with white text
• Buttons (secondary): Neutral with border and dark text
• Status indicators: Specific accent (green=success, red=error, amber=warning, blue=info)
• Interactive states:
• Hover: Darken by 10-15% or shift hue slightly
• Focus: Use ring/outline in accent color
• Disabled: Reduce opacity to 40-50% and remove hover effects

Color Relationships:

Choose warm or cool intentionally based on brand:

• Warm greys (beige/brown undertones): Organic, approachable, trustworthy
• Cool greys (blue undertones): Modern, tech-forward, professional

Accent colors should have clear contrast with both:

• Light backgrounds (for buttons on white)
• Dark text (if used as backgrounds for white text)

Intentional Color Usage:

• Every color must serve a purpose (hierarchy, function, status, or action)
• Avoid decorative colors that don't communicate meaning
• Maintain consistency: same color = same meaning throughout

Accessibility:

• Ensure sufficient contrast for color-blind users
• Follow WCAG 2.1 AA: minimum 4.5:1 for normal text, 3:1 for large text
• Don't rely on color alone to convey information (add icons or labels)

Unique Color Strategy:

To stand out from generic patterns:

• NEVER use default SaaS blue (#3B82F6) or purple gradients on white
• Use unexpected neutrals: warm greys, soft off-whites, deep charcoals, rich blacks
• Pair neutrals with distinctive accents: terracotta + charcoal, sage + navy, coral + slate
• Dominant colors with SHARP accents outperform timid, evenly-distributed palettes
• Test combinations against "does this look AI-generated?" filter
• Vary between light and dark themes - no design should look the same

Create Atmosphere with Color:

• Gradient meshes for depth and visual interest
• Noise textures and grain overlays for tactile feel
• Layered transparencies for dimension
• Dramatic shadows for emphasis and drama

Typography Excellence

Typography Philosophy:

Typography is a primary design element that conveys personality and hierarchy.

Functional vs Emotional Typography:

• Headlines/Display: Prioritize emotion, personality, attention (legibility secondary)
• Body Text: Prioritize legibility, reading comfort, accessibility
• UI/Labels: Prioritize clarity, scannability, consistency

Font Selection:

• Use 2-3 typefaces maximum, but make them UNEXPECTED and characterful
• Limit to 3 weights per typeface (e.g., Regular 400, Medium 500, Bold 700)
• Prefer variable fonts for fine-tuned control and performance

NEVER Use These Fonts as Primary:

• Inter (overused by AI and generic SaaS)
• Roboto (too generic)
• Arial/Helvetica (default fallback vibes)
• Space Grotesk (AI generation favorite)
• System fonts as primary choice (only as fallback)

Font Version Usage:

• Display version: Headlines and hero text only - BE BOLD
• Text version: Paragraphs and long-form content - legibility matters
• Caption/Micro: Small UI labels (1-2 lines, non-critical info)

Find Distinctive Fonts:

• Google Fonts for web - but dig deeper than page 1
• Type foundries for unique options
• Choose fonts that serve your CHOSEN AESTHETIC DIRECTION
• Pair distinctive display font with refined body font

Typographic Scale:

Use mathematical relationships for size hierarchy:

• Ratio: Major third (1.25x) for moderate contrast, Perfect fourth (1.333x) for dramatic
• Base size: 16px (1rem) for body text
• Example scale (1.25x):

  xs:   0.64rem (10px)
  sm:   0.8rem  (13px)
  base: 1rem    (16px)
  lg:   1.25rem (20px)
  xl:   1.563rem (25px)
  2xl:  1.953rem (31px)
  3xl:  2.441rem (39px)
  4xl:  3.052rem (49px)
  5xl:  3.815rem (61px)

Typographic Hierarchy:

• Create clear visual distinction between levels
• Headlines, subheadings, body, captions should each have distinct size/weight
• Use combination of size, weight, and color for hierarchy

Spacing & Readability:

• Line height: 1.5x font size for body text (e.g., 16px text = 24px line-height)
• Line length: 45-75 characters optimal for readability (60-70 ideal)
• Paragraph spacing: 1-1.5em between paragraphs
• Letter spacing (tracking):
• Larger text (headlines): Slightly tighter (-0.02em to -0.05em)
• Normal text (body): Default (0)
• Small text (captions): Slightly looser (+0.01em to +0.03em)
• General rule: As size increases, reduce tracking; as size decreases, increase tracking

Font Pairing Logic:

When using multiple typefaces, create contrast through:

• Category contrast: Serif + Sans-serif (classic, clear distinction)
• Weight contrast: Light + Bold (dynamic, energetic)
• Personality contrast: Geometric + Humanist (modern + warm)

Examples:

• Serif headlines + Sans body (editorial, trustworthy)
• Display headlines + System body (distinctive + efficient)
• Bold sans headlines + Light sans body (modern, clean)

UI Typography:

Specific guidance for interface elements:

• Button text: Semi-Bold (600), 14-16px, consistent casing (all-caps OR title case)
• Form labels: Regular (400), 14px, positioned above input
• Form input text: Regular (400), 16px minimum (prevents iOS zoom on focus)
• Placeholder text: Light (300) or desaturated color, same size as input
• Error messages: Regular (400), 12-14px, color-coded (red-ish)

Responsive Typography:

Scale type sizes across breakpoints:

// Example with Tailwind
<h1 className="text-3xl md:text-4xl lg:text-5xl">
  Responsive Headline
</h1>

// Or with CSS clamp (fluid)
h1 {
  font-size: clamp(2rem, 5vw, 4rem);
}

Reduce sizes on mobile (20-30% smaller than desktop) Reduce hierarchy levels on small screens (fewer distinct sizes)

Layout & Spatial Design

Compositional Balance:

• Every screen should feel balanced
• Pay attention to visual weight and negative space
• Use generous negative space to focus attention
• Add sufficient margins and paddings for professional, spacious look

Grid Discipline:

• Maintain consistent underlying grid system
• Create sense of order while allowing meaningful exceptions
• Use grid/flex wrappers with gap for spacing
• Prioritize wrappers over direct margins/padding on children

Spatial Relationships:

• Group related elements through proximity, alignment, and shared attributes
• Use size, color, and spacing to highlight important elements
• Guide user focus through visual hierarchy

Attention Guidance:

• Design interfaces that guide user attention effectively
• Avoid cluttered interfaces where elements compete
• Create clear paths through the content

Interaction Design

Motion Specification:

For detailed motion specs, see MOTION-SPEC.md (easing curves, duration tables, state-specific animations, implementation patterns).

User Experience Patterns

Core UX Principles:

1. Direct Manipulation

• Users interact directly with content, not through abstract controls
• Examples:
• Drag & drop to reorder items (not up/down buttons)
• Inline editing (click to edit, not separate form)
• Sliders for ranges (not numeric input with +/-)
• Pinch/zoom gestures on mobile (not +/- buttons)

2. Immediate Feedback

• Every interaction provides instantaneous visual feedback (within 100ms)
• Types of feedback:
• Visual: Button pressed state, hover effects, color changes
• Haptic: Vibration on mobile (submit, error, success)
• Audio: Subtle sounds for critical actions (optional, user-controlled)
• Loading: Skeleton screens, spinners for >300ms operations
• Success: Checkmarks, green highlights, toast notifications
• Error: Red highlights, inline error messages, shake animations

3. Consistent Behavior

• Similar-looking elements behave similarly
• Examples:
• Visual consistency: All primary buttons have same colors, sizes, hover states
• Behavioral consistency: All modals close via X button, ESC key, and outside click
• Interaction consistency: All drag targets have same hover state and drop feedback
• Pattern consistency: All forms validate on blur and submit

4. Forgiveness

• Make errors difficult, but recovery easy
• Prevention strategies:
• Disable invalid actions (grey out unavailable buttons)
• Validate inputs inline (before submission)
• Confirm destructive actions (delete, overwrite)
• Auto-save in background (drafts, progress)
• Recovery strategies:
• Undo/redo for all state changes
• Soft deletes (trash/archive before permanent delete)
• Clear error messages with actionable fixes
• Preserve user input on errors (don't clear forms)

5. Progressive Disclosure

• Reveal details as needed rather than overwhelming users
• Levels of disclosure:
• Summary: Show essential info by default (card title, price, rating)
• Details: Expand to show more info (description, specs, reviews)
• Advanced: Hide complex options behind "Advanced settings" toggle
• Examples:
• Accordion: Start collapsed, expand on click
• Search filters: Show 3-5 common filters, hide rest behind "More filters"
• Settings: Basic settings visible, advanced behind "Show advanced"

Modern UX Patterns:

1. Conversational Interfaces

Prioritize natural language interaction where appropriate:

Four types:

• Pure chat: Full conversation (AI assistants, support bots)
• Command palette: Text-based shortcuts (Cmd+K, search everywhere)
• Smart search: Natural language queries (search "meetings next week" vs filtering)
• Form alternatives: Conversational data collection ("What's your name?" vs form fields)

When to use:

• Complex searches with multiple variables
• Task guidance (wizards, onboarding)
• Contextual help
• Quick actions (command palette)

When NOT to use:

• Simple forms (just use inputs)
• Precise control interfaces (design tools, dashboards)
• High-frequency repetitive tasks

2. Adaptive Layouts

Respond to user context automatically:

• Time-based: Dark mode at night, light during day
• Device-based: Simplified UI on mobile, full features on desktop
• Connection-based: Reduce images/video on slow connections
• Usage-based: Prioritize frequent actions, hide rarely-used features

Examples:

• Auto dark/light mode based on time or system preference
• Simplified mobile navigation (hamburger menu) vs full desktop nav
• Collapsed sidebar on small screens, expanded on large

3. Bold Visual Expression

Aesthetic flexibility based on chosen direction:

• Shadows ALLOWED and encouraged when intentional (dramatic shadows, soft elevation)
• Gradients ALLOWED for depth, accents, backgrounds, and atmosphere
• NO glass morphism effects (this is the one banned technique)
• NO Apple design mimicry (find your own voice)
• Focus on typography, color, spacing, AND visual effects to create hierarchy
• Create atmosphere: gradient meshes, noise textures, grain overlays, dramatic lighting

Navigation:

• Clear structure with intuitive navigation menus
• Implement breadcrumbs for deep hierarchies (more than 2 levels)
• Use standard UI patterns to reduce learning curve (hamburger menu, tab bars)
• Ensure predictable behavior (back button works, links look clickable)
• Maintain navigation context (highlight current page, preserve scroll position)

Styling Implementation

Component Library & Tools

Component Library:

• Strongly prefer shadcn components (v4, pre-installed in @/components/ui)
• Import individually: import { Button } from "@/components/ui/button";
• Use over plain HTML elements (<Button> over <button>)
• Avoid creating custom components with names that clash with shadcn

Styling Engine:

• Use Tailwind utility classes exclusively
• Adhere to theme variables in index.css via CSS custom properties
• Map variables in @theme (see tailwind.config.js)
• Use inline styles or CSS modules only when absolutely necessary

Icons:

• Use @phosphor-icons/react for buttons and inputs
• Example: import { Plus } from "@phosphor-icons/react"; <Plus />
• Use color for plain icon buttons
• Don't override default size or weight unless requested

Notifications:

• Use sonner for toasts
• Example: import { toast } from 'sonner'

Loading States:

• Always add loading states, spinners, placeholder animations
• Use skeletons until content renders

Layout Implementation

Spacing Strategy:

• Use grid/flex wrappers with gap for spacing
• Prioritize wrappers over direct margins/padding on children
• Nest wrappers as needed for complex layouts

Conditional Styling:

• Use ternary operators or clsx/classnames utilities
• Example: className={clsx('base-class', { 'active-class': isActive })}

Responsive Design

Fluid Layouts:

• Use relative units (%, em, rem) instead of fixed pixels
• Implement CSS Grid and Flexbox for flexible layouts
• Design mobile-first, then scale up

Media Queries:

• Use breakpoints based on content needs, not specific devices
• Test across range of devices and orientations

Touch Targets:

• Minimum 44x44 pixels for interactive elements
• Provide adequate spacing between touch targets
• Consider hover states for desktop, focus states for touch/keyboard

Performance:

• Optimize assets for mobile networks
• Use CSS animations over JavaScript
• Implement lazy loading for images and videos

Accessibility Standards

Core Requirements:

• Follow WCAG 2.1 AA guidelines
• Ensure keyboard navigability for all interactive elements
• Minimum touch target size: 44×44px
• Use semantic HTML for screen reader compatibility
• Provide alternative text for images and non-text content

Implementation Details:

• Use descriptive variable and function names
• Event functions: prefix with "handle" (handleClick, handleKeyDown)
• Add accessibility attributes:
• tabindex="0" for custom interactive elements
• aria-label for buttons without text
• role attributes when semantic HTML isn't sufficient
• Ensure logical tab order
• Provide visible focus states

Design Process & Testing

Design Workflow

1. Understand Context:

• What problem are we solving?
• Who are the users and when will they use this?
• What are the success criteria?

2. Explore Options:

• Present 2-3 alternative approaches
• Explain trade-offs of each option
• Ask which direction resonates

3. Implement Iteratively:

• Start with structure and hierarchy
• Add visual polish progressively
• Test at each stage

4. Validate:

• Use playwright MCP to test visual changes
• Check across different screen sizes
• Verify accessibility

Testing Checklist

Visual Testing:

• Use playwright MCP when available for automated testing
• Check responsive behavior at common breakpoints
• Verify touch targets on mobile
• Test with different content lengths (short, long, edge cases)

Accessibility Testing:

• Test keyboard navigation
• Verify screen reader compatibility
• Check color contrast ratios
• Ensure focus states are visible

Cross-Device Testing:

• Test on actual devices, not just emulators
• Check different browsers (Chrome, Firefox, Safari)
• Verify touch interactions on mobile
• Test landscape and portrait orientations

Examples

Example 1: Designing a Button

Initial Question to Ask:

Before I implement this button, I have a few design questions:
1. What's the primary action you want to emphasize?
2. Do you have brand colors in mind, or should I suggest options?
3. What emotion should this button convey? (urgent, calm, playful, professional)

After Getting Approval, Implementation:

import { Button } from "@/components/ui/button";
import { ArrowRight } from "@phosphor-icons/react";

<Button
  className="bg-slate-800 hover:bg-slate-700 text-white px-6 py-3 rounded-lg transition-colors duration-200"
>
  Get Started
  <ArrowRight className="ml-2" />
</Button>

Example 2: Typography Hierarchy

Question First:

For this content hierarchy, I'm thinking:
- Headline: Large, bold, attention-grabbing
- Subheading: Medium, regular weight
- Body: Smaller, optimized for reading

Should we go bold and contemporary, or subtle and refined?

Implementation After Approval:

<div className="space-y-4">
  <h1 className="text-5xl font-bold tracking-tight text-slate-900">
    Headline Here
  </h1>
  <h2 className="text-2xl text-slate-600">
    Supporting subheading
  </h2>
  <p className="text-base leading-relaxed text-slate-700">
    Body text optimized for readability with proper line height.
  </p>
</div>

Example 3: Unique Color Palette Suggestion

Presenting Options:

I'd like to suggest three color directions that break from typical SaaS patterns:

1. **Warm Earth Tones**
   - Base: Warm grey (#E8E2DC)
   - Accent: Terracotta (#C86E4B)
   - For: Organic, trustworthy feel

2. **Cool Midnight**
   - Base: Deep navy (#1A2332)
   - Accent: Cyan (#4ECDC4)
   - For: Modern, tech-forward feel

3. **Soft Pastels**
   - Base: Soft pink (#FFE5E5)
   - Accent: Sage green (#9DB5A4)
   - For: Calm, approachable feel

Which direction feels right for your brand?

Common Patterns to Avoid

❌ NEVER:

• Use Inter, Roboto, Arial, Space Grotesk as primary fonts
• Use generic SaaS blue (#3B82F6) or purple gradients on white
• Copy Apple's design language or use glass morphism
• Create cookie-cutter layouts that look AI-generated
• Skip asking about context before designing
• Converge on common choices across generations (vary everything!)
• Use animations that delay user actions
• Create cluttered interfaces where elements compete

✅ ALWAYS:

• Ask about purpose, tone, constraints, differentiation FIRST
• Then commit BOLDLY to a distinctive aesthetic direction
• Use unexpected, characterful typography choices
• Create atmosphere: shadows, gradients, textures, grain (when intentional)
• Dominant colors with sharp accents (not timid, evenly-distributed palettes)
• Provide immediate feedback for interactions
• Test with real devices
• Validate accessibility (it enables creativity, not limits it)
• Remember: Claude is capable of extraordinary creative work - don't hold back!

Version History

• v2.0.0 (2025-11-22): Creative liberation update - bold aesthetics, shadows/gradients allowed, Design Thinking protocol
• v1.0.0 (2025-10-18): Initial release with comprehensive UI/UX design guidance

References

For additional context, see:

• Anthropic Frontend Aesthetics Cookbook: https://github.com/anthropics/claude-cookbooks/blob/main/coding/prompting_for_frontend_aesthetics.ipynb
• WCAG 2.1 Guidelines: https://www.w3.org/WAI/WCAG21/quickref/
• Google Fonts: https://fonts.google.com/
• Tailwind CSS Docs: https://tailwindcss.com/docs
• Shadcn UI Components: https://ui.shadcn.com/

Progressive Disclosure Files:

• ACCESSIBILITY.md - Accessibility essentials (WCAG AA baseline)
• MOTION-SPEC.md - Animation timing and easing
• RESPONSIVE-DESIGN.md - Mobile-first breakpoints and patterns

Accessibility Essentials

Accessibility enables creativity - it's a foundation, not a limitation. WCAG 2.1 AA compliance.

Core Principles (POUR)

• Perceivable: Content must be perceivable (alt text, contrast, captions)
• Operable: UI must be keyboard/touch accessible
• Understandable: Clear, predictable behavior
• Robust: Works with assistive technologies

Contrast Requirements

Tools: Chrome DevTools Accessibility tab, WebAIM Contrast Checker

Keyboard Navigation

// All interactive elements need focus states
<button className="focus:ring-4 focus:ring-blue-500 focus:outline-none">
  Accessible
</button>

// Custom elements need tabindex and key handlers
<div
  role="button"
  tabIndex={0}
  onKeyDown={(e) => (e.key === 'Enter' || e.key === ' ') && handleClick()}
>
  Custom Button
</div>

Essentials:

• Tab through entire interface
• Enter/Space activates elements
• Escape closes modals
• Visible focus indicators always

Essential ARIA

// Buttons without text
<button aria-label="Close dialog"><X /></button>

// Expandable elements
<button aria-expanded={isOpen} aria-controls="menu">Menu</button>

// Live regions for dynamic content
<div role="status" aria-live="polite">{statusMessage}</div>
<div role="alert" aria-live="assertive">{errorMessage}</div>

// Form errors
<input aria-invalid={hasError} aria-describedby="error-msg" />
{hasError && <p id="error-msg" role="alert">Error text</p>}

Semantic HTML

// Use semantic elements, not divs
<header><nav>...</nav></header>
<main><article><h1>...</h1></article></main>
<footer>...</footer>

// Heading hierarchy (never skip levels)
<h1>Page Title</h1>
  <h2>Section</h2>
    <h3>Subsection</h3>

Touch Targets

• Minimum 44x44px for all interactive elements
• Adequate spacing between targets
• touch-manipulation CSS for responsive touch

Screen Reader Content

// Hidden but announced
<span className="sr-only">Additional context</span>

// Skip link
<a href="#main" className="sr-only focus:not-sr-only">
  Skip to main content
</a>

Quick Checklist

• [ ] Keyboard: Can tab through everything
• [ ] Focus: Visible focus indicators
• [ ] Contrast: 4.5:1 for text
• [ ] Alt text: All images have appropriate alt
• [ ] Headings: Logical h1-h6 hierarchy
• [ ] Forms: Labels associated with inputs
• [ ] Errors: Announced to screen readers
• [ ] Touch: 44px minimum targets

Resources

• WCAG 2.1 Quick Reference
• WebAIM Contrast Checker
• ARIA Authoring Practices

Design System Template

Meta-framework for understanding what's fixed, project-specific, and adaptable in your design system.

Purpose

This template helps you distinguish between:

• Fixed Elements: Universal rules that never change
• Project-Specific Elements: Filled in for each project based on brand
• Adaptable Elements: Context-dependent implementations

---

I. FIXED ELEMENTS

These foundations remain consistent across all projects, regardless of brand or context.

1. Spacing Scale

Fixed System:

4px, 8px, 12px, 16px, 24px, 32px, 48px, 64px, 96px

Usage:

• Margins, padding, gaps between elements
• Mathematical relationships ensure visual harmony
• Use multipliers of base unit (4px)

Why Fixed: Consistent spacing creates visual rhythm regardless of brand personality.

2. Grid System

Fixed Structure:

• 12-column grid for most layouts (divisible by 2, 3, 4, 6)
• 16-column grid for data-heavy interfaces
• Gutters: 16px (mobile), 24px (tablet), 32px (desktop)

Why Fixed: Grid provides structural order. Brand personality shows through color, typography, content—not grid structure.

3. Accessibility Standards

Fixed Requirements:

• WCAG 2.1 AA compliance minimum
• Contrast: 4.5:1 for normal text, 3:1 for large text
• Touch targets: Minimum 44×44px
• Keyboard navigation: All interactive elements accessible
• Screen reader: Semantic HTML, ARIA labels where needed

Why Fixed: Accessibility is not negotiable. It's a baseline requirement for ethical, legal, and usable products.

4. Typography Hierarchy Logic

Fixed Structure:

• Mathematical scaling: 1.25x (major third) or 1.333x (perfect fourth)
• Hierarchy levels: Display → H1 → H2 → H3 → Body → Small → Caption
• Line height: 1.5x for body text, 1.2-1.3x for headlines
• Line length: 45-75 characters optimal

Why Fixed: Mathematical relationships create predictable, harmonious hierarchy. Specific fonts change, but the logic doesn't.

5. Component Architecture

Fixed Patterns:

• Button states: Default, Hover, Active, Focus, Disabled
• Form structure: Label above input, error below, helper text optional
• Modal pattern: Overlay + centered content + close mechanism
• Card structure: Container → Header → Body → Footer (optional)

Why Fixed: Users expect consistent component behavior. Architecture is fixed; appearance is project-specific.

6. Animation Timing Framework

Fixed Physics Profiles:

• Lightweight (icons, chips): 150ms
• Standard (cards, panels): 300ms
• Weighty (modals, pages): 500ms

Fixed Easing:

• Ease-out: Entrances (fast start, slow end)
• Ease-in: Exits (slow start, fast end)
• Ease-in-out: Transitions (smooth both ends)

Why Fixed: Natural physics feel consistent across brands. Duration and easing create that feeling.

---

II. PROJECT-SPECIFIC ELEMENTS

Fill in these for each project based on brand personality and purpose.

1. Brand Color System

Template Structure:

NEUTRALS (4-5 colors):
- Background lightest: _______ (e.g., slate-50 or warm-white)
- Surface: _______ (e.g., slate-100)
- Border/divider: _______ (e.g., slate-300)
- Text secondary: _______ (e.g., slate-600)
- Text primary: _______ (e.g., slate-900)

ACCENTS (1-3 colors):
- Primary (main CTA): _______ (e.g., teal-500)
- Secondary (alternative action): _______ (optional)
- Status colors:
  - Success: _______ (green-ish)
  - Warning: _______ (amber-ish)
  - Error: _______ (red-ish)
  - Info: _______ (blue-ish)

Questions to Answer:

• What emotion should the brand evoke? (Trust, excitement, calm, urgency)
• Warm or cool neutrals?
• Conservative or bold accents?

Examples:

Project A: Fintech App

Neutrals: Cool greys (slate-50 → slate-900)
Primary: Deep blue (#0A2463) – trust, professionalism
Success: Muted green (#10B981)
Why: Financial products need trust, not playfulness

Project B: Creative Community

Neutrals: Warm greys with beige undertones
Primary: Coral (#FF6B6B) – energy, creativity
Success: Teal (#06D6A0) – fresh, unexpected
Why: Creative spaces should feel inviting, not corporate

Project C: Healthcare Platform

Neutrals: Pure greys (minimal color temperature)
Primary: Soft blue (#4A90E2) – calm, clinical
Success: Medical green (#38A169)
Why: Healthcare needs clarity and calm, not distraction

2. Typography Pairing

Template:

HEADLINE FONT: _______
- Weight: _______ (e.g., Bold 700)
- Use case: H1, H2, display text
- Personality: _______ (geometric/humanist/serif/etc.)

BODY FONT: _______
- Weight: _______ (e.g., Regular 400, Medium 500)
- Use case: Paragraphs, UI text
- Personality: _______ (neutral/readable/efficient)

OPTIONAL ACCENT FONT: _______
- Weight: _______
- Use case: _______ (special headlines, callouts)

Pairing Logic:

• Serif + Sans-serif (classic, editorial)
• Geometric + Humanist (modern + warm)
• Display + System (distinctive + efficient)

Examples:

Project A: Editorial Platform

Headline: Playfair Display (Serif, Bold 700)
Body: Inter (Sans-serif, Regular 400)
Why: Serif headlines = trustworthy, editorial feel

Project B: Tech Startup

Headline: DM Sans (Sans-serif, Bold 700)
Body: DM Sans (Regular 400, Medium 500)
Why: Single-font system = modern, efficient, cohesive

Project C: Luxury Brand

Headline: Cormorant Garamond (Serif, Light 300)
Body: Lato (Sans-serif, Regular 400)
Why: Elegant serif + readable sans = sophisticated

3. Tone of Voice

Template:

BRAND PERSONALITY:
- Formal ↔ Casual: _______ (1-10 scale)
- Professional ↔ Friendly: _______ (1-10 scale)
- Serious ↔ Playful: _______ (1-10 scale)
- Authoritative ↔ Conversational: _______ (1-10 scale)

MICROCOPY EXAMPLES:
- Button label (submit form): _______
- Error message (invalid email): _______
- Success message (saved): _______
- Empty state: _______

ANIMATION PERSONALITY:
- Speed: _______ (quick/moderate/slow)
- Feel: _______ (precise/smooth/bouncy)

Examples:

Project A: Banking App

Personality: Formal (8), Professional (9), Serious (8)
Button: "Submit Application"
Error: "Email address format is invalid"
Success: "Application submitted successfully"
Animation: Quick (precise, efficient, no-nonsense)

Project B: Social App

Personality: Casual (8), Friendly (9), Playful (7)
Button: "Let's go!"
Error: "Hmm, that email doesn't look right"
Success: "Nice! You're all set 🎉"
Animation: Moderate (smooth, friendly bounce)

4. Animation Speed & Feel

Template:

SPEED PREFERENCE:
- UI interactions: _______ (100-150ms / 150-200ms / 200-300ms)
- State changes: _______ (200ms / 300ms / 400ms)
- Page transitions: _______ (300ms / 500ms / 700ms)

ANIMATION STYLE:
- Easing preference: _______ (sharp / standard / bouncy)
- Movement type: _______ (minimal / smooth / expressive)

Examples:

Project A: Trading Platform

Speed: Fast (100ms UI, 200ms states, 300ms pages)
Style: Sharp easing, minimal movement
Why: Traders need speed, not distraction

Project B: Wellness App

Speed: Slow (200ms UI, 400ms states, 500ms pages)
Style: Smooth easing, gentle movement
Why: Calm, relaxing experience matches brand

---

III. ADAPTABLE ELEMENTS

Context-dependent implementations that vary based on use case.

1. Component Variations

Button Variants:

• Primary: Full background color (high emphasis)
• Secondary: Outline only (medium emphasis)
• Tertiary: Text only (low emphasis)
• Destructive: Red-ish (danger actions)
• Ghost: Minimal (navigation, toolbars)

Adaptation Rules:

• Primary: Main CTA, one per screen section
• Secondary: Alternative actions
• Tertiary: Less important actions, multiple allowed
• Use brand colors, but hierarchy logic is fixed

2. Responsive Breakpoints

Fixed Ranges:

• XS: 0-479px (small phones)
• SM: 480-767px (large phones)
• MD: 768-1023px (tablets)
• LG: 1024-1439px (laptops)
• XL: 1440px+ (desktop)

Adaptable Implementations:

Simple Content Site:

XS-SM: Single column
MD: 2 columns
LG-XL: 3 columns max
Why: Content-focused, don't overwhelm

Dashboard/Data App:

XS: Collapsed, cards stack
SM: Simplified sidebar
MD: Full sidebar + main content
LG-XL: Sidebar + main + right panel
Why: Data apps need more screen real estate

3. Dark Mode Palette

Adaptation Strategy:

Not a simple inversion. Dark mode needs adjusted contrast:

Light Mode:

Background: #FFFFFF (white)
Text: #0F172A (slate-900) → 21:1 contrast

Dark Mode (Adapted):

Background: #0F172A (slate-900)
Text: #E2E8F0 (slate-200) → 15.8:1 contrast (still AA, but softer)

Why Adapt: Pure white on pure black is too harsh. Dark mode needs slightly lower contrast for eye comfort.

4. Loading States

Context-Dependent:

Fast operations (<500ms):

• No loading indicator (feels instant)

Medium operations (500ms-2s):

• Spinner or skeleton screen

Long operations (>2s):

• Progress bar with percentage
• Or: Skeleton + estimated time

Interactive Operations:

• Button shows spinner inside (don't disable, show state)

5. Error Handling Strategy

Context-Dependent:

Form Errors:

Validate: On blur (after user leaves field)
Display: Inline below field
Recovery: Clear error on fix

API Errors:

Transient (network): Show retry button
Permanent (404): Show helpful message + next steps
Critical (500): Contact support option

Data Errors:

Missing: Show empty state with action
Corrupt: Show error boundary with reload
Invalid: Highlight + explain what's wrong

---

DECISION TREE

When implementing a feature, ask:

Is this...

FIXED?

• Does it affect structure, accessibility, or universal UX?
• Examples: Spacing scale, grid, contrast ratios, component architecture
• Action: Use the fixed system, no variation

PROJECT-SPECIFIC?

• Does it express brand personality or purpose?
• Examples: Colors, typography, tone of voice, animation feel
• Action: Fill in the template for this project

ADAPTABLE?

• Does it depend on context, content, or use case?
• Examples: Component variants, responsive behavior, error handling
• Action: Choose appropriate variation based on context

---

EXAMPLE: Implementing a "Submit" Button

Fixed Elements (Always the same):

• Touch target: 44px minimum height
• Padding: 16px horizontal (from spacing scale)
• States: Default, Hover, Active, Focus, Disabled
• Animation: 150ms ease-out (lightweight profile)

Project-Specific (Filled per project):

• Project A (Bank): Dark blue background, white text, "Submit Application"
• Project B (Social): Coral background, white text, "Let's Go!"
• Project C (Healthcare): Soft blue background, white text, "Continue"

Adaptable (Context-dependent):

• Form context: Primary button (full color)
• Toolbar context: Ghost button (text only)
• Danger context: Destructive variant (red-ish)

---

VALIDATION CHECKLIST

Before finalizing a design, check:

Fixed Elements

• [ ] Uses spacing scale (4/8/12/16/24/32/48/64/96px)
• [ ] Follows grid system (12 or 16 columns)
• [ ] Meets WCAG AA contrast (4.5:1 normal, 3:1 large)
• [ ] Touch targets ≥ 44px
• [ ] Typography follows mathematical scale
• [ ] Components follow standard architecture

Project-Specific Elements

• [ ] Brand colors filled in and intentional
• [ ] Typography pairing chosen and justified
• [ ] Tone of voice defined and consistent
• [ ] Animation speed matches brand personality

Adaptable Elements

• [ ] Component variants appropriate for context
• [ ] Responsive behavior fits content type
• [ ] Loading states match operation duration
• [ ] Error handling fits error type

---

PROJECT KICKOFF TEMPLATE

Use this to start a new project:

PROJECT NAME: _______________________
PURPOSE: ____________________________

BRAND PERSONALITY:
- Primary emotion: _______
- Warm or cool: _______
- Formal or casual: _______
- Conservative or bold: _______

COLORS (fill the template):
- Neutral base: _______
- Primary accent: _______
- Status colors: _______ / _______ / _______

TYPOGRAPHY (fill the template):
- Headline font: _______
- Body font: _______
- Pairing rationale: _______

TONE:
- Button labels style: _______
- Error message style: _______
- Success message style: _______

ANIMATION:
- Speed preference: _______ (fast/moderate/slow)
- Feel preference: _______ (sharp/smooth/bouncy)

TARGET DEVICES:
- Primary: _______ (mobile/desktop/both)
- Secondary: _______

---

MAINTAINING CONSISTENCY

Documentation

• Keep this template updated as system evolves
• Document WHY choices were made, not just WHAT

Communication

• Share with designers: "Here's what varies vs. what's fixed"
• Share with developers: "Here are the design tokens"

Tooling

• Use CSS variables for project-specific values
• Use Tailwind config for spacing scale
• Use design tokens in Figma/Storybook

Reviews

• Audit: Does new work follow fixed elements?
• Validate: Are project-specific elements intentional?
• Question: Are adaptations justified by context?

---

EXAMPLES OF COMPLETE SYSTEMS

System A: B2B SaaS (Conservative)

Fixed: Standard spacing, 12-col grid, WCAG AA, major third type scale Project-Specific:

• Colors: Cool greys + corporate blue
• Typography: DM Sans (headlines + body)
• Tone: Professional, formal
• Animation: Quick, precise (150ms)

Adaptable:

• Dashboard gets multi-panel layout
• Forms are extensive (use progressive disclosure)
• Errors show detailed technical info

System B: Consumer Social App (Playful)

Fixed: Same spacing/grid/accessibility/type logic Project-Specific:

• Colors: Warm greys + vibrant coral
• Typography: Poppins (headlines) + Inter (body)
• Tone: Casual, friendly, playful
• Animation: Moderate, bouncy (200ms)

Adaptable:

• Mobile-first (most users on phones)
• Forms are minimal (progressive profiling)
• Errors are friendly, not technical

System C: Healthcare Platform (Clinical)

Fixed: Same foundational structure Project-Specific:

• Colors: Pure greys + medical blue
• Typography: System fonts (SF Pro / Segoe)
• Tone: Clear, authoritative, calm
• Animation: Slow, smooth (300ms)

Adaptable:

• Desktop-first (clinical use at workstations)
• Forms are complex (HIPAA compliance)
• Errors are precise with next steps

---

KEY TAKEAWAY

The system flexibility framework lets you:

• Maintain consistency (fixed elements)
• Express brand personality (project-specific)
• Adapt to context (adaptable elements)

Without this framework:

• Designers reinvent spacing every project
• Components feel inconsistent across products
• Brand personality overrides accessibility
• Context-blind implementations feel wrong

With this framework:

• Speed: Start from proven foundations
• Consistency: Fixed elements guarantee it
• Flexibility: Express unique brand identity
• Context: Adapt without breaking system

Motion Specification

Motion should surprise and delight while serving function. Animation is a creative tool.

Easing Curves

Duration by Element Weight

Duration by Interaction

Common Patterns

// Hover transition (CSS)
<button className="transition-colors duration-150 ease-out hover:bg-blue-700">

// Fade + slide (Framer Motion)
<motion.div
  initial={{ opacity: 0, y: 20 }}
  animate={{ opacity: 1, y: 0 }}
  transition={{ duration: 0.3, ease: "easeOut" }}
/>

// Stagger children
<motion.ul variants={{ visible: { transition: { staggerChildren: 0.1 } } }}>
  <motion.li variants={{ hidden: { opacity: 0 }, visible: { opacity: 1 } }} />
</motion.ul>

Performance Rules

• Only animate transform and opacity (GPU-accelerated)
• Avoid animating width, height, margin, padding
• Keep durations under 500ms for UI interactions
• Respect prefers-reduced-motion:

@media (prefers-reduced-motion: reduce) {
  *, *::before, *::after {
    animation-duration: 0.01ms !important;
    transition-duration: 0.01ms !important;
  }
}

Resources

• Framer Motion
• CSS Easing Functions

Responsive Design Essentials

Mobile-first approach: start with mobile, progressively enhance for larger screens.

Breakpoints

Tailwind Responsive

// Mobile-first: base styles, then scale up
<div className="
  w-full          // mobile: full width
  sm:w-1/2        // 480px+: half
  md:w-1/3        // 768px+: third
  lg:w-1/4        // 1024px+: quarter
">

// Responsive grid
<div className="grid grid-cols-1 sm:grid-cols-2 lg:grid-cols-3 xl:grid-cols-4 gap-6">

// Responsive typography
<h1 className="text-3xl md:text-4xl lg:text-5xl">

// Show/hide by breakpoint
<div className="block md:hidden">Mobile only</div>
<div className="hidden md:block">Desktop only</div>

Fluid Typography

h1 { font-size: clamp(2rem, 5vw, 4rem); }
p { font-size: clamp(1rem, 2.5vw, 1.25rem); }

Touch Targets

• Minimum 44x44px for all interactive elements
• Use touch-manipulation to prevent 300ms tap delay
• Adequate spacing between targets

<button className="min-w-[44px] min-h-[44px] touch-manipulation">

Mobile Simplification

Images

// Responsive images
<img
  srcSet="image-400w.jpg 400w, image-800w.jpg 800w, image-1200w.jpg 1200w"
  sizes="(max-width: 640px) 100vw, (max-width: 1024px) 50vw, 33vw"
  loading="lazy"
/>

// Next.js
<Image src="/hero.jpg" width={1200} height={600} priority className="w-full h-auto" />

Testing

Test at these widths:

• 375px (iPhone SE)
• 390px (iPhone 14)
• 768px (iPad)
• 1024px (iPad Pro)
• 1280px+ (Desktop)

Resources

• Tailwind Responsive