agentleFS
AthenDrakomin-hubAthenDrakomin-hub/agent-skills/skills/mobile-app-ui-design/SKILL.md

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

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.
  • VercelSkill

    web-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

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
  1. Common:

    Before designing anything, understand three things:

    line 14
  2. Common:

    Follow this sequence for any mobile screen:

    line 21
  3. Common:

    Place primary actions in the thumb zone (bottom 1/3 of screen)

    line 32
  4. Common:

    Follow the F-pattern reading order for content layout

    line 33
  5. Common:

    Follow these rules in order:

    line 39
  6. Common:

    Use one font family (two max, with clear hierarchy purpose)

    line 42
  7. Common:

    Use monospace variants for large numbers (prices, stats, metrics)

    line 44
  8. Common:

    Keep text containers under 600px wide for readability

    line 45
  9. Common:

    Create hierarchy with size, weight, and opacity — not just bold everything

    line 46
  10. Common:

    Use opacity variations of the neutral color for text hierarchy: 100% for headings, 80% for body, 60-70% for secondary text

    line 52
  11. Common:

    Use the accent color at 5% opacity for secondary buttons and subtle card highlights

    line 53
  12. Common:

    All spacing values must be divisible by 8 or 4 (8, 12, 16, 24, 32, 48, 64, 80, 96)

    line 58
  13. Common:

    Use relationship-based spacing: related elements closer together, unrelated further apart

    line 59
  14. Common:

    Always use soft shadows — never harsh/distinct

    line 66
  15. Common:

    Use subtle white inner shadows on buttons to add dimension

    line 68
  16. Common:

    Add faded drop shadows for depth without heaviness

    line 69
  17. Common:

    Use icons, emojis, illustrations, and images to make information digestible

    line 72
  18. Common:

    Keep visual style consistent across the entire app — no random stock photo mix

    line 75
  19. Common:

    Use AI-generated or curated visuals with matching color palettes

    line 76
  20. Common:

    Add emotional feedback loops: success states should feel rewarding (bounce, glow, sparkle)

    line 84
  21. Common:

    Use motion and animation as trust signals, especially in high-stakes domains (finance, crypto, health)

    line 86
  22. Common:

    Add subtle glow effects behind key elements (blur + opacity)

    line 89
  23. Common:

    Use tiny white inner shadows on primary buttons

    line 90
  24. Common:

    Add 5% opacity primary-color borders on secondary elements

    line 91
  25. Common:

    Consider micro-animations for state changes

    line 92
  26. Common:

    Ensure all tap targets are at least 44×44pt

    line 93
  27. Common:

    Check contrast ratios for accessibility

    line 94
  28. Common:

    Never show a blank search screen.

    line 105
  29. Common:

    Use visual timelines instead of text-based date lists

    line 113
  30. Common:

    Use color-coded cards with soft backgrounds and clean isolated images

    line 116
  31. Common:

    Ensure visual consistency across all category items

    line 117
  32. Common:

    Create rhythm in the layout for effortless scanning

    line 118
  33. Common:

    When building these designs as React artifacts or HTML:

    line 139
  34. Common:

    Use Tailwind CSS utility classes for spacing, colors, and typography

    line 140
  35. Common:

    Import Lucide React for clean, consistent iconography

    line 141
  36. Common:

    Use Recharts for any data visualization

    line 142
  37. Common:

    Use CSS variables for the color system

    line 144
  38. Very specific:

    Use rounded-2xl or rounded-3xl for modern card aesthetics

    line 146

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

  1. What is the user trying to accomplish? (reduce friction to that goal)
  2. How should this make the user feel? (trust, delight, confidence, calm)
  3. 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-2xl or rounded-3xl for modern card aesthetics
  • Apply backdrop-blur for glassmorphism effects where appropriate

For deeper guidance on industry-specific conventions and emotional design patterns, read references/industry-conventions.md.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.