mobile-developer

Route mobile development requests to framework-specific sub-skills.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/pikakit/agent-skills --skill mobile-developer-pikakit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mobile-developer
Source: https://github.com/pikakit/agent-skills/tree/main/.agent/skills/mobile-developer
Command: npx skills add https://github.com/pikakit/agent-skills --skill mobile-developer-pikakit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Cross-platform orchestration for mobile development, aligning React Native, Flutter, and native platforms with architecture patterns, offline considerations, and publishing workflows to reduce fragmentation.

Core Features & Use Cases

  • Framework selection and routing across RN, Flutter, and native codebases.
  • Publishing routing, including ASO, deep linking, and push notifications, with platform-specific guidance.
  • Deterministic invocation of sub-skills and selective loading to ensure predictable outcomes.

Quick Start

Initiate a mobile-first planning workflow to route the task to the appropriate sub-skills.

Frequently Asked Questions about mobile-developer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route cross-platform mobile architecture tasks between React Native and Flutter?

Cross-platform mobile architecture routing directs requests to framework-specific sub-skills for React Native, Flutter, or native codebases. It uses a deterministic invocation process with mandatory questions to selectively load routed sub-skills, ensuring predictable architecture outcomes.

What's the best way to plan offline strategy and security for a cross-platform mobile project?

Planning offline strategy and security for cross-platform mobile projects requires mobile-first orchestration. This process applies architecture routing to enforce deterministic framework selection, selectively loading sub-skills to align offline considerations and security planning.

Does this mobile architecture routing handle publishing workflows like ASO and deep linking?

Yes, mobile architecture routing handles publishing workflows including App Store Optimization, deep linking, and push notifications. It routes these publishing patterns to platform-specific guidance, ensuring deterministic invocation of the correct publishing sub-skills.

Can I use this orchestration for native mobile codebases or is it limited to cross-platform frameworks?

This orchestration applies to both native mobile codebases and cross-platform frameworks. Framework selection routing explicitly supports React Native, Flutter, and native platforms, directing tasks to the appropriate sub-skills regardless of the chosen architecture.

Why does mobile architecture routing require mandatory questions before loading sub-skills?

Mandatory questions enforce a deterministic routing process before selectively loading sub-skills. This ensures predictable outcomes by validating the specific architecture routing, offline strategy, and security planning requirements of the cross-platform mobile project.

When do I need mobile-first orchestration for my architecture routing instead of direct framework tools?

You need mobile-first orchestration when managing cross-platform mobile projects that require architecture routing across multiple frameworks. It reduces fragmentation by aligning React Native, Flutter, and native codebases with unified offline considerations and publishing workflows.