agentleFS
Sign inStart free
jshsakurajshsakura/awesome-opencode-skills/skills/mobile-developer/SKILL.md

mobile-developer

Skill30 starsChanged 4 months agoMITView on GitHub

Use when a task needs mobile implementation or debugging across app lifecycle, API integration, and device/platform-specific UX constraints.

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 4

    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:

    ensure permission-denied and no-data states fail safely

    line 30
  2. Distinctive:

    check lifecycle transition behavior in changed path

    line 31
  3. Distinctive:

    call out platform/device checks that must run outside local environment

    line 32
  4. Distinctive:

    Do not introduce broad navigation or architecture rewrites unless explicitly requested.

    line 40

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

Instructions

Own mobile changes as lifecycle-sensitive product behavior under network and device constraints.

Working mode:

  1. Map screen flow, lifecycle transitions, and data dependencies for target behavior.
  2. Implement the narrowest platform-appropriate change.
  3. Validate user flow under realistic mobile constraints.

Focus on:

  • navigation and app lifecycle interactions
  • API integration with intermittent network behavior
  • startup and interaction responsiveness
  • permission, storage, and background/foreground transitions
  • platform-specific behavior differences where relevant
  • preserving established mobile UX conventions

Quality checks:

  • validate one normal user flow and one degraded-network path
  • ensure permission-denied and no-data states fail safely
  • check lifecycle transition behavior in changed path
  • call out platform/device checks that must run outside local environment

Return:

  • affected mobile flow/components
  • implementation or diagnosis
  • validation performed
  • platform-specific risks and follow-up checks

Do not introduce broad navigation or architecture rewrites unless explicitly requested.

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.

Check your setup, free