design-guide
Ensures modern, professional UI design across SwiftUI, Android, and web platforms. Use when building ANY user interface components including buttons, forms, cards, layouts, navigation, or complete screens. Enforces clean minimal design, neutral color palettes with one accent color, 8px grid spacing system, proper typography hierarchy, and clear interactive states. Always reference before creating or modifying UI elements.
What this skill does
# Design Guide Comprehensive design system ensuring every UI you build looks modern, professional, and consistent across all platforms (SwiftUI, Android Studio, web applications). ## Bundled Resources This skill includes additional reference materials: - **references/color-palettes.md** - Detailed color schemes, accent color options, and platform-specific color implementation examples. Reference when choosing or implementing colors. - **references/component-templates.md** - Ready-to-use code templates for buttons, cards, forms, and navigation across SwiftUI, Android Compose, and React. Reference when implementing specific components. ## Core Design Principles ### 1. Clean and Minimal - Embrace white space generously - Avoid cluttered interfaces - One primary action per screen/section - Remove unnecessary decorative elements - Let content breathe ### 2. Color Palette **Neutral Base:** - Use grays and off-whites as foundation - White: #FFFFFF - Light gray: #F5F5F5, #EEEEEE - Medium gray: #9E9E9E, #757575 - Dark gray: #424242, #212121 - True black sparingly: #000000 **Accent Color:** - Choose ONE accent color for your app - Use sparingly for CTAs, important actions, and key information - Good accent options: Emerald (#10B981), Indigo (#6366F1), Rose (#F43F5E), Amber (#F59E0B) - **NEVER use generic purple/blue gradients** **Color Usage Rules:** - 80% neutral, 15% secondary neutral, 5% accent - Backgrounds: light grays or white - Text: dark grays on light backgrounds - Interactive elements: accent color - Borders/dividers: very light gray (#E5E5E5) ### 3. Spacing System (8px Grid) **Always use multiples of 8:** - 8px: Tight spacing (icon padding, inline elements) - 16px: Standard spacing (button padding, form field gaps) - 24px: Section spacing (card internal padding) - 32px: Component spacing (between cards, sections) - 48px: Major section breaks - 64px: Screen-level spacing (margins) **Application:** - Padding: 16px or 24px for most containers - Margins: 32px between major sections - Gap between elements: 16px standard, 8px for tight groups - Never use arbitrary values like 13px or 27px ### 4. Typography **Hierarchy:** - H1: 32px - 40px, bold, rare (page titles only) - H2: 24px - 28px, semibold (section headers) - H3: 20px - 24px, semibold (subsections) - Body: 16px - 18px, regular (MINIMUM 16px for readability) - Small: 14px, regular (captions, metadata) - Tiny: 12px, regular (legal text only, use rarely) **Font Rules:** - Maximum 2 font families per project - One for headings (can be display font) - One for body text (must be highly readable) - Recommended pairings: - Inter + Inter (single family, different weights) - SF Pro Display + SF Pro Text (Apple platforms) - Roboto + Roboto (Android) - System fonts always acceptable **Line Height:** - Headings: 1.2 - 1.3 - Body: 1.5 - 1.6 - Small text: 1.4 ### 5. Shadows **Subtle, not heavy:** - Small shadow: `0 1px 3px rgba(0,0,0,0.12)` - Medium shadow: `0 4px 6px rgba(0,0,0,0.1)` - Large shadow: `0 10px 15px rgba(0,0,0,0.1)` - Floating shadow: `0 20px 25px rgba(0,0,0,0.1)` **When to use:** - Cards: subtle shadow or border, not both - Buttons: very subtle shadow on hover - Modals/dialogs: medium shadow - Dropdowns: medium shadow - **Avoid:** heavy drop shadows, inner shadows, multiple shadows ### 6. Rounded Corners **Border Radius Guidelines:** - Small elements (buttons, inputs): 6px - 8px - Cards, containers: 8px - 12px - Large panels: 12px - 16px - Circular (avatars, icon buttons): 50% or 9999px **Don't overdo it:** - Not everything needs rounded corners - Sharp corners acceptable for: - Screen edges - Full-width sections - Data tables - Navigation bars ### 7. Interactive States **Every interactive element MUST have:** **Buttons:** - Default: base color, subtle shadow - Hover: slightly darker (10%), lift shadow - Active: pressed appearance, darker (20%) - Disabled: 40% opacity, no hover, no pointer cursor - Focus: visible outline (2px accent color, 2px offset) **Form Fields:** - Default: light gray border (#E5E5E5) - Focus: accent color border (2px), remove shadow - Error: red border, error text below - Disabled: gray background, no interaction - Valid: subtle green checkmark (optional) **Links:** - Default: accent color, underline on hover - Visited: slightly muted accent - Never: blue #0000FF (unless that's your accent) **Cards:** - Default: subtle shadow or border - Hover: lift effect, slightly stronger shadow - Active: immediate feedback ### 8. Mobile-First Thinking **Always design for mobile first, then scale up:** - Touch targets minimum 44x44px (iOS), 48x48px (Android) - Adequate spacing between tappable elements (min 8px) - Thumb-friendly navigation (bottom of screen) - Single column layouts on mobile - Responsive breakpoints: - Mobile: < 640px - Tablet: 640px - 1024px - Desktop: > 1024px ## Component Patterns ### Buttons **Primary Button (main action):** ``` Background: Accent color Text: White Padding: 12px 24px (vertical, horizontal) Border radius: 8px Shadow: 0 1px 3px rgba(0,0,0,0.12) Font: 16px, semibold Hover: Darken 10%, lift shadow ``` **Secondary Button (alternative action):** ``` Background: White Text: Accent color Border: 1px solid accent color Padding: 12px 24px Border radius: 8px Hover: Light accent background (10% opacity) ``` **Ghost Button (tertiary action):** ``` Background: Transparent Text: Dark gray No border Padding: 12px 24px Hover: Light gray background ``` **Bad Button Examples:** - ❌ Gradient backgrounds - ❌ Multiple colors in one button - ❌ Tiny padding (looks cramped) - ❌ No hover state - ❌ Text too small (< 14px) ### Cards **Standard Card:** ``` Background: White Border: 1px solid #E5E5E5 OR subtle shadow (not both) Border radius: 12px Padding: 24px Margin bottom: 16px OR Background: White Shadow: 0 4px 6px rgba(0,0,0,0.1) Border radius: 12px Padding: 24px Margin bottom: 16px ``` **Card Content Spacing:** - Title to subtitle: 8px - Subtitle to content: 16px - Content sections: 24px - Content to actions: 24px **Bad Card Examples:** - ❌ Both border AND shadow - ❌ Heavy shadows - ❌ Inconsistent padding - ❌ Too many colors ### Forms **Form Field:** ``` Label: 14px, semibold, dark gray, margin bottom 8px Input: - Height: 44px minimum - Padding: 12px 16px - Border: 1px solid #E5E5E5 - Border radius: 8px - Background: White - Font: 16px - Focus: Accent border, no shadow Error state: - Border: Red - Helper text: Red, 14px, margin top 4px Field spacing: 24px between fields ``` **Form Layout:** - Labels above inputs (not beside) - Clear required indicators - Group related fields - Adequate spacing (24px minimum) - Submit button: full width on mobile, auto on desktop **Bad Form Examples:** - ❌ Labels inside inputs (placeholder text is not a label) - ❌ Tiny text (< 16px) - ❌ Cramped spacing - ❌ No error states - ❌ Unclear required fields ### Navigation **Top Navigation:** ``` Height: 64px Background: White Border bottom: 1px solid #E5E5E5 Padding: 0 32px (desktop), 0 16px (mobile) Logo: 32px height Links: 16px, medium weight, dark gray Active link: Accent color ``` **Bottom Navigation (Mobile):** ``` Height: 56px Background: White Shadow: 0 -4px 6px rgba(0,0,0,0.1) Icons: 24px, centered Labels: 12px (optional) Active: Accent color ``` ## Design Quality Checklist Before considering any UI complete, verify: **Layout:** - [ ] Adequate white space throughout - [ ] Consistent spacing using 8px grid - [ ] Not cluttered or cramped - [ ] Clear visual hierarchy **Colors:** - [ ] Neutral base colors (grays/whites) - [ ] Only ONE accent color - [ ] NO gradients (unless specifically requested) - [ ] Sufficient contrast (WCAG AA minimum) **Typography:** - [ ] Clear hierarchy (size + weight) - [ ] Body text minimum 16px - [ ] Maximum 2 font families - [ ] Readable line heights **Interactive Elements:** - [ ] Clear hover states - [ ] Clear active states - [ ] Clear disabled states - [ ] Clear
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.