skills.rest
Vincri126
Vincri126COMMUNITY
Explore all skills by this author →
GitHub

mobile-development

Plan React Native and Flutter mobile architecture with QA readiness.

Updated Aug 23, 2026
Search Tags:#cross-platform#react-native#flutter#app-store-submission#qa-gates#mobile-architecture
One-click install
npx skills add https://github.com/Vincri126/MCO-Template --skill mobile-development-vincri126
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mobile-development
Source: https://github.com/Vincri126/MCO-Template/tree/main/.orchestrator/skills/mobile-development
Command: npx skills add https://github.com/Vincri126/MCO-Template --skill mobile-development-vincri126

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires metro-cli, tsc, eslint, npm, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Mobile teams working across React Native and Flutter lack a unified advisor that covers architecture, native module integration, deployment, and QA readiness; this skill delivers a single directive combining structure, performance tactics, and compliance checklists so architects can ship resilient apps without missing platform-specific constraints or release requirements. It also factors in limited device resources, offline connectivity, and app store expectations to keep builds production-ready and predictable.

Core Features & Use Cases

  • React Native Blueprint: Detailed guidance on scalable project structure, navigation, deep linking, native modules, image caching, bundle sizing, and Detox/Jest testing keeps React Native codebases organized and performant.
  • Flutter Architecture: Widget tree planning, Riverpod state management, platform channel communication, and integration/e2e testing patterns ensure Flutter modules align with shared domain logic and native services.
  • Cross-Platform Patterns & Performance: Shared business logic layers, responsive hooks, virtualization, offline-first databases, and QA gate references like references/qa-gates.md align development across both platforms.
  • Release & QA Operations: scripts/mobile-qa-gate.sh enforces linting, security, manifest, performance, and dependency checks while references/app-store-checklist.md plus QA gating docs document accessibility, analytics, and store submission rituals.

Quick Start

Provide a React Native and Flutter cross-platform architecture plan that addresses offline storage, push notifications, and QA gate readiness.

Frequently Asked Questions about mobile-development

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

FAQPage Schema
How do I plan cross-platform mobile architecture for React Native and Flutter?▼

To plan cross-platform mobile architecture, structure shared business logic layers, configure responsive hooks, and align Flutter widget trees with React Native navigation to ensure modules integrate with native services.

What's the best way to enforce mobile QA gates before app store submission?▼

The best way to enforce mobile QA gates is running automated checks for linting, security, manifest validation, and bundle sizing, followed by referencing app store checklists to document accessibility and analytics.

How do I handle offline storage and push notifications in React Native and Flutter?▼

Handle offline storage and push notifications by implementing offline-first databases and native module integration, utilizing platform channel communication for Flutter and native modules for React Native.

Does this mobile development workflow support iOS and Android release requirements?▼

Yes, the mobile development workflow supports iOS and Android release requirements by providing comprehensive QA documentation, app store submission checklists, and performance gating checks for both platforms.

Can I use Detox and Jest for React Native integration testing alongside Flutter e2e tests?▼

Yes, you can use Detox and Jest for React Native integration testing alongside Flutter e2e tests by applying shared testing patterns that align with cross-platform QA gating tasks.

Why do I need tsc and eslint for cross-platform mobile development?▼

You need tsc and eslint for cross-platform mobile development to enforce TypeScript type checking and code linting, which are critical dependencies for passing automated mobile QA gate scripts.

Related Skills

Explore More Software Engineering Skills→
BaoNguyen09BaoNguyen09
6

install-windows

Install Node.js and project dependencies on Windows with PowerShell.

Community
Intermediate
oldwombatoldwombat

expo-deployment

Automate Expo app builds and submissions to iOS, Android, and web via EAS CLI.

Community
Advanced
Nir-BhayNir-Bhay
19

detox-mobile-test

Generates Detox-based end-to-end tests for React Native apps.

Community
Advanced
Yemomo511Yemomo511
2

expo-brownfield

Integrate Expo and React Native modules into existing native iOS and Android apps.

Community
Intermediate