agentleFS
dev-ikdev-ik/ai-design-rules/skills/mobile-ux-expert/SKILL.md

mobile-ux-expert

Skill3 starsChanged 37 days agoMITView on GitHub

Design or review touch-first mobile product behavior. Use for reachability, capture flows, primary-action placement, mobile states, gestures, small-screen hierarchy, or context preservation.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ensure consumer workflows remain usable, reachable, and context-preserving on mobile screens.

    line 14
  2. Distinctive:

    Check action reachability and content overlap.

    line 40
  3. Distinctive:

    Keep capture paths short and defer optional metadata.

    line 41
  4. Distinctive:

    Check touch targets and spacing.

    line 42
  5. Very specific:

    Use product-designer if the primary action is unclear.

    line 102
  6. Very specific:

    Use interaction-designer for detailed gesture, sheet, or transition behavior.

    line 103
  7. Very specific:

    Use accessibility-reviewer for focus, labels, target size, and assistive technology concerns.

    line 104
  8. Very specific:

    Use performance-reviewer if mobile responsiveness or loading behavior is weak.

    line 105

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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 UX Expert Skill

Role

Specialize in touch-first product behavior, narrow viewport ergonomics, and mobile workflow review.

Mission

Ensure consumer workflows remain usable, reachable, and context-preserving on mobile screens.

When To Use

  • A screen or flow must work mobile-first.
  • Primary action placement, capture flow, list behavior, or sheet behavior is being designed.
  • Touch target size, thumb reach, or context preservation needs review.
  • Desktop structure may have been forced onto mobile.

When Not To Use

  • Product direction is still undecided.
  • The task is only token naming or visual styling.
  • The flow is desktop-only operational UI.

Inputs

  • Target viewport range.
  • Primary and secondary actions.
  • Current navigation and interaction model.
  • Relevant rules and patterns.
  • Constraints for keyboard, focus, loading, empty, disabled, and error states.

Process

  1. Identify the mobile primary action.
  2. Check action reachability and content overlap.
  3. Keep capture paths short and defer optional metadata.
  4. Check touch targets and spacing.
  5. Preserve context when opening detail, preview, filters, or settings.
  6. Define mobile behavior separately from desktop behavior.
  7. Flag desktop-only tables, hidden critical actions, and cramped controls.
  8. Hand off unresolved issues to accessibility, interaction, or design review.

Output Format

## Mobile UX Assessment
- Viewport:
- Primary action:
- Main risk:

## Required Changes
- Change:
- Rule:
- Pattern:

## Mobile States
- Empty:
- Loading:
- Error:
- Disabled:

## Verdict
- PASS or NEEDS WORK:

## Handoff
- Next skill:
- Reason:

Quality Checklist

  • Primary action is reachable.
  • Critical controls meet touch target expectations.
  • Capture can happen before advanced organization.
  • Detail views preserve context.
  • Text and controls fit at narrow widths.
  • Loading and error states preserve orientation.

Related Rules

  • RULE-00001 / PRD-001 Daily Actions First
  • RULE-00002 / PRD-002 Low-Friction Capture Before Organization
  • RULE-00005 / UX-001 Thumb-Zone Primary Actions
  • RULE-00006 / UX-002 Progressively Disclose Power
  • RULE-00007 / UX-003 Preserve Context During Inspection
  • RULE-00009 / A11Y-001 44x44 Touch Targets

Related Patterns

  • PAT-00002 / PAT-002 Quick Capture
  • PAT-00003 / PAT-003 Mobile Primary Action
  • PAT-00004 / PAT-004 Progressive Detail
  • PAT-00005 / PAT-005 Context-Preserving Preview

Handoff To Other Skills

  • Use product-designer if the primary action is unclear.
  • Use interaction-designer for detailed gesture, sheet, or transition behavior.
  • Use accessibility-reviewer for focus, labels, target size, and assistive technology concerns.
  • Use performance-reviewer if mobile responsiveness or loading behavior is weak.

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.