agentleFS
FAHTHIZFAHTHIZ/oasis/skills/mobile-development/SKILL.md

mobile-development

Skill4 starsChanged 9 days agoApache-2.0View on GitHub

Build and troubleshoot mobile applications and mobile-device development environments safely.

14 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use context-engineering and ui-ux-pro-max.

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

    context-engineering

    Master context engineering for AI agent systems. Use when designing agent architectures, debugging context failures, optimizing token usage, implementing memory systems, building multi-agent coordination, evaluating agent performance, or developing LLM-powered pipelines. Covers context fundamentals, degradation patterns, optimization techniques (compaction, masking, caching), compression strategies, memory architectures, multi-agent patterns, LLM-as-Judge evaluation, tool design, and project development.

    Also in 3 projects that use this

  • StrayDragonSkill

    ui-ux-pro-max

    UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.

    Also in 3 projects that use this

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 13 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:

    Prefer official SDKs, package managers, and documented APIs.

    line 11
  2. Distinctive:

    Keep device-only secrets out of browser storage, logs, screenshots, source control, and agent prompts unless essential.

    line 13
  3. Distinctive:

    Add tests for platform-independent logic and explicitly list the device checks that cannot be simulated in CI.

    line 14
  4. Distinctive:

    Never claim a mobile build or install succeeded without an actual build/install result on the target platform.

    line 15

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

  1. Inspect the existing framework, target platforms, package scripts, SDK requirements, and project conventions before changing architecture.
  2. Distinguish browser/PWA behavior from native Android or iOS capabilities. Do not claim device APIs, background execution, local shell access, or offline behavior unless implemented and tested on the target.
  3. For Android and Termux, verify the device architecture, Node/runtime support, storage permissions, and available package managers before suggesting installation steps. Give one terminal command at a time when the user is following steps interactively.
  4. Prefer official SDKs, package managers, and documented APIs. Avoid remote shell scripts, broad permissions, and hard-coded secrets.
  5. Design for narrow screens, touch targets, keyboard/IME behavior, reduced motion, accessible labels, and graceful network loss.
  6. Keep device-only secrets out of browser storage, logs, screenshots, source control, and agent prompts unless essential.
  7. Add tests for platform-independent logic and explicitly list the device checks that cannot be simulated in CI.
  8. Never claim a mobile build or install succeeded without an actual build/install result on the target platform.

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.