Skip to content
cccskills
FreePublished on GitHub

mobile-architecture

Designs and reviews mobile architecture across Flutter, native Android, native iOS, React Native and Kotlin Multiplatform. Covers state ownership, data flow, modules, dependency boundaries, navigation, offline data and KMP shared source sets versus host apps. Use when structuring a feature, choosing state management, refactoring layers or deciding where a real class or screen belongs.

The English summary is being prepared. Showing the original description.

See how to install

Files included (15)

  • SKILL.md3.5 KB
  • references/android.md3.0 KB
  • references/flutter.md1.9 KB
  • references/flutter/app-architecture.md6.1 KB
  • references/flutter/bloc.md9.8 KB
  • references/flutter/change-notifier.md3.2 KB
  • references/flutter/feature-first.md5.4 KB
  • references/flutter/login-use-case.md571 B
  • references/flutter/managing-state.md7.9 KB
  • references/flutter/provider.md3.4 KB
  • references/flutter/recommended-architecture.md6.1 KB
  • references/flutter/riverpod.md6.8 KB
  • references/ios.md2.7 KB
  • references/kotlin-multiplatform.md1.6 KB
  • references/react-native.md2.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Mobile Architecture

What makes a mobile codebase keep up with its team, and how each stack expresses it. This file holds the principles; each platform's patterns, libraries and structure live in its reference.

1. Pick the reference

ProjectRead
Flutterreferences/flutter.md — structure guides and one guide per state management library
Native Android (Kotlin), or the Android side of Kotlin Multiplatformreferences/android.md
Native iOS (Swift)references/ios.md
React Native or Exporeferences/react-native.md
Kotlin Multiplatform shared code and target boundariesreferences/kotlin-multiplatform.md

2. Map before judging

Read the entry point, navigation setup, dependency wiring, module or package graph and two or three representative features before proposing changes. A coherent structure that differs from the references is not a finding; inconsistency and coupling are.

3. Principles on every stack

  • Layers with one direction of dependency. UI renders state and sends events; logic (view models, blocs, stores, use cases) decides; data (repositories and data sources) fetches and stores. UI never calls HTTP clients, databases or platform SDKs directly.
  • Unidirectional data flow. State flows down to the UI; events flow up. The UI does not mutate shared state in place.
  • Single source of truth. Each piece of data has one owner — usually a repository — that the rest of the app observes. Duplicated copies drift.
  • State ownership. Screen state lives with the screen's logic and survives configuration changes where the platform requires it; app-wide state (session, settings) has one explicit owner; server data lives in a cache or repository, not copied into global stores.
  • Impossible states unrepresentable. Model loading, content and error as one sealed or discriminated state instead of independent flags.
  • Feature boundaries. Organize by feature once there are several; features depend on shared core code, not on each other's internals.
  • Dependencies injected. Construct dependencies at a composition root (DI container or initializers) and pass them in; no service locators reached from deep inside features.
  • Offline and errors by design. Decide what works offline, how writes sync and how failures reach the user before building screens.
  • Testability as a check. If business logic cannot be tested without a device, it is in the wrong layer.

4. Proportion

Match the structure to the app and team. A domain layer, a DI framework or a multi-module build pays off with size and team count; adding them to a small app is also a finding. Propose incremental steps with the files involved, highest impact and lowest risk first.

Output

## Architecture Overview
## Architecture Issues
## Coupling Problems
## Refactoring Suggestions
## Recommended Architecture
## Action Plan

Cite path:line for every finding.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Audits and fixes mobile accessibility across Flutter, native Android, native iOS, React Native and Kotlin Multiplatform, including shared Compose UI and native hosts. Covers TalkBack/VoiceOver labels, roles, state, reading order, touch targets, text scaling, contrast and focus. Use for a11y audits, screen-reader bugs or accessible UI implementation.

The English summary is being prepared. Showing the original description.

wrsilva/reis-mobile7Updated Oct 14, 2026

Builds native Android apps with the Android team's guides — Jetpack Compose UI, adaptive layouts, edge-to-edge, Compose styles, migrating XML views to Compose, Navigation 3 and predictive back; Android Gradle Plugin 9 upgrades, R8 keep rule analysis, profiling with Android Studio and Perfetto, and the Android CLI; Google Play policy compliance, Play Billing upgrades and the Engage SDK; Credential Manager restore and verified email; CameraX and Media3 Cast; App Functions and the ML Kit GenAI Prompt API; Wear OS, Android TV and display glasses. Use when writing, upgrading or auditing native Android (Kotlin) code for any of these topics, even if the user does not name the library.

The English summary is being prepared. Showing the original description.

wrsilva/reis-mobile7Updated Oct 14, 2026

Implements and reviews mobile identity and session flows across Flutter, Android, iOS, React Native and Kotlin Multiplatform. Use for sign-in, passkeys, account recovery, provider linking, reauthentication, logout and concurrent refresh. Security audits belong to mobile-security; account deletion belongs to mobile-privacy.

The English summary is being prepared. Showing the original description.

wrsilva/reis-mobile7Updated Oct 14, 2026

Reviews mobile code for production bugs across Flutter, native Android, native iOS, React Native and Kotlin Multiplatform, including KMP source-set and host API contracts. Covers lifecycle, concurrency, UI state and native boundaries with file:line evidence. Use for a code review, PR, project audit, quality check or /reis-mobile:review.

The English summary is being prepared. Showing the original description.

wrsilva/reis-mobile7Updated Oct 14, 2026

Diagnoses build and runtime failures across Flutter, native Android, native iOS, React Native and Kotlin Multiplatform. Covers pub/Dart, Gradle/AGP, Xcode/CocoaPods, Metro, KMP source sets and iOS frameworks, crashes and deep links. Use for failing builds, app launches, stack traces or /reis-mobile:debug.

The English summary is being prepared. Showing the original description.

wrsilva/reis-mobile7Updated Oct 14, 2026

Detects the mobile stack of the current project (Flutter, Android, iOS, React Native, Kotlin Multiplatform), its languages and target platforms, using the reis-mobile detector. Use when you need to know which mobile stack a project uses before reviewing, debugging or changing it, or when the user asks "what stack is this project?".

The English summary is being prepared. Showing the original description.

wrsilva/reis-mobile7Updated Oct 14, 2026

See all skills by wrsilva

Report a problem with this skill