app-ui-design▌
majiayu000/claude-arsenal · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Expert guidance for designing beautiful, accessible, and platform-native mobile app interfaces following 2025 best practices.
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.
❌ 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.
❌ 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.
❌ 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.
❌ 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
## 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
## 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
## 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
## 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
## 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 expressive typography
- Rounded, approachable shapes
### Component Shapes
- Extra Small: 4dp
- Small: 8dp
- Medium: 12dp
- Large: 16dp
- Extra Large: 28dp
- Full: 50% (pills/circles)
### Standard Dimensions
- App bar height: 64dp
- Bottom navigation height: 80dp
- FAB size: 56dp (standard), 40dp (small), 96dp (large)
2025 Design Trends
AI-Driven Personalization
## Adaptive UI Patterns
### Personalization Strategies
- Content recommendations based on behavior
- Adaptive UI layouts based on usage patterns
- Smart defaults and predictive actions
- Contextual feature suggestions
### Implementation Guidelines
- Always provide manual override options
- Explain why content is recommended
- Respect user privacy preferences
- Gradual personalization (don't overwhelm new users)
Dark Mode Excellence
## Dark Mode Best Practices
### Color Adaptation
Light Mode → Dark Mode
White (#FFFFFF) → Dark gray (#121212)
Black (#000000) → White (#FFFFFF)
Primary (vibrant) → Primary (desaturated)
Shadows → Subtle shadows or none
### Surface Elevation (Material 3)
Elevation 0 → #121212
Elevation 1 → #1E1E1E (+ 5% white overlay)
Elevation 2 → #232323 (+ 7% white overlay)
<How to use app-ui-design on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add app-ui-design
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches app-ui-design from GitHub repository majiayu000/claude-arsenal and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate app-ui-design. Access the skill through slash commands (e.g., /app-ui-design) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.8★★★★★47 reviews- ★★★★★Chaitanya Patil· Dec 28, 2024
Solid pick for teams standardizing on skills: app-ui-design is focused, and the summary matches what you get after install.
- ★★★★★Meera Dixit· Dec 16, 2024
app-ui-design is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Sophia Abebe· Dec 12, 2024
Registry listing for app-ui-design matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Kwame Torres· Dec 8, 2024
Solid pick for teams standardizing on skills: app-ui-design is focused, and the summary matches what you get after install.
- ★★★★★Kwame Huang· Nov 27, 2024
We added app-ui-design from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Piyush G· Nov 19, 2024
We added app-ui-design from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Arya Thomas· Nov 19, 2024
app-ui-design reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Dev Jackson· Nov 7, 2024
Useful defaults in app-ui-design — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Arya Tandon· Oct 26, 2024
I recommend app-ui-design for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Sophia Diallo· Oct 18, 2024
app-ui-design fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 47