ui-ux-design
Modern UI/UX design principles, patterns, and best practices for web and mobile applications. Use when building user interfaces, designing layouts, choosing color palettes, implementing responsive design, ensuring accessibility (WCAG), or creating beautiful modern applications. Includes 2026 design trends, Tailwind CSS patterns, Shadcn/ui integration, micro-interactions, and mobile-first responsive design.
What this skill does
# UI/UX Design --- ## When to Use This Skill Activate this skill when: - Building or designing web/mobile interfaces - Choosing colors, typography, or layout systems - Implementing responsive design (mobile-first) - Ensuring accessibility compliance (WCAG 2.2) - Setting up Shadcn/ui + Tailwind CSS projects - Creating micro-interactions and animations - Reviewing UI/UX decisions before coding --- ## Core Design Principles ### 1. Mobile-First Always - Start with 320px width (smallest phone) - Breakpoints: 576px (phone), 768px (tablet), 992px (laptop), 1200px (desktop) - Single-column default, expand only when space allows ### 2. Visual Hierarchy Guide user attention using: - **Size:** Larger = more important - **Color:** Bright/contrasting = attention - **Whitespace:** More space = emphasis - **Proximity:** Related items grouped together - **Contrast:** Dark on light or light on dark (4.5:1 minimum for text) ### 3. Whitespace is Your Weapon - Space elements in multiples of 8px (8, 16, 24, 32, 48, 64) - Breathing room between sections: 48-64px minimum - Padding inside cards: 24-32px --- ## Quick Reference ### Color System Build a primary color scale (50-900): - **Primary:** Brand color (CTAs, links, active states) - **Neutrals:** Grays 50-900 (text, backgrounds, borders) - **Semantic:** Success (green), Error (red), Warning (yellow/orange) Tools: Huevy.app, Coolors.co, Adobe Color ### Typography Scale (8px baseline) ``` text-xs: 12px / 16px line-height text-sm: 14px / 20px text-base: 16px / 24px (body default) text-lg: 18px / 28px text-xl: 20px / 28px text-2xl: 24px / 32px text-3xl: 30px / 36px (section headers) text-4xl: 36px / 40px text-5xl: 48px / 1 (hero titles) ``` **Font pairing:** 2 fonts max (sans-serif for UI, optional serif for headings) ### Layout Patterns - **CSS Grid:** 2D layouts (page structure) - **Flexbox:** 1D layouts (component internals) - **Auto-fit grid:** `repeat(auto-fit, minmax(280px, 1fr))` (no media queries!) ### Micro-Interactions - **Hover:** Scale 1.05x (buttons feel clickable) - **Click:** Scale 0.95x (tactile feedback) - **Duration:** 0.2-0.3s max (keep it subtle) - **Animate only:** `transform` and `opacity` (GPU accelerated) ### Accessibility (WCAG 2.2) - **Text contrast:** 4.5:1 minimum (normal text), 3:1 (large text) - **UI components:** 3:1 contrast minimum - **Keyboard navigation:** Tab order logical, focus states visible (3:1 contrast) - **ARIA labels:** Always provide for buttons, images, interactive elements --- ## Shadcn/ui + Tailwind Stack ### Setup (Next.js) ```bash npx create-next-app@latest project-name --typescript --tailwind --app cd project-name npx shadcn@latest init ``` Choose: Style (Default), Base color (Blue or custom), CSS variables (Yes) ### Adding Components ```bash npx shadcn@latest add button npx shadcn@latest add card npx shadcn@latest add dialog npx shadcn@latest add calendar ``` Components appear in `components/ui/` — you own the code, customize freely. ### Tailwind Best Practices - Use design tokens (not arbitrary values): `p-4` not `p-[17px]` - Responsive utilities: `w-full md:w-1/2 lg:w-1/3` - Dark mode: `dark:bg-gray-900 dark:text-white` --- ## Pre-Build Checklist Before writing code, confirm: - [ ] Color palette defined (primary + neutrals + semantic colors) - [ ] Typography scale chosen (6-8 sizes) - [ ] Component library picked (Shadcn + Tailwind) - [ ] Mobile breakpoints planned (576px, 768px, 992px) - [ ] Accessibility contrast ratios checked (4.5:1 text, 3:1 UI) - [ ] Micro-interaction list (hover, click, success states) - [ ] Grid layout sketched (mobile → desktop progression) --- ## Inspiration Sources **Study these products:** - Linear (linear.app) — Best keyboard-first UI, subtle animations - Stripe Dashboard — Clean data visualization, perfect spacing - Vercel — Minimalist, fast, modern gradients - Notion — Intuitive drag-and-drop, clear hierarchy **Tools:** - Figma (mockups before coding) - WebAIM Contrast Checker (accessibility) - Coolors/Huevy (color palettes) --- ## The 5 Laws of Beautiful UI 1. **Contrast creates hierarchy** (big vs small, dark vs light) 2. **Whitespace creates calm** (never fear empty space) 3. **Consistency builds trust** (same patterns repeated) 4. **Feedback confirms action** (animations, success messages) 5. **Accessibility includes everyone** (contrast, keyboard, screen readers) --- ## Full Reference For comprehensive deep-dives (component patterns, animation examples, responsive grid techniques), see `UI_UX_MASTER_GUIDE.md` in this skill directory. --- **Last Updated:** 2026-02-05
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.