Ui principles

UI Design Principles

Core principles for building high-quality UI. Reference these when creating components, layouts, and pages.

Spacing System

Use a consistent spacing scale. Never use arbitrary values.

• 4px — tight inner padding (badges, pills)
• 8px — default inner padding, small gaps
• 12px — compact component padding
• 16px — standard component padding, list gaps
• 24px — card padding, medium section gaps
• 32px — large component gaps
• 48px — section padding (mobile)
• 64px — section padding (tablet)
• 80px — section padding (desktop small)
• 120px — section padding (desktop large)

Typography Hierarchy

Every page should have a clear type hierarchy. Never use more than 3-4 font sizes per page.

• Display: 48-72px — hero headlines only
• H1: 36-48px — page titles
• H2: 24-32px — section titles
• H3: 20-24px — card titles, subsections
• Body: 16-18px — paragraph text
• Small: 14px — captions, labels, metadata
• Micro: 12px — badges, overlines

Line height: 1.1-1.2 for headlines, 1.5-1.6 for body text.

Type Rendering (Font Smoothing)

Browsers default to subpixel antialiasing, which renders text heavier and slightly blurrier than design tools show it (Figma uses its own renderer, so what you approved is not what ships). Fix it once, globally:

* {
  -webkit-font-smoothing: antialiased;
  -moz-osx-font-smoothing: grayscale;
}

• macOS only: Windows ClearType ignores both properties. You're fixing the platform where the Figma-to-browser delta is most visible.
• No layout impact: glyph widths, line breaks, and spacing stay identical. Purely how edges meet the pixel grid.
• Most visible on dark backgrounds, where subpixel rendering is at its heaviest.
• The catch: grayscale rendering removes visual weight from letterforms. Don't go below font-weight: 400 at small sizes, and bump weight up as size goes down — what reads fine at 400 on 16px needs a bump at 12px to hold the same presence.
• Font format is irrelevant here: WOFF2/OTF/TTF rasterize identically. Use WOFF2 for file size, not rendering.

Layout Rules

• Max content width: 1200-1280px
• Text max-width: 640-720px for readability
• Use 12-column grid for desktop, collapse to 4 for mobile
• Cards: consistent padding, consistent radius, consistent shadow
• Sections: alternate between full-width and contained widths for rhythm
• Always group related elements with less space than unrelated elements (proximity principle)

Visual Hierarchy

• One primary action per section (single CTA)
• Use size, weight, and color to establish 3 levels: primary, secondary, tertiary
• Dark backgrounds for emphasis sections, light for breathing room
• Icons support text, never replace it (except established patterns like search, close, menu)

Color Systems

• Prefer OKLCH/OKLab for palette and gradient work when the stack supports it.
• Build color ramps around real roles: background, surface, border, text, muted text, accent, danger, success.
• Check contrast on every text/background pair before shipping.
• Keep accent colors scarce; one strong accent usually beats several competing accents.
• Use gradients for gradient-heavy work and swiss-design or another design-system skill when the user requests a specific visual language.

Component Patterns

• Buttons: minimum 44px height for touch, 12-24px horizontal padding, never less than 80px wide
• Cards: consistent internal structure (image/icon → title → description → action)
• Inputs: minimum 44px height, visible labels (not just placeholder), clear focus states
• Navigation: logo left, links center or right, CTA far right

Responsive

• Design desktop-first for marketing sites, mobile-first for apps
• Breakpoints: 640px (mobile), 768px (tablet), 1024px (desktop), 1280px (wide)
• Stack horizontal layouts vertically on mobile
• Reduce section padding by ~40% on mobile
• Headlines scale down 1-2 steps on mobile

Common Mistakes to Avoid

• Inconsistent spacing (mixing 15px and 16px)
• Too many font sizes on one page
• Buttons that look like links and links that look like buttons
• Sections with no breathing room between them
• Text over images without sufficient contrast/overlay
• Centering everything — left-align body text

AI Slop Detection

Generated UI has recognizable tells. If you spot these patterns, you're probably producing generic output instead of intentional design. Fix or remove them:

• Gratuitous gradients — purple-to-blue or teal-to-cyan backgrounds with no design rationale
• Glassmorphism everywhere — frosted glass cards with backdrop-blur used as a default style, not a deliberate choice
• Generic hero layout — centered text over a stock gradient with a "Get Started" button and no real content hierarchy
• Decoration over function — floating blobs, animated mesh backgrounds, glow effects that don't support the content
• Same component repeated 3x — three feature cards, three pricing tiers, three testimonials, all identical structure with placeholder-quality copy
• Over-rounded everything — rounded-2xl or rounded-3xl on every surface with no variation
• Default shadow stack — shadow-lg on cards, shadow-xl on modals, no thought about elevation system

The fix is always the same: ask what the design is trying to communicate, then choose the simplest visual treatment that achieves it.

Fluid Scale (Tailwind Config)

Map fluid clamp() values into Tailwind so you use utilities, not raw CSS:

// tailwind.config.ts
export default {
  theme: {
    extend: {
      fontSize: {
        'fluid-sm':  'clamp(0.875rem, 0.5vw + 0.75rem, 1rem)',
        'fluid-base': 'clamp(1rem, 1vw + 0.75rem, 1.25rem)',
        'fluid-lg':  'clamp(1.25rem, 2vw + 0.75rem, 2rem)',
        'fluid-xl':  'clamp(1.5rem, 3vw + 0.75rem, 3rem)',
        'fluid-2xl': 'clamp(2rem, 5vw + 1rem, 4rem)',
        'fluid-hero': 'clamp(2.5rem, 6vw + 1rem, 5rem)',
      },
      spacing: {
        'fluid-xs': 'clamp(0.25rem, 0.5vw, 0.5rem)',
        'fluid-s':  'clamp(0.5rem, 1vw, 0.75rem)',
        'fluid-m':  'clamp(1rem, 2vw + 0.5rem, 2rem)',
        'fluid-l':  'clamp(1.5rem, 4vw + 0.5rem, 4rem)',
        'fluid-xl': 'clamp(2rem, 6vw + 1rem, 8rem)',
        'fluid-2xl': 'clamp(3rem, 10vw + 1rem, 12rem)',
      },
    },
  },
}

Always combine rem + vw in the preferred value. Pure vw doesn't scale when users zoom to 200%.

Viewport Units

Unit	Browser UI state	Use for
svh	Fully expanded (smallest)	Default. hero sections, modals, anything that must fit on load
lvh	Fully retracted (largest)	Backgrounds, decorative elements
dvh	Dynamic, updates on scroll	Sparingly. chat interfaces, overlays tracking exact visible space

Always provide a fallback: height: 100vh; height: 100svh;. Avoid dvh for primary layout.

Touch, Hover, Motion

Touch targets (in globals.css inside @layer base):

@media (pointer: coarse) {
  button, a, [role="button"] { min-height: 44px; min-width: 44px; }
}

Hover gating for transforms:

@media (hover: hover) and (pointer: fine) {
  .hover-lift:hover { transform: translateY(-4px); }
}

Reduced motion with Tailwind:

<div className="motion-safe:animate-fade-in motion-reduce:animate-none">

Pretext (Text Measurement)

Use Pretext (bun add @chenglou/pretext) when layout depends on text height: virtualized lists, masonry, shrink-wrapping chat bubbles, text flowing around obstacles.

import { prepare, layout } from '@chenglou/pretext'
const prepared = prepare('Your text here', '16px Inter')  // one-time, expensive
const { height, lineCount } = layout(prepared, width, 24) // cheap, call on every resize

Use a named font, not system-ui. The font string must match your CSS exactly.