agentleFS
podopodo/design-agent-skills/skills/mobile-app-design/SKILL.md

mobile-app-design

Skill32 starsChanged 6 months agoMITView on GitHub

Comprehensive mobile app UI/UX design skill covering iOS HIG, Android Material 3, accessibility standards, React Native best practices, touch targets, thumb zones, and adaptive patterns, with detailed reference documents, examples and audit scripts.

5 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 1

    Distinctive

    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:

    License: no LICENSE file <!-- das:install:end -->

    line 57

“Common” is measured: kept by at least 6 in 10 of the 5 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-design

Catalogue stub — full skill: awesome-skills/mobile-app-design

<!-- das:install:start — generated from stub.yaml by `npm run generate`; edit stub.yaml, not this block -->

Decision tree

  1. Is the full skill already installed? Upstream names this skill mobile-app-design-standards, so it installs next to this pointer (the pointer is not replaced).
    • Global: f=~/.agents/skills/mobile-app-design-standards/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"
    • Project: f=.agents/skills/mobile-app-design-standards/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"
    • installed → the skill is installed as mobile-app-design-standards, invoke it and proceed
    • pointer → go to step 2
  2. Detect scope, then install:

    [ -e ~/.agents/skills/mobile-app-design ] && echo "global" || echo "project"

    Global:

    npx skills add awesome-skills/mobile-app-design --skill "Mobile App Design Standards" -g -y

    Project:

    npx skills add awesome-skills/mobile-app-design --skill "Mobile App Design Standards" -y

    Claude Code: send a command as a chat message starting with ! to run it without leaving the conversation.

Heads-up

  • License: no LICENSE file
<!-- das:install:end -->

Invoke after install

  • Skill name: mobile-app-design-standards
  • Triggers: "mobile app design", "iOS design", "Android design", "touch targets", "thumb zones"

What it does

Extensive mobile UI/UX design guidance. Covers Apple iOS Human Interface Guidelines, Android Material 3, WCAG mobile accessibility, React Native implementation best practices, correct touch target sizing, thumb-zone ergonomics, and adaptive layout patterns for phones and tablets. Ships reference documents (iOS, Android, accessibility checklist, performance, common mistakes, platform differences, UI libraries), example screens, and helper scripts for accessibility, contrast and touch-target checks. Use for any cross-platform mobile design decision.

The upstream skill is named "Mobile App Design Standards", so it installs as mobile-app-design-standards next to this pointer.

When NOT to use

  • Apple HIG-only work — use apple-hig-skills
  • SwiftUI-specific implementation — use swiftui-patterns
  • Professional mobile UI craft patterns — use mobile-app-ui-design

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.