agentleFS
Evan-Kim2028Evan-Kim2028/agent-skills/skills/frontend/mobile-product-ux/SKILL.md

mobile-product-ux

Skill1 starsChanged 3 months agoMITView on GitHub

Mobile product UX — sticky chrome, bottom bars, sheets, safe areas, gesture conflicts, one-thumb density. Use only when phone/tablet chrome is the focus (sticky misbehaving, sheet vs keyboard, adapting desktop product UI to mobile). Prefer product-design when multi-step product UX is unclear (it routes here). Prefer frontend-design for full FE feature builds. Not for marketing landings only, pure desktop dashboards, general polish (product-ui-craft), or browser proof loops (browser-verify / quality-check).

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Always consider at least:

    line 39
  2. Distinctive:

    Avoid hover-only tooltips for critical info

    line 58
  3. Distinctive:

    Before shipping swipeable panels:

    line 63
  4. Distinctive:

    Prefer numbers-first expandable rows over walls of labels

    line 72

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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 product UX

Job: Make product surfaces usable with a thumb without discarding desktop power.

Sources (attribution)

  • Mobile platform practice (safe areas, bottom reachability, sheet patterns) aligned with iOS HIG / Material guidance — summarized for agents.
  • Production patterns from dense product apps: sticky filter docks, floating action HUDs, grade/tool bars that must track matrix height, chat action bars.
  • Gesture hygiene: don’t let swipe containers steal sliders/scroll.

Original synthesis for agent-skills; not a copy of a single upstream skill.

When to load

  • Card detail sticky grade bars, mobile action rows
  • Chat history/share density on small screens
  • Trade floor floating HUD / Accept placement
  • Filter docks, bottom sheets, share sheets
  • “Works on desktop, broken on iPhone”

Design rules

1. Viewports are requirements

Always consider at least:

  • ~390×844 (phone)
  • Safe-area insets (env(safe-area-inset-*))
  • Landscape only if product cares

2. Chrome model

ElementGuidance
Top stickyThin; must not eat content; respect notch
Bottom sticky / HUDClear primary action; pad for home indicator
Dual stickiesContent padding both ends; test scroll range
SheetsDrag handle affordance; focus trap; dismiss ≠ error

3. Touch

  • Min ~44×44 px targets
  • Separate destructive vs primary
  • Avoid hover-only tooltips for critical info
  • Haptics (if project has a shared helper) only for meaningful commits

4. Gesture conflicts

Before shipping swipeable panels:

  • Horizontal swipe doesn’t steal slider/range inputs
  • Vertical scroll wins inside lists
  • Nested scroll areas have clear ownership
  • Pull-to-refresh (if any) doesn’t fight chat scroll

5. Density on small screens

  • Prefer numbers-first expandable rows over walls of labels
  • Collapse secondary actions into menus / overflow
  • One primary CTA visible without scroll when possible
  • Don’t clone desktop multi-column toolbars — re-prioritize

6. Content visibility

  • Sticky bars must remain stuck for the full scroll region they claim
  • Keyboard open: composer/chat stays usable (visual viewport)
  • Fixed footers never permanently hide the last list items

Implementation checklist

  • pb-safe / padding uses safe-area tokens if project defines them
  • position: sticky parent overflow not breaking stick
  • z-index layers documented for HUD vs sheet vs nav
  • Mobile nav items match product priorities (drop low-value tabs)
  • Share sheet dismiss treated as cancel, not failure toast

Verify (required for sticky/gesture work)

Route to browser-verify:

  • Mobile project or 390-wide snapshot
  • Scroll through full matrix/list with sticky claimed
  • Open sheet + dismiss
  • Primary CTA reachable with one thumb

Hand off

NeedNext skill
Token/type systemdesign-system
General density polishproduct-ui-craft
A11y focus in sheetsweb-quality
Jank while scrollingreact-performance

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.