frontend-ui-ux-design
Creates comprehensive frontend UI/UX designs including user interfaces, design systems, component libraries, responsive layouts, and accessibility implementations. Produces wireframes, mockups, design specifications, and implementation guidelines. Use when designing user interfaces, creating design systems, building component libraries, implementing responsive designs, ensuring accessibility compliance, or when users mention UI design, UX design, interface design, design systems, user experience, or frontend design patterns.
What this skill does
# Frontend UI/UX Design ## Overview This skill enables creation of production-ready frontend UI/UX designs from research through implementation. Follow a structured design process that balances user needs, business goals, technical constraints, and accessibility requirements. ## Design Workflow ## 1. Understand Requirements **Gather Context:** - Project goals and success metrics - Target audience and user personas - Technical constraints (frameworks, browsers, devices) - Brand guidelines and design language - Accessibility requirements (WCAG level) **Clarify Scope:** - Type of deliverable (wireframes, mockups, design system, component library) - Fidelity level (low, medium, high) - Responsive breakpoints needed - Browser and device support ### 2. Research & Strategy **User Research:** - Analyze user needs, goals, and pain points - Review existing analytics or user feedback - Identify key user journeys and scenarios - Define information architecture **For complete research process**: See [uiux-design-process.md](references/uiux-design-process.md) for detailed research, personas, journey mapping, and information architecture guidelines. ### 3. Design & Prototype **Create Wireframes:** - Start with low-fidelity layouts - Focus on content hierarchy and structure - Define user flows for key tasks - Iterate based on feedback **Apply Visual Design:** - Define color palette (primary, secondary, semantic colors) - Establish typography scale and spacing system - Design components with variants and states - Ensure visual hierarchy and consistency **For design principles**: See [design-principles.md](references/design-principles.md) for visual hierarchy, consistency, simplicity, feedback, and error prevention guidelines. **For design systems**: See [design-systems.md](references/design-systems.md) when building comprehensive design systems with design tokens, governance, and documentation. ### 4. Ensure Accessibility **WCAG Compliance:** - Minimum contrast ratios (4.5:1 for text, 3:1 for large text/UI) - Keyboard navigation support - Screen reader compatibility (semantic HTML, ARIA labels) - Focus indicators and skip links - Alternative text for images **For complete accessibility guidance**: See [accessibility-guide.md](references/accessibility-guide.md) for WCAG 2.1/2.2 standards, ARIA patterns, keyboard navigation, testing tools, and compliance checklists. ### 5. Design Responsive Layouts **Mobile-First Approach:** - Start with mobile design (320px minimum) - Progressively enhance for tablets (768px+) - Optimize for desktop (1024px+, 1440px+) - Use fluid grids and flexible images - Apply appropriate layout patterns **For responsive patterns**: See [responsive-design.md](references/responsive-design.md) for breakpoints, layout patterns (fluid grid, column drop, off-canvas), responsive navigation, typography, images, tables, forms, and container queries. ### 6. Build Component Libraries **Component Design:** - Design atomic components (buttons, inputs, icons) - Create molecule components (form fields, cards, menus) - Build organism components (headers, forms, sections) - Define component variants, states, and props - Document component usage patterns **For component details**: See [component-library.md](references/component-library.md) and [component-patterns.md](references/component-patterns.md) for comprehensive component catalogs with specifications, variants, states, and usage guidelines. ### 7. Optimize Performance **Performance Considerations:** - Optimize images (WebP/AVIF, lazy loading, responsive images) - Minimize CSS/JS bundle sizes - Implement critical CSS for above-the-fold content - Use efficient animations (transform, opacity) - Monitor Core Web Vitals (LCP, FID, CLS) **For optimization details**: See [performance-optimization.md](references/performance-optimization.md) for image optimization, code splitting, caching strategies, and performance budgets. ### 8. Document & Handoff **Design Deliverables:** - Design specifications (colors, typography, spacing) - Component documentation with variants - Responsive breakpoint designs - Accessibility report and compliance checklist - Implementation guidelines and design tokens **For output format**: See [output-format.md](references/output-format.md) for structured deliverable formats including design briefs, wireframes, visual designs, component libraries, and developer handoff materials. ## Quick Reference ### When to Load References - **[uiux-design-process.md](references/uiux-design-process.md)** - Full design process from research through prototyping and user testing - **[design-principles.md](references/design-principles.md)** - Core design principles (hierarchy, consistency, simplicity, feedback) - **[design-systems.md](references/design-systems.md)** - Building comprehensive design systems with tokens and governance - **[accessibility-guide.md](references/accessibility-guide.md)** - WCAG compliance, ARIA patterns, keyboard navigation, testing - **[responsive-design.md](references/responsive-design.md)** - Breakpoints, layout patterns, responsive components - **[component-library.md](references/component-library.md)** - Atomic/molecular component catalog with specifications - **[component-patterns.md](references/component-patterns.md)** - Component patterns (forms, navigation, data display, feedback) - **[performance-optimization.md](references/performance-optimization.md)** - Image optimization, code splitting, Core Web Vitals - **[design-tools-and-resources.md](references/design-tools-and-resources.md)** - Design tools, frameworks, icon libraries, resources - **[output-format.md](references/output-format.md)** - Structured deliverable formats for handoff - **[examples.md](references/examples.md)** - Real-world design examples and patterns - **[design-checklist.md](references/design-checklist.md)** - Quality checklist before finalizing designs ## Key Principles **1. User-Centered Design** - Always start with user needs and goals - Validate assumptions through research and testing - Prioritize usability over aesthetics **2. Accessibility First** - Design for all users, including those with disabilities - Follow WCAG 2.1 AA standards minimum - Test with keyboard navigation and screen readers **3. Mobile-First Responsive** - Start with smallest screen sizes - Progressively enhance for larger screens - Ensure touch-friendly interactions (44x44px minimum) **4. Design System Thinking** - Build reusable, consistent components - Document patterns and usage guidelines - Maintain design token systems **5. Performance Matters** - Optimize images and assets - Keep bundle sizes small - Monitor and improve Core Web Vitals **6. Iterative Process** - Start with low-fidelity, iterate to high-fidelity - Gather feedback early and often - Refine based on user testing and metrics
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.