app-ui-design
The app-ui-design skill provides expert guidance for creating accessible, platform-native mobile app interfaces for iOS and Android. Use this skill when designing app screens, establishing design systems, implementing Material Design 3 or Human Interface Guidelines, ensuring WCAG 2.2 AA accessibility compliance, selecting typography and color schemes, or aligning interfaces with current mobile design trends and best practices.
git clone --depth 1 https://github.com/majiayu000/spellbook /tmp/app-ui-design && cp -r /tmp/app-ui-design/skills/app-ui-design ~/.claude/skills/app-ui-designSKILL.md
# 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
Audit AND optimize a CLAUDE.md / AGENTS.md instruction file — score it against the five high-leverage patterns, flag anti-patterns, then apply approved fixes in place. Use when the user says 优化 CLAUDE.md / 优化 AGENTS.md / optimize my agent doc / 帮我改 claudemd, or after an audit when they want the fixes applied (not just reported).
Generate or update repository-specific AGENTS.md instruction files from real repo evidence. Use when asked to create, design, scaffold, split, or improve root or scoped AGENTS.md files for Codex/Claude/agent workflows, especially when a repo needs directory-specific rules, validation commands, generated-file boundaries, or a short agent onboarding router.
REST/GraphQL/gRPC API design best practices. Use when designing APIs, defining contracts, handling versioning. Covers OpenAPI 3.2, GraphQL Federation, gRPC streaming.
End-to-end app feature inventory and user-story testing workflow with a canonical tracker. Use when the user asks to audit every feature, derive expected behavior from code, test user journeys, or explicitly fix and retest documented UX or logistical defects.
Design architecture foundations before implementation. Use when asked to design or refactor architecture, choose Rust/Go crate, package, module, runtime, workflow, or service boundaries, compare mature project architecture, prevent stacked one-off PRs, audit migration debt in existing repos, or produce a spec before coding.
Evidence-driven architecture research for understanding real systems and making technical decisions. Use when doing architecture landscape studies, source-backed system archaeology, build-vs-buy or adopt/adapt/build decisions, open-source and commercial comparisons, revisiting an earlier architecture choice, or handling requests such as 架构调研, 架构选型, 竞品架构, 技术尽调, 同类方案, 开源替代, how is X built, and what should we learn from X. Do not use for small mechanical changes, market-only discovery, or detailed design after the technology direction is already fixed.
Ask Grok or Gemini via opencli (browser-session based, no API cost). Use when the user says "问 grok", "问 gemini", "ask grok", "ask gemini", "用 grok 查", "grok 怎么看", "让 gemini 分析", or wants a second opinion from Grok/Gemini without paying API tokens. Routes to opencli which drives the already-logged-in Chrome session.
OAuth 2.1 + JWT authentication security best practices. Use when implementing auth, API authorization, token management. Follows RFC 9700 (2025).