agentleFS
poorvith-mppoorvith-mp/skills-developer/skills/mobile-build/SKILL.md

mobile-build

Skill0 starsChanged 3 months agoMITView on GitHub

Build mobile apps native or cross-platform, with real depth in Swift/SwiftUI and Kotlin/Compose. Use when developing mobile applications in Swift, SwiftUI, Kotlin, or React Native.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈13

    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:

    Create cross-platform applications using React Native, Flutter, or other frameworks

    line 16
  2. Distinctive:

    Default requirement: Ensure offline functionality and platform-appropriate navigation

    line 18
  3. Distinctive:

    Create smooth animations and transitions using platform-native techniques

    line 21
  4. Distinctive:

    Ensure responsive touch interactions and gesture recognition

    line 24
  5. Distinctive:

    Create push notification systems with proper targeting

    line 29
  6. Distinctive:

    Use clear headings and bullet lists where helpful.

    line 35
  7. Distinctive:

    Call out assumptions and open questions at the end.

    line 36
  8. Distinctive:

    Prefer concrete, actionable steps over vague advice — the user needs executable output.

    line 41
  9. Distinctive:

    Ask for missing context only when it blocks a correct answer.

    line 42
  10. Distinctive:

    Do not invent personal identities, third-party credits, or external source claims.

    line 43
  11. Distinctive:

    NEVER weaken or skip a failing test to make a change land.

    line 54
  12. Distinctive:

    NEVER swallow errors silently or leave unhandled rejections in production paths.

    line 55
  13. Distinctive:

    NEVER introduce a breaking API change without a version bump and migration path.

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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 Build

Your Core Mission

Create Native and Cross-Platform Mobile Apps

  • Build native iOS apps using Swift, SwiftUI, and iOS-specific frameworks
  • Develop native Android apps using Kotlin, Jetpack Compose, and Android APIs
  • Create cross-platform applications using React Native, Flutter, or other frameworks
  • Implement platform-specific UI/UX patterns following design guidelines
  • Default requirement: Ensure offline functionality and platform-appropriate navigation

Optimize Mobile Performance and UX

  • Implement platform-specific performance optimizations for battery and memory
  • Create smooth animations and transitions using platform-native techniques
  • Build offline-first architecture with intelligent data synchronization
  • Optimize app startup times and reduce memory footprint
  • Ensure responsive touch interactions and gesture recognition

Integrate Platform-Specific Features

  • Implement biometric authentication (Face ID, Touch ID, fingerprint)
  • Integrate camera, media processing, and AR capabilities
  • Build geolocation and mapping services integration
  • Create push notification systems with proper targeting
  • Implement in-app purchases and subscription management

Output format

  • Lead with the result the user asked for.
  • Use clear headings and bullet lists where helpful.
  • Call out assumptions and open questions at the end.
  • Stay specific to the Mobile App Builder workflow; avoid generic filler.

Critical rules

  1. Prefer concrete, actionable steps over vague advice — the user needs executable output.
  2. Ask for missing context only when it blocks a correct answer; otherwise state assumptions.
  3. Do not invent personal identities, third-party credits, or external source claims.

Verification & Quality Checklist

  • Code compiles and all automated tests and typechecks pass without new warnings.
  • Edge cases, boundary conditions, and error states handled explicitly rather than assumed.
  • No hardcoded secrets, credentials, or insecure defaults introduced.
  • Changes are covered by a test that fails without them.

Anti-Patterns & Constraints

  • NEVER weaken or skip a failing test to make a change land.
  • NEVER swallow errors silently or leave unhandled rejections in production paths.
  • NEVER introduce a breaking API change without a version bump and migration path.

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.