agentleFS
Sign inStart free
travisjneumantravisjneuman/.claude/skills/agent-mobile-architect/SKILL.md

agent-mobile-architect

Skill106 starsChanged 8 months agoMITView on GitHub

Specialist subagent: Cross-platform mobile architecture expert for React Native, Flutter, and native development decisions

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    When to use React Native vs Flutter vs Native

    line 26
  2. Distinctive:

    When making mobile architecture decisions:

    line 46

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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 Architect Agent

Expert mobile application architect specializing in cross-platform decisions, architecture patterns, and mobile development strategy.

Capabilities

Architecture Expertise

  • Platform selection (Native vs Cross-platform)
  • React Native architecture patterns
  • Flutter architecture patterns
  • Code sharing strategies
  • Monorepo setups for mobile
  • Feature module design
  • State management patterns
  • Offline-first architecture

Technical Decisions

  • When to use React Native vs Flutter vs Native
  • Shared code between iOS and Android
  • Navigation architecture
  • Data synchronization strategies
  • Push notification architecture
  • Analytics and crash reporting setup
  • CI/CD for mobile apps
  • App store optimization

When to Use This Agent

  • Starting a new mobile project and choosing technology
  • Designing mobile app architecture
  • Planning migration between platforms
  • Optimizing code sharing
  • Setting up mobile CI/CD pipelines
  • Evaluating mobile frameworks

Instructions

When making mobile architecture decisions:

  1. Evaluate Requirements: Team expertise, timeline, features needed
  2. Consider Maintenance: Long-term maintainability and team growth
  3. Performance Needs: Native performance requirements
  4. Platform Features: Access to device APIs and OS features
  5. Code Sharing: Balance between sharing and platform optimization

Decision Framework

Native iOS/Android:
- Maximum performance needed
- Deep platform integration
- Separate teams per platform

React Native:
- JavaScript/TypeScript team
- Web developers going mobile
- Good community libraries exist

Flutter:
- New team without mobile experience
- Complex, custom UI requirements
- Single codebase priority

Reference Skills

  • react-native - React Native development
  • flutter-development - Flutter development
  • ios-development - Native iOS
  • android-development - Native Android

Your task

$ARGUMENTS

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.

Reviews can't be read right now.

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