mobile-app-ui-design
Skill0 starsChanged 28 days agoMITView on GitHub
Design high-quality mobile app UI/UX screens, flows, and components. Use this skill whenever the user asks to design a mobile app screen, create app mockups, build mobile UI components, improve an existing mobile app design, create onboarding flows, design mobile navigation, or requests any mobile-first interface work. Also trigger when the user mentions app design, mobile UI, mobile UX, screen design, app mockups, wireframes, or wants to build React Native / Flutter / SwiftUI style interfaces as visual prototypes. Even if the user just says 'design an app' or 'make this screen look better', use this skill. 设计高质量移动应用UI/UX界面、流程和组件。适用于App界面设计、原型、组件、引导流程、导航设计。触发词:App设计, 移动UI, 移动端设计, App原型, 界面设计, 引导页设计, 移动导航, React Native设计, Flutter设计.
7 other projects use a version of this, 5 of them edited.
Adopted by
Most recently taken up by
- podo/design-agent-skillstheir own version, first seen Nov 8, 2026
- ceorkm/mobile-app-ui-designedited, first seen Oct 28, 2026
- jasonfesta/design-agentstheir own version, first seen Oct 15, 2026
- ZeroTokenClaw/agents-skillsedited, first seen Sep 21, 2026
- sync-buzz/syncedited, first seen Sep 17, 2026
- FkennedyFox/claude-skillsedited, first seen Sep 8, 2026
Used with
Projects with it also use web-design-guidelines.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
VercelSkillweb-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
Also in 3 projects that use this
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 5
- ceorkm/mobile-app-ui-design★ 48597% same
- sync-buzz/sync★ 7100% same
- br3eze-code/br3eze-code★ 3100% same
- ZeroTokenClaw/agents-skills★ 1100% same
- FkennedyFox/claude-skills★ 0100% same
Wrote their own version · 2
- podo/design-agent-skills★ 32same name
- jasonfesta/design-agents★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository33 other files it gives its agents.
- ad-creativeSkill
- adsSkill
- ai-writing-detectorSkill
- boxim-release-assistantSkill
- business-toolboxSkill
- codebase-analyzerSkill
- code-quality-reviewSkill
- code-to-prdSkill
- context-modeSkill
- conversational-ai-dev-workflowSkill
- copywritingSkill
- croSkill
- design-taste-frontendSkill
- diagram-designSkill
- douyin-to-feishu-archiverSkill
- github-tech-optimizerSkill
- git-safety-guardSkill
- gsap-scroll-landingSkill
- image-to-codeSkill
- inverse-thinking-content-creatorSkill
- ios-ui-ux-devSkill
- perfection-loopSkill
- project-finishing-workflowSkill
- rea-reverse-engineeringSkill
- reverse-engineering-suiteSkill
- site-launch-checklistSkill
- skill-forgeSkill
- skill-installerSkill
- socialSkill
- uniapp-multi-platform-auditSkill
- uniapp-release-notesSkill
- video-content-extractionSkill
- wechat-article-htmlSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
38 rules. 37 are common, 0 are distinctive, and 1 is very specific to this project.
37
Common
Most of the 7 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 14
Before designing anything, understand three things:
- Common: line 21
Follow this sequence for any mobile screen:
- Common: line 32
Place primary actions in the thumb zone (bottom 1/3 of screen)
- Common: line 33
Follow the F-pattern reading order for content layout
- Common: line 39
Follow these rules in order:
- Common: line 42
Use one font family (two max, with clear hierarchy purpose)
- Common: line 44
Use monospace variants for large numbers (prices, stats, metrics)
- Common: line 45
Keep text containers under 600px wide for readability
- Common: line 46
Create hierarchy with size, weight, and opacity — not just bold everything
- Common: line 52
Use opacity variations of the neutral color for text hierarchy: 100% for headings, 80% for body, 60-70% for secondary text
- Common: line 53
Use the accent color at 5% opacity for secondary buttons and subtle card highlights
- Common: line 58
All spacing values must be divisible by 8 or 4 (8, 12, 16, 24, 32, 48, 64, 80, 96)
- Common: line 59
Use relationship-based spacing: related elements closer together, unrelated further apart
- Common: line 66
Always use soft shadows — never harsh/distinct
- Common: line 68
Use subtle white inner shadows on buttons to add dimension
- Common: line 69
Add faded drop shadows for depth without heaviness
- Common: line 72
Use icons, emojis, illustrations, and images to make information digestible
- Common: line 75
Keep visual style consistent across the entire app — no random stock photo mix
- Common: line 76
Use AI-generated or curated visuals with matching color palettes
- Common: line 84
Add emotional feedback loops: success states should feel rewarding (bounce, glow, sparkle)
- Common: line 86
Use motion and animation as trust signals, especially in high-stakes domains (finance, crypto, health)
- Common: line 89
Add subtle glow effects behind key elements (blur + opacity)
- Common: line 90
Use tiny white inner shadows on primary buttons
- Common: line 91
Add 5% opacity primary-color borders on secondary elements
- Common: line 92
Consider micro-animations for state changes
- Common: line 93
Ensure all tap targets are at least 44×44pt
- Common: line 94
Check contrast ratios for accessibility
- Common: line 105
Never show a blank search screen.
- Common: line 113
Use visual timelines instead of text-based date lists
- Common: line 116
Use color-coded cards with soft backgrounds and clean isolated images
- Common: line 117
Ensure visual consistency across all category items
- Common: line 118
Create rhythm in the layout for effortless scanning
- Common: line 139
When building these designs as React artifacts or HTML:
- Common: line 140
Use Tailwind CSS utility classes for spacing, colors, and typography
- Common: line 141
Import Lucide React for clean, consistent iconography
- Common: line 142
Use Recharts for any data visualization
- Common: line 144
Use CSS variables for the color system
- Very specific: line 146
Use rounded-2xl or rounded-3xl for modern card aesthetics
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Mobile App UI/UX Design Skill
This skill guides the creation of professional, polished mobile app interfaces that follow proven design principles used by top-tier apps like Airbnb, Duolingo, Spotify, Revolut, and Phantom.
Core Philosophy
Great mobile UI isn't about flashiness — it's about intentionality. Every pixel, every spacing value, every color choice should serve the user. The goal is to create interfaces that feel smooth, personal, and alive — not just functional.
Before designing anything, understand three things:
- What is the user trying to accomplish? (reduce friction to that goal)
- How should this make the user feel? (trust, delight, confidence, calm)
- What's the one thing they should notice first? (visual hierarchy)
Design Process
Follow this sequence for any mobile screen:
Step 1: Understand the Context
- What type of app? (fitness, finance, social, productivity, health, crypto, etc.)
- Who is the user? (new, returning, power user — adapt the experience)
- What's the primary action on this screen?
- What industry design conventions apply? (See
references/industry-conventions.md)
Step 2: Structure First (UX Lens)
- Map the user flow: what screen comes before and after?
- Identify the MVP elements — only what's essential for this screen
- Place primary actions in the thumb zone (bottom 1/3 of screen)
- Follow the F-pattern reading order for content layout
- Reduce interaction cost: expose content directly instead of hiding behind taps
- Turn empty states into opportunities with guidance, illustration, and a CTA
- Choose the right input method: sliders/scroll wheels for one-time setup, text fields for repeated/precise entry
Step 3: Apply Visual Design (UI Lens)
Follow these rules in order:
Typography
- Use one font family (two max, with clear hierarchy purpose)
- Maximum 4 font sizes and 2 font weights
- Use monospace variants for large numbers (prices, stats, metrics)
- Keep text containers under 600px wide for readability
- Create hierarchy with size, weight, and opacity — not just bold everything
Color System (60/30/10 Rule)
- 60% — neutral base (white, light gray, or dark background)
- 30% — complementary color (black text, dark elements)
- 10% — brand/accent color (CTAs, key indicators, icons)
- Use opacity variations of the neutral color for text hierarchy: 100% for headings, 80% for body, 60-70% for secondary text
- Use the accent color at 5% opacity for secondary buttons and subtle card highlights
- Match shadow colors to the background (tint shadows, never pure gray/black on colored backgrounds)
- Save strong colors (like red) for meaningful moments — overuse kills hierarchy
Spacing (8-Point Grid System)
- All spacing values must be divisible by 8 or 4 (8, 12, 16, 24, 32, 48, 64, 80, 96)
- Use relationship-based spacing: related elements closer together, unrelated further apart
- Multiplier rule: if related text elements are 16px apart, the gap to the next group should be 2× (32px)
- Section vertical padding: at least 80-96px (160px for major sections on larger screens)
- Card internal padding: 24-32px baseline
- Larger text = larger spacing needed
Shadows
- Always use soft shadows — never harsh/distinct
- Match shadow color to the background with a tinted hue
- Use subtle white inner shadows on buttons to add dimension
- Add faded drop shadows for depth without heaviness
Visual Cues & Imagery
- Use icons, emojis, illustrations, and images to make information digestible
- User avatars/photos > initials > generic icons (for representing people)
- Color-coded categories with soft solid backgrounds + clean isolated images
- Keep visual style consistent across the entire app — no random stock photo mix
- Use AI-generated or curated visuals with matching color palettes
Step 4: Design for Emotion (Peak-End Rule)
The user will remember two moments: the peak (most intense) and the end (last impression).
- Identify your peak moment: completing a core task, hitting a milestone, finding what they want
- Design the peak: micro-animations, celebratory feedback, sparkles, badges, encouraging copy
- Design the ending: summary card, progress affirmation, gentle nudge to return
- Add emotional feedback loops: success states should feel rewarding (bounce, glow, sparkle)
- Celebrate small wins — success states don't need to be huge, but they should feel intentional
- Use motion and animation as trust signals, especially in high-stakes domains (finance, crypto, health)
Step 5: Polish & Details
- Add subtle glow effects behind key elements (blur + opacity)
- Use tiny white inner shadows on primary buttons
- Add 5% opacity primary-color borders on secondary elements
- Consider micro-animations for state changes
- Ensure all tap targets are at least 44×44pt
- Check contrast ratios for accessibility
- Design error states, empty states, loading states, and success states
Smart Patterns to Apply
Personalization by User Stage
- New users: simple welcome, guided setup, minimal options
- Returning users: personalized content, routine-focused, progress indicators
- Power users: advanced stats, optimization tools, dense information
Smarter Search
Never show a blank search screen. Include:
- Recent searches
- Popular/trending items
- Personalized recommendations
Order/Status Tracking
- Open with a confident status message
- Humanize with photos, names, quick-action buttons
- Use visual timelines instead of text-based date lists
Category Screens
- Use color-coded cards with soft backgrounds and clean isolated images
- Ensure visual consistency across all category items
- Create rhythm in the layout for effortless scanning
Selection Over Manual Input
- Offer tappable selections for common options (job titles, preferences, etc.)
- Include icons/emojis alongside options for personality
- Provide an "Other" option with manual input as fallback
Anti-Patterns to Avoid
- Overusing flashy gradients and blur effects (unless you can truly pull it off)
- More than 4 font sizes or 3 font weights
- Random spacing values (use the 8-point grid!)
- Hiding key content behind banners or extra taps
- Placing CTAs outside the thumb zone
- Generic empty states with no guidance
- Using sliders for frequent/precise data entry
- Making all information the same visual weight (no hierarchy)
- Emphasizing labels over values (e.g., making "Sales" bigger than "591")
- Pure gray/black shadows on colored backgrounds
Implementation Notes
When building these designs as React artifacts or HTML:
- Use Tailwind CSS utility classes for spacing, colors, and typography
- Import Lucide React for clean, consistent iconography
- Use Recharts for any data visualization
- Apply CSS transitions for micro-interactions and state changes
- Use CSS variables for the color system
- Mobile-first: design for 375px width (iPhone SE) as baseline
- Use
rounded-2xlorrounded-3xlfor modern card aesthetics - Apply
backdrop-blurfor glassmorphism effects where appropriate
For deeper guidance on industry-specific conventions and emotional design patterns, read references/industry-conventions.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

