UI/UX Design
This skill should be used when the user asks about "UI design", "UX design", "user interface", "user experience", "wireframes", "mockups", "design patterns", "design system", "component design", "layout", or mentions UI/UX decisions.
What this skill does
# UI/UX Design
Guidance for user interface and user experience design decisions.
## Core Principles
### Visual Hierarchy
Establish clear importance levels:
1. **Size**: Larger elements draw attention first
2. **Color**: Contrast guides the eye
3. **Spacing**: White space creates groupings
4. **Position**: Top-left reads first (in LTR languages)
### Consistency
- Use consistent spacing scale (4px, 8px, 16px, 24px, 32px, 48px)
- Maintain consistent component patterns
- Follow platform conventions (Material, iOS, Web)
### Feedback
Every action needs feedback:
- **Immediate**: Button press states
- **Progress**: Loading indicators
- **Completion**: Success/error messages
## Layout Patterns
### Card Layout
```
┌─────────────────┐
│ Image │
├─────────────────┤
│ Title │
│ Description │
│ [Action Button] │
└─────────────────┘
```
Use for: Collections, products, articles
### List Layout
```
┌──┬──────────────┐
│##│ Title │
│ │ Subtitle │
└──┴──────────────┘
```
Use for: Settings, navigation, data tables
### Dashboard Layout
```
┌────────┬────────┬────────┐
│ Metric │ Metric │ Metric │
├────────┴────────┴────────┤
│ Main Chart │
├─────────────┬────────────┤
│ Table │ Activity │
└─────────────┴────────────┘
```
## Component Design
### Buttons
| Type | Use Case |
|------|----------|
| Primary | Main action (1 per view) |
| Secondary | Alternative actions |
| Tertiary/Ghost | Low-emphasis actions |
| Destructive | Delete, remove actions |
### Forms
- Label above input (not placeholder-only)
- Show validation inline
- Group related fields
- Mark optional fields, not required
- Provide helpful error messages
### Navigation
- **Top nav**: Global, persistent
- **Side nav**: Complex apps, many sections
- **Bottom nav**: Mobile, 3-5 items max
- **Breadcrumbs**: Deep hierarchies
## Responsive Design
### Breakpoints
```css
/* Mobile first */
/* Default: Mobile (< 640px) */
@media (min-width: 640px) { /* Tablet */ }
@media (min-width: 1024px) { /* Desktop */ }
@media (min-width: 1280px) { /* Large desktop */ }
```
### Adaptation Strategies
- **Stack**: Columns become rows on mobile
- **Hide**: Show/hide elements by importance
- **Resize**: Proportional scaling
- **Reflow**: Different layouts per breakpoint
## Color Usage
### Semantic Colors
| Color | Meaning |
|-------|---------|
| Blue | Primary actions, links |
| Green | Success, positive |
| Yellow/Orange | Warning, attention |
| Red | Error, destructive |
| Gray | Neutral, disabled |
### Contrast Requirements
- Text on background: 4.5:1 minimum (WCAG AA)
- Large text: 3:1 minimum
- Interactive elements: 3:1 minimum
## Typography
### Scale
```
xs: 12px - Labels, captions
sm: 14px - Body small
base: 16px - Body default
lg: 18px - Body large
xl: 20px - Heading small
2xl: 24px - Heading medium
3xl: 30px - Heading large
4xl: 36px - Display
```
### Line Height
- Headings: 1.2 - 1.3
- Body text: 1.5 - 1.6
- UI elements: 1.0 - 1.25
## UX Patterns
### Empty States
Show when no data:
- Friendly illustration
- Explain what goes here
- Provide action to add first item
### Loading States
- Skeleton screens > spinners
- Progressive loading
- Optimistic UI when safe
### Error Handling
- Explain what went wrong
- Suggest how to fix
- Provide recovery action
- Don't blame the user
## Design Checklist
- [ ] Clear visual hierarchy
- [ ] Consistent spacing and alignment
- [ ] Responsive across devices
- [ ] Accessible color contrast
- [ ] Clear interactive states
- [ ] Helpful error messages
- [ ] Loading feedback
- [ ] Empty state design
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.