app-ui-design
Mobile app UI design expert for iOS and Android. Use when designing app interfaces, creating design systems, ensuring accessibility, or following platform guidelines. Covers Material Design 3, Human Interface Guidelines, color theory, typography, and 2025 trends.
What this skill does
# Mobile App UI Design > Expert guidance for designing beautiful, accessible, and platform-native mobile app interfaces following 2025 best practices. ## Core Philosophy - **User-First Design** — Prioritize user needs, behaviors, and mental models over aesthetics - **Platform Consistency** — Follow iOS HIG and Android Material Design guidelines - **Accessibility as Foundation** — Design for all users from the start, not as an afterthought - **Emotional Intelligence** — Create interfaces that users emotionally connect with - **Performance-Conscious** — Beautiful design that doesn't sacrifice app performance --- ## Hard Rules (Must Follow) > These rules are mandatory. Violating them means the skill is not working correctly. ### Accessibility First **All designs must meet WCAG 2.2 AA standards. Accessibility is not optional.** ```markdown ❌ FORBIDDEN: - Color contrast below 4.5:1 for text - Touch targets smaller than 44×44pt (iOS) or 48×48dp (Android) - Information conveyed by color alone - Missing alternative text for images - Non-keyboard-navigable interfaces ✅ REQUIRED: - Minimum 4.5:1 contrast ratio for normal text - Minimum 3:1 contrast ratio for large text (18pt+) - Touch targets: 44×44pt (iOS) / 48×48dp (Android) - Support for Dynamic Type / Font Scaling - VoiceOver (iOS) / TalkBack (Android) compatibility - Clear focus indicators for keyboard navigation ``` ### Platform Guidelines Adherence **Follow platform-specific design guidelines. Do not mix iOS and Android patterns.** ```markdown ❌ FORBIDDEN: - Using Android-style FAB on iOS - Using iOS-style bottom sheets on Android without adaptation - Mixing platform navigation patterns - Ignoring platform typography (SF Pro vs Roboto) ✅ REQUIRED: iOS (Human Interface Guidelines): - Use SF Pro font family - Tab bar at bottom for primary navigation - Push navigation with back chevron - Standard iOS controls (UIKit/SwiftUI) Android (Material Design 3): - Use Roboto font family - Bottom navigation bar or navigation drawer - Material components with ripple effects - Follow Material You dynamic theming ``` ### Consistent Design System **Every app must have a documented design system with tokens.** ```markdown ❌ FORBIDDEN: - Ad-hoc colors and spacing values - Inconsistent button styles across screens - Multiple unnamed font sizes - Components without defined states ✅ REQUIRED: Design System Must Include: ├── Color Tokens (primary, secondary, surface, error, etc.) ├── Typography Scale (heading1-6, body, caption, etc.) ├── Spacing Scale (4, 8, 12, 16, 24, 32, 48px) ├── Border Radius Tokens (none, sm, md, lg, full) ├── Shadow/Elevation Tokens (elevation1-5) └── Component Library (button, input, card, etc.) ``` ### Touch-Friendly Design **All interactive elements must be optimized for touch interaction.** ```markdown ❌ FORBIDDEN: - Touch targets smaller than minimum size - Interactive elements too close together (<8px gap) - Important actions outside thumb reach zone - Hover-dependent interactions ✅ REQUIRED: - Minimum touch target: 44×44pt (iOS) / 48×48dp (Android) - Minimum spacing between targets: 8px - Primary actions in thumb-friendly zone (bottom 2/3) - Clear tap feedback (ripple, highlight, scale) ``` --- ## Quick Reference ### When to Use What | Scenario | Approach | Key Considerations | |----------|----------|-------------------| | New app design | Start with design system | Define tokens before screens | | iOS-only app | Human Interface Guidelines | SF Pro, standard iOS patterns | | Android-only app | Material Design 3 | Roboto, Material components | | Cross-platform app | Adaptive design | Platform-specific navigation | | Redesign existing app | Audit first | Maintain mental models | | Accessibility review | WCAG 2.2 AA checklist | Contrast, touch targets, labels | --- ## Design System Fundamentals ### Color System ```markdown ## Color Token Structure ### Semantic Colors primary → Main brand color, CTAs primary-variant → Darker/lighter primary for states secondary → Secondary actions, accents background → App background surface → Card backgrounds, elevated surfaces error → Error states, destructive actions on-primary → Text/icons on primary color on-background → Text/icons on background on-surface → Text/icons on surface ### Color Palette (60-30-10 Rule) 60% → Neutral/background colors 30% → Secondary/supporting colors 10% → Accent/primary colors ### Dark Mode Considerations - Don't just invert colors - Use desaturated colors for dark surfaces - Reduce contrast slightly (avoid pure white on black) - Maintain color meaning across modes ``` ### Typography Scale ```markdown ## Mobile Typography Guidelines ### iOS Typography (SF Pro) Large Title → 34pt, Bold Title 1 → 28pt, Bold Title 2 → 22pt, Bold Title 3 → 20pt, Semibold Headline → 17pt, Semibold Body → 17pt, Regular Callout → 16pt, Regular Subhead → 15pt, Regular Footnote → 13pt, Regular Caption 1 → 12pt, Regular Caption 2 → 11pt, Regular ### Android Typography (Roboto / Material 3) Display Large → 57sp Display Medium → 45sp Display Small → 36sp Headline Large → 32sp Headline Medium→ 28sp Headline Small → 24sp Title Large → 22sp Title Medium → 16sp, Medium Title Small → 14sp, Medium Body Large → 16sp Body Medium → 14sp Body Small → 12sp Label Large → 14sp, Medium Label Medium → 12sp, Medium Label Small → 11sp, Medium ### Best Practices - Maximum 2-3 font families per app - Minimum body text: 16px (14px absolute minimum) - Line height: 1.4-1.6× font size for body text - Support Dynamic Type (iOS) / Font Scaling (Android) ``` ### Spacing System ```markdown ## 8-Point Grid System Base Unit: 8px ### Spacing Scale spacing-0 → 0px spacing-1 → 4px (half unit) spacing-2 → 8px (1 unit) spacing-3 → 12px (1.5 units) spacing-4 → 16px (2 units) spacing-5 → 24px (3 units) spacing-6 → 32px (4 units) spacing-7 → 48px (6 units) spacing-8 → 64px (8 units) ### Component Spacing Button padding → 12px vertical, 24px horizontal Card padding → 16px List item padding → 16px horizontal, 12px vertical Section spacing → 24px-32px Screen edge margin → 16px (phones), 24px (tablets) ### Touch Target Spacing Minimum gap between interactive elements: 8px Recommended gap: 12-16px ``` --- ## Platform Guidelines ### iOS Human Interface Guidelines ```markdown ## iOS Design Principles ### Core Principles 1. Clarity → Text legible, icons precise, purpose obvious 2. Deference → UI helps understanding, not competing with content 3. Depth → Visual layers and realistic motion convey hierarchy ### Navigation Patterns - Tab Bar (bottom) → 3-5 primary destinations - Navigation Bar (top) → Title, back button, actions - Modal sheets → Temporary focused tasks - Popovers (iPad) → Contextual options ### 2025 Updates: Liquid Glass - Translucent materials for controls - Floating navigation elements - Dynamic depth and hierarchy - Background blur effects ### Safe Areas - Top: Status bar + Dynamic Island/Notch - Bottom: Home indicator (34pt on Face ID devices) - Use safeAreaInsets for proper content placement ### Standard Dimensions - Navigation bar height: 44pt (96pt with large title) - Tab bar height: 49pt (83pt on Face ID devices) - Toolbar height: 44pt ``` ### Android Material Design 3 ```markdown ## Material Design 3 Principles ### Core Concepts 1. Material You → Personal, adaptive, dynamic color 2. Expressiveness → Emotional connection through design 3. Accessibility → Inclusive design for all users ### Navigation Patterns - Bottom Navigation → 3-5 primary destinations - Navigation Drawer → 5+ destinations or secondary nav - Navigation Rail → Tablets and large screens - Top App Bar → Title, navigation, actions ### Material 3 Expressive (2025) - Dynamic color from user wallpaper - Springy, physics-based motion - Bolder, more ex
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.