reis-mobile 0.3.6 → 0.5.0

package/README.md

@@ -2,11 +2,11 @@
 
 A mobile app is not a generic project. A code review that does not know about `BuildContext` after `await`, `android:exported`, `NSAllowsArbitraryLoads` or `Podfile.lock` lets through exactly the bugs that only show up on the device. **reis-mobile** detects your project's stack, picks the right specialist and loads only the skills that apply to Flutter, Android, iOS or React Native.
 
-**AI agents for mobile engineering.** A Claude Code plugin with agents, skills and workflows specialized in mobile development.
+**AI agents and skills for mobile development — Flutter, Android, iOS and React Native.** A plugin for Claude Code and Codex with specialist agents and skills for code review, debugging, tests, architecture, security and Firebase.
 
 <p align="center">
   <a href="https://github.com/wrsilva/reis-mobile/actions/workflows/ci.yml"><img src="https://github.com/wrsilva/reis-mobile/actions/workflows/ci.yml/badge.svg" alt="CI"></a>
-  <img src="https://img.shields.io/badge/Version-0.3.6-blue" alt="Version 0.3.6">
+  <img src="https://img.shields.io/badge/Version-0.5.0-blue" alt="Version 0.5.0">
   <img src="https://img.shields.io/badge/Claude_Code-plugin-blueviolet" alt="Claude Code plugin">
   <img src="https://img.shields.io/badge/Node.js-22+-339933?logo=node.js&logoColor=white" alt="Node.js 22+">
   <img src="https://img.shields.io/badge/Dependencies-0-brightgreen" alt="Zero dependencies">
@@ -23,7 +23,7 @@ A mobile app is not a generic project. A code review that does not know about `B
 
 🔎 **Detects the stack on its own.** Flutter (app or plugin), React Native (including Expo), Kotlin Multiplatform, native Android and iOS, with languages and target platforms. A Flutter app with `android/` and `ios/` is still Flutter.
 
-👥 **7 agents and 67 mobile skills.** Flutter architect, performance and test engineers, Flutter/Android/iOS staff engineer, native plugin specialist, code reviewer and a lead that coordinates them all, plus skills for BLoC, Riverpod, Firebase, testing, layout, plugins and security.
+👥 **16 agents and 11 mobile skills.** Architect, performance and test engineers for Flutter, native Android, native iOS and React Native, a staff engineer, a native plugin specialist, a code reviewer and a lead that coordinates them all, plus skills for Gradle, Xcode and CocoaPods builds, Jetpack Compose, BLoC, Riverpod, Firebase and testing on every platform, plugins and security.
 
 🌐 **Answers in English or Portuguese.** `reis-mobile init eng` or `reis-mobile init pt` sets the language of reports, explanations and debates.
 
@@ -35,25 +35,27 @@ A mobile app is not a generic project. A code review that does not know about `B
 
 🔒 **Secrets never reach the model.** The diff sent for review goes through a layer that masks API keys, tokens, JWTs, private keys and keystore passwords.
 
-🪶 **No dependencies.** `npx reis-mobile init eng` installs it in Claude Code and Codex, with zero npm dependencies, no hooks and no external provider.
+🪶 **Two commands to install.** `npm install -g reis-mobile` and `reis-mobile init eng` set it up in Claude Code and Codex, with zero npm dependencies, no hooks and no external provider.
 
 ---
 
 ## What's new
 
-> 🆕 **v0.3.0: the specialists debate.** On an architecture decision, a single specialist gives you the answer of their specialty. `/reis-mobile:debate` puts three of them to defend incompatible positions on the same question — and `lead-mobile` decides, instead of listing pros and cons.
+> 🆕 **v0.4.0: every mobile stack.** Native Android, native iOS and React Native get their own architect, performance and test specialists, and `/reis-mobile:debug` finds the cause of a failing build with the toolchain versions in hand.
 >
 > ```bash
-> /reis-mobile:debate Riverpod or BLoC for this app's state?
-> /reis-mobile:debate --rounds 3 offline-first with Firestore or a local cache?
+> /reis-mobile:debug Execution failed for task ':app:compileDebugKotlin'
+> /reis-mobile:debug pod install could not find compatible versions for Firebase
 > ```
 >
-> Round 1 is blind, so nobody anchors the others. Participants do not vary only in role: they vary in model, because three instances of the same model agree for the same wrong reasons.
+> Tests and Firebase are one skill each — `mobile-test` and `mobile-firebase` — with a guide per platform, so a request loads only what your stack needs.
 
 | Version | Highlights |
 |--------|-----------|
-| **v0.3.6** (current) | `reis-mobile init eng` installs the plugin in Claude Code and Codex at once, skipping whichever is not installed; `init --uninstall` removes it from both. |
-| **v0.3.5** | Installs through npm (`npx reis-mobile init`) and the Claude Code and Codex plugins. Homebrew and the curl/PowerShell installers are discontinued. |
+| **v0.5.0** (current) | 11 skills instead of 60: topic skills with a guide per platform (`mobile-architecture`, `mobile-code-review`, `mobile-debug`, `mobile-test`, `mobile-security`, `mobile-firebase`) and platform skills (`mobile-flutter`, `mobile-android`, and the new `mobile-ios` and `mobile-rn`). Half the fixed context cost. |
+| **v0.4.0** | Native Android, iOS and React Native: architect, performance and test agents for each; `/reis-mobile:debug` for Gradle, Xcode, CocoaPods and Flutter failures; `mobile-test` and `mobile-firebase` with a guide per platform; the Android team's skills; `.reis-mobile/config.yaml` for monorepos. Skills now use stack prefixes. |
+| **v0.3.6** | `reis-mobile init eng` installs the plugin in Claude Code and Codex at once, skipping whichever is not installed; `init --uninstall` removes it from both. |
+| **v0.3.5** | Installs through npm and the Claude Code and Codex plugins. |
 | **v0.3.4** | Back to the `reis-mobile` name: `reis-mobile` CLI and `/reis-mobile:*` commands, undoing the `mobile` renames of v0.3.2 and v0.3.3. |
 | **v0.3.1** | Answers in English or Portuguese: `reis-mobile init pt\|en` and `reis-mobile lang` save the language for reports, doctor explanations and debates. Agents, skills, commands and docs are now written in English. |
 | **v0.3.0** | `/reis-mobile:debate` command: three specialists with conflicting priorities debate over two rounds and `lead-mobile` decides. Participants vary in role and model; `--external` adds Codex and Gemini. Brings forward the `council` planned for v0.8.0. |
@@ -65,24 +67,16 @@ A mobile app is not a generic project. A code review that does not know about `B
 
 ## Installation
 
-reis-mobile ships through three channels:
+You need **Node.js 22+** and **[Claude Code](https://claude.com/claude-code)**, the **Codex CLI**, or both.
 
-| Channel | What you get |
-|---|---|
-| **Claude Code plugin** | Everything: 7 agents, 67 skills and the `/reis-mobile:*` commands |
-| **Codex plugin** | The skills |
-| **npm** | The `reis-mobile` CLI: `init` installs both plugins, plus `doctor`, `route`, `review` and `lang` |
-
-Requirements: **Node.js 22+**, and **[Claude Code](https://claude.com/claude-code)**, the **Codex CLI**, or both.
-
-### Quick install (Claude Code and Codex)
+### Install
 
 ```bash
 npm install -g reis-mobile
 reis-mobile init eng
 ```
 
-`reis-mobile init` finds which of `claude` and `codex` are on your `PATH` and installs the plugin in each, skipping the missing one:
+`init` installs the plugin in Claude Code and Codex, whichever you have, and sets the answer language (`eng` or `pt`):
 
 ```text
 ✓ Claude Code installed
@@ -90,21 +84,35 @@ reis-mobile init eng
 ✓ Language    en (~/.config/reis-mobile/config.json)
 ```
 
-Running it again is safe, and it also updates an existing install. Without a global install, use `npx reis-mobile init eng`.
+Restart Claude Code and Codex, open your app folder and try it:
 
-Restart Claude Code and Codex. In Claude Code, run in your app folder:
+| Tool | Try |
+|---|---|
+| Claude Code | `/reis-mobile:doctor`, then `/reis-mobile:review` |
+| Codex | Type `$` to search the skills, or use `/skills` |
 
-```text
-/reis-mobile
-/reis-mobile:doctor
-/reis-mobile:review
+### Update
+
+```bash
+npm update -g reis-mobile
+reis-mobile init eng
+```
+
+Then restart Claude Code and Codex. See what changed in the [CHANGELOG](CHANGELOG.md).
+
+### Uninstall
+
+```bash
+reis-mobile init --uninstall
+npm uninstall -g reis-mobile
 ```
 
-In Codex, type `$` in the message field to search for skills, or use `/skills`. See the [official Codex skills documentation](https://learn.chatgpt.com/docs/build-skills#how-chatgpt-and-codex-use-skills).
+The first command removes the plugin from Claude Code and Codex and deletes the saved language; the second removes the CLI. Keep the `-g`: without it, npm looks for the package in the current folder and removes nothing.
 
-### Manual install, without npm
+<details>
+<summary>Install without npm</summary>
 
-The plugins install straight from GitHub. In each tool, the first command registers the marketplace and only needs to run once per machine:
+Add the plugin straight from GitHub. The `marketplace add` line only needs to run once per machine.
 
 ```bash
 # Claude Code
@@ -116,60 +124,62 @@ codex plugin marketplace add https://github.com/wrsilva/reis-mobile.git
 codex plugin add reis-mobile@reis-mobile
 ```
 
-If Codex answers `plugin reis-mobile was not found in marketplace reis-mobile`, the marketplace is either not registered or an old snapshot: run `codex plugin marketplace add` again, or `codex plugin marketplace upgrade reis-mobile`, and repeat `codex plugin add`.
-
-### Using the CLI from Codex
+To update, run `claude plugin marketplace update reis-mobile` and `claude plugin update reis-mobile@reis-mobile` in Claude Code, or `codex plugin marketplace upgrade reis-mobile` and `codex plugin add reis-mobile@reis-mobile` in Codex.
 
-The Codex plugin gives Codex the skills; the agents and the `/reis-mobile:*` commands are Claude Code formats and have not been validated in Codex. For routing and review context, run the CLI in the app folder:
+To uninstall:
 
 ```bash
-reis-mobile doctor
-reis-mobile route "review architecture" --json
-reis-mobile review --json
-```
+# Claude Code
+claude plugin uninstall reis-mobile@reis-mobile
+claude plugin marketplace remove reis-mobile
 
-You can also ask Codex: *"Run `reis-mobile review --json`, read the instructions in the returned files and review the changes using that context."* The CLI selects the instructions and gathers the context; Codex does the analysis.
+# Codex
+codex plugin remove reis-mobile@reis-mobile
+codex plugin marketplace remove reis-mobile
+```
+</details>
 
-### Language
+<details>
+<summary>Language</summary>
 
-Agents, skills and commands are written in English, and that does not change. What you choose is the language reis-mobile **answers** in: `/reis-mobile:review` reports, `/reis-mobile:doctor` explanations, and debate rounds and syntheses.
+Agents, skills and commands are written in English. The language you choose is the one reis-mobile **answers** in: `/reis-mobile:review` reports, `/reis-mobile:doctor` explanations, and debate rounds and syntheses.
 
 ```bash
-reis-mobile init eng         # install the plugins and answer in English (also: en)
-reis-mobile init pt          # install the plugins and answer in Brazilian Portuguese
-reis-mobile lang eng         # change the language later, without reinstalling
+reis-mobile lang pt          # switch to Brazilian Portuguese without reinstalling
+reis-mobile lang eng         # switch to English
 reis-mobile lang             # show the current language
 ```
 
-The choice is saved to `~/.config/reis-mobile/config.json` (`%APPDATA%\reis-mobile\config.json` on Windows), so it survives `claude plugin update`. Precedence is `--lang` on a single run, then the `REIS_MOBILE_LANG` environment variable, then the saved file. With nothing set, each command answers in the language of your request. Agents that Claude Code triggers on its own, outside a `/reis-mobile:*` command, follow the language of the conversation.
+The choice is saved to `~/.config/reis-mobile/config.json` (`%APPDATA%\reis-mobile\config.json` on Windows) and survives plugin updates. `--lang` on a single run and the `REIS_MOBILE_LANG` environment variable override it. With nothing set, each command answers in the language of your request. Agents that Claude Code triggers on its own, outside a `/reis-mobile:*` command, follow the language of the conversation.
+</details>
 
 <details>
-<summary>Uninstall</summary>
+<summary>Using the CLI from Codex</summary>
+
+The Codex plugin gives Codex the skills; the agents and the `/reis-mobile:*` commands are Claude Code formats and have not been validated in Codex. For routing and review context, run the CLI in the app folder:
 
 ```bash
-reis-mobile init --uninstall        # plugin and marketplace in Claude Code and Codex, and the saved language
-npm uninstall -g reis-mobile        # CLI (the -g matters: without it npm looks in the current folder)
+reis-mobile doctor
+reis-mobile route "review architecture" --json
+reis-mobile review --json
 ```
+
+You can also ask Codex: *"Run `reis-mobile review --json`, read the instructions in the returned files and review the changes using that context."* The CLI selects the instructions and gathers the context; Codex does the analysis.
 </details>
 
 <details>
-<summary>Installed with Homebrew or the curl/PowerShell installer?</summary>
-
-Those channels were discontinued after v0.3.4. Remove them and install from npm:
-
-```bash
-# Homebrew
-brew uninstall reis-mobile && brew untap wrsilva/tap
+<summary>Troubleshooting</summary>
 
-# curl installer (macOS/Linux)
-rm -rf ~/.local/share/reis-mobile ~/.local/bin/reis-mobile
-```
+| Symptom | Solution |
+|---------|---------|
+| Codex says `plugin reis-mobile was not found in marketplace reis-mobile` | The marketplace is not registered or is outdated. Run `reis-mobile init eng`, or `codex plugin marketplace add https://github.com/wrsilva/reis-mobile.git` followed by `codex plugin add reis-mobile@reis-mobile` |
+| `claude plugin update` says it is already on the latest version, but the release is newer | Run `claude plugin marketplace update reis-mobile` before `update` |
+| New agents or skills do not show up | Restart Claude Code or Codex: plugins only reload in a new session |
+| `reis-mobile --version` still shows the old version after updating | Another `reis-mobile` comes first on the `PATH`; find it with `which -a reis-mobile` (`where.exe reis-mobile` on Windows) and remove it |
+| `npm uninstall reis-mobile` says `up to date` and the command is still there | Add `-g`: `npm uninstall -g reis-mobile` |
+| `/reis-mobile:*` commands missing after upgrading from v0.3.2 or v0.3.3 | Those versions named the plugin `mobile`. Run `reis-mobile init eng`: it installs `reis-mobile@reis-mobile` and removes `mobile@reis-mobile` |
+| Plugin broken after updating | Reinstall: `reis-mobile init --uninstall`, then `reis-mobile init eng` |
 
-```powershell
-# PowerShell installer (Windows)
-Remove-Item -Recurse -Force "$env:LOCALAPPDATA\reis-mobile"
-Remove-Item -Force "$HOME\.local\bin\reis-mobile.cmd"
-```
 </details>
 
 <details>
@@ -183,53 +193,7 @@ reis-mobile init --local      # plugin pointing at the clone
 npm run check                 # validates and runs the tests
 ```
 
-After editing agents, skills or commands, restart the Claude Code session.
-</details>
-
----
-
-## Updating
-
-To see what changed, check the [CHANGELOG](CHANGELOG.md) or the [releases](https://github.com/wrsilva/reis-mobile/releases).
-
-```bash
-npm update -g reis-mobile
-reis-mobile init eng         # refreshes the marketplace and the plugin in Claude Code and Codex
-```
-
-Without npm, update each tool by hand:
-
-```bash
-# Claude Code
-claude plugin marketplace update reis-mobile
-claude plugin update reis-mobile@reis-mobile
-
-# Codex
-codex plugin marketplace upgrade reis-mobile
-codex plugin add reis-mobile@reis-mobile
-```
-
-Then **restart Claude Code or Codex**. The plugin update only happens when a new version is out; if you are already on the latest, Claude Code answers `already at the latest version`.
-
-Check that the CLI and the plugin match:
-
-```bash
-reis-mobile --version
-claude plugin list | grep -A1 reis-mobile
-```
-
-> **Installed v0.3.2 or v0.3.3?** Those versions renamed the plugin and the CLI to `mobile`; v0.3.4 goes back to `reis-mobile`. Run `reis-mobile init eng`: in Claude Code and Codex it installs `reis-mobile@reis-mobile` and removes `mobile@reis-mobile`.
-
-<details>
-<summary>Update troubleshooting</summary>
-
-| Symptom | Solution |
-|---------|---------|
-| `claude plugin update` says it is already on the latest version, but the release is newer | Run `claude plugin marketplace update reis-mobile` before `update` |
-| New agents or skills do not show up | Restart Claude Code: plugins only reload in a new session |
-| `reis-mobile --version` is still old after `npm update -g` | Another `reis-mobile` comes first on the `PATH`, often from Homebrew or the old installers; check with `which -a reis-mobile` (`where.exe reis-mobile` on Windows) |
-| Plugin broken after updating | Reinstall: `reis-mobile init --uninstall` and then `reis-mobile init eng` |
-
+After editing agents, skills or commands, restart Claude Code or Codex.
 </details>
 
 ---
@@ -244,10 +208,17 @@ claude plugin list | grep -A1 reis-mobile
 /reis-mobile:review                               # Reviews uncommitted changes (or the whole project, if there are none)
 /reis-mobile:review --base main                   # Reviews the current branch against main, pull request style
 /reis-mobile:review --base main focus on security # Free-form focus, in English or Portuguese
+/reis-mobile:debug pod install fails on CI        # Finds the cause of a build or runtime failure and proposes the fix
 /reis-mobile:debate Riverpod or BLoC in this app? # Debate between the specialists, with a decision by lead-mobile
 /reis-mobile:debate --rounds 3 --external ...     # More rounds; --external adds Codex and Gemini, if installed
 ```
 
+### Debug
+
+`/reis-mobile:debug` takes the error, the failing command or a description of the problem. It routes to the debug agent and to the skills for the stack and the build area it recognizes (`gradle`, `xcode`, `cocoapods`, `signing`, `pub`...), adds the doctor report with the installed toolchain versions, and answers with the cause, the evidence, the minimal fix and how to verify it.
+
+It proposes; it does not change your project on its own. Commands that alter files or caches — `flutter clean`, `pod install`, deleting `DerivedData` or Gradle caches, dependency upgrades — only run after you ask it to apply the fix.
+
 ### Debate
 
 `/reis-mobile:debate` puts three specialists with conflicting priorities to defend positions on the same question. Round 1 is blind, so the first to answer does not anchor the others; in round 2 each one rebuts specific points from the others; at the end, `lead-mobile` decides and delivers the action plan. The rounds are stored in `.reis-mobile/debates/`.
@@ -265,13 +236,13 @@ $ reis-mobile route "Execution failed for task ':app:compileDebugKotlin'"
 Intent      debug (confidence 0.5) · area gradle
 Stack       flutter · focus android
 Agent       mobile-staff-engineer
-Skills      dart-fix-runtime-errors, dart-resolve-package-conflicts, flutter-errors, flutter-fix-layout-issues
+Skills      mobile-debug
 
 $ reis-mobile route "write tests for the login cubit"
 Intent      test (confidence 1)
 Stack       flutter
 Agent       flutter-test-engineer
-Skills      dart-add-unit-test, dart-collect-coverage, dart-generate-test-mocks, flutter-add-integration-test, flutter-add-widget-test, mockito, mocktail, patrol-e2e-testing, testing
+Skills      mobile-test
 ```
 
 The router never invents a specialist: if no agent serves the intent, it warns you. You do not need to call agents by name, because Claude Code triggers them by their description when the request fits. To force one of them, ask: *"use reis-mobile:flutter-architect to review the architecture"*.
@@ -286,17 +257,16 @@ The router never invents a specialist: if no agent serves the intent, it warns y
 | Review a PR or my changes | `/reis-mobile:review` | ✅ |
 | Audit an entire Flutter project | `/reis-mobile:review` with no pending changes | ✅ |
 | Find out a project's stack | `reis-mobile detect` | ✅ |
-| Review the architecture of a Flutter app | agent `flutter-architect` | ✅ |
-| Find the cause of jank, rebuilds or leaks | agent `flutter-performance-engineer` | ✅ |
-| Write or audit Flutter tests | agent `flutter-test-engineer` | ✅ |
-| Debug a Gradle, Xcode or CocoaPods build | agent `mobile-staff-engineer` | ✅ |
+| Review the architecture of an app | agent `flutter-architect`, `android-architect`, `ios-architect` or `rn-architect` | ✅ |
+| Find the cause of jank, rebuilds, hangs or leaks | agent `flutter-`, `android-`, `ios-` or `rn-performance-engineer` | ✅ |
+| Write or audit tests | agent `flutter-`, `android-`, `ios-` or `rn-test-engineer` | ✅ |
+| Debug a Gradle, Xcode, CocoaPods or Flutter build | `/reis-mobile:debug` | ✅ |
 | Build a plugin or debug MethodChannel/EventChannel | agent `plugin-native-expert` | ✅ |
 | Full audit with several specialists | agent `lead-mobile` | ✅ |
 | Decide between two architectures with a real trade-off | `/reis-mobile:debate` | ✅ |
-| Dedicated debug command | `/reis-mobile:debug` | 🔜 v0.4 |
-| Dedicated test command (including XCTest and Espresso) | `/reis-mobile:test` | 🔜 v0.4 |
-| Check whether the app is ready for the store | `/reis-mobile:release` | 🔜 v0.5 |
-| Consolidated decision by consensus between agents | `/reis-mobile:council` | 🔜 v0.8 |
+| Dedicated test command (including XCTest and Espresso) | `/reis-mobile:test` | 🔜 v0.6 |
+| Check whether the app is ready for the store | `/reis-mobile:release` | 🔜 v0.7 |
+| Consolidated decision by consensus between agents | `/reis-mobile:council` | 🔜 v0.9 |
 
 <details>
 <summary><strong>How is it different from plain Claude Code?</strong></summary>
@@ -307,8 +277,8 @@ The router never invents a specialist: if no agent serves the intent, it warns y
 | **Project context** | You explain the stack | Deterministic detection of stack, platform and variant |
 | **Review** | Generic | Mobile checklists: lifecycle, `BuildContext`, MASVS, manifest, ATS |
 | **Secrets in the diff** | Sent as they are | Masked before reaching the model |
-| **Specialists** | None | 7 agents and 67 mobile skills |
-| **Context cost** | Zero | ~4,800 fixed tokens (agent and skill descriptions), no hooks |
+| **Specialists** | None | 16 agents and 11 mobile skills |
+| **Context cost** | Zero | ~3,900 fixed tokens (agent and skill descriptions), no hooks |
 | **Best for** | General tasks | Teams and developers working on mobile apps |
 
 **In short:** Claude Code already knows how to code. reis-mobile makes it look at what matters in a mobile app.
@@ -325,7 +295,7 @@ The router never invents a specialist: if no agent serves the intent, it warns y
      ├─ detect stack ──────── pubspec.yaml → flutter (android, ios)
      ├─ detect intent ─────── review
      ├─ select agent ──────── mobile-code-reviewer
-     ├─ select skills ─────── code-review · effective-dart · flutter-project-audit · flutter-widget-review · mobile-security-audit …
+     ├─ select skills ─────── mobile-code-review · mobile-flutter · mobile-security
      ├─ collect context ───── git diff (lock files out, secrets masked)
      └─ review report ─────── Summary · Critical · Bugs · Architecture · Security · Performance · Maintainability
 ```
@@ -350,180 +320,42 @@ The Node.js core decides **what** to load. The model decides **how** to review,
 | `flutter-architect` | Flutter | architecture | Layers, feature-first, coupling, misplaced logic, refactoring plan |
 | `flutter-performance-engineer` | Flutter | performance | Rebuilds, jank, lists, leaks, paint, startup, with a score and top 3 fixes |
 | `flutter-test-engineer` | Flutter | test | Unit, BLoC/Cubit, widget and integration, coverage audit and fragile tests |
+| `android-architect` | Android | architecture | UI, domain and data layers, Gradle modules, ViewModel and DI boundaries |
+| `android-performance-engineer` | Android | performance | Compose recomposition, lists, ANRs, startup, leaks, app size |
+| `android-test-engineer` | Android | test | ViewModel and coroutine tests, Compose and Espresso UI tests, flaky tests |
+| `ios-architect` | iOS | architecture | SwiftUI and UIKit structure, packages, navigation, concurrency boundaries |
+| `ios-performance-engineer` | iOS | performance | Hangs, SwiftUI updates, lists, launch time, retain cycles, memory |
+| `ios-test-engineer` | iOS | test | Swift Testing and XCTest unit tests, async code, XCUITest flows |
+| `rn-architect` | React Native | architecture | Feature structure, server vs client state, navigation, native modules |
+| `rn-performance-engineer` | React Native | performance | Re-renders, lists, JavaScript thread, animations, startup, bundle size |
+| `rn-test-engineer` | React Native | test | Jest, React Native Testing Library, native module mocks, Detox or Maestro |
 | `mobile-staff-engineer` | all | debug, architecture, performance, test, security, release, migration, dependency, build, deployment, accessibility | Senior Flutter/Android/iOS specialist for whatever no specific agent covers |
 | `plugin-native-expert` | Flutter | on demand | MethodChannel, EventChannel, Pigeon and Kotlin/Swift bridges, threading and lifecycle |
 | `lead-mobile` | all | on demand | Coordinates the other agents and consolidates a single action plan |
 
-When more than one agent serves the intent, the stack-specific one wins. In a Flutter app, `performance` goes to `flutter-performance-engineer`; in a native Android app, it goes to `mobile-staff-engineer`.
+When more than one agent serves the intent, the stack-specific one wins. In a Flutter app, `performance` goes to `flutter-performance-engineer`; in a native Android app, to `android-performance-engineer`. Intents without a stack specialist, such as `debug` or `release`, go to `mobile-staff-engineer`.
 
 ### Skills
 
-**Auto-routed** skills are loaded by the router together with the agent. The others (—) are triggered by Claude Code when the request matches the description, for example *"add push notifications with FCM"* → `firebase-messaging`.
-
-<details>
-<summary><strong>Review and quality</strong> (7)</summary>
-
-| Skill | What it does | Auto-routed for | Stack | Origin |
-|---|---|---|---|---|
-| `code-review` | Performs thorough code reviews for Flutter/Dart pull requests and merge requests. | review | Flutter | evanca/flutter-ai-rules |
-| `effective-dart` | Applies Effective Dart guidelines in Flutter/Dart code. | review | Flutter | evanca/flutter-ai-rules |
-| `dart-run-static-analysis` | Execute `dart analyze` to identify warnings and errors, and use `dart fix --apply` to automatically resolve… | review | Flutter | dart-lang/skills |
-| `flutter-project-audit` | Audits the health of a Flutter project as a whole — pubspec constraints and lock file, analysis_options and lints,… | review, architecture, dependency | Flutter | reis-mobile |
-| `flutter-widget-review` | Reviews Flutter widget code for lifecycle bugs, BuildContext misuse across async gaps, missing dispose, side effects… | review, performance | Flutter | reis-mobile |
-| `dart-3-updates` | Applies Dart 3 language features in Flutter/Dart code. | migration | Flutter | evanca/flutter-ai-rules |
-| `dart-use-pattern-matching` | Applies Dart 3 pattern matching, switch expressions, and destructuring idiomatically to validate data schemas,… | — | Flutter | dart-lang/skills |
-
-</details>
-
-<details>
-<summary><strong>Architecture and state</strong> (9)</summary>
-
-| Skill | What it does | Auto-routed for | Stack | Origin |
-|---|---|---|---|---|
-| `architecture-feature-first` | Structures Flutter apps using layered architecture (UI / Logic / Data) with feature-first file organization. | architecture | Flutter | evanca/flutter-ai-rules |
-| `flutter-app-architecture` | Provides best practices for Flutter app architecture, including layered architecture, data flow, state management… | architecture | Flutter | evanca/flutter-ai-rules |
-| `flutter-apply-architecture-best-practices` | Architects a Flutter application using the recommended layered approach (UI, Logic, Data). | architecture | Flutter | flutter/skills |
-| `flutter-managing-state` | Manages application and ephemeral state in a Flutter app. | architecture | Flutter | flutter/skills |
-| `bloc` | Implements Flutter state management using the bloc library (Bloc and Cubit). | — | Flutter | evanca/flutter-ai-rules |
-| `riverpod` | Uses Riverpod for state management in Flutter/Dart. | — | Flutter | evanca/flutter-ai-rules |
-| `provider` | Uses the Provider package for dependency injection and state management in Flutter. | — | Flutter | evanca/flutter-ai-rules |
-| `flutter-change-notifier` | Implements state management with ChangeNotifier and Provider in Flutter. | — | Flutter | evanca/flutter-ai-rules |
-| `flutter-login-usecase` | Implements a Flutter login use case that authenticates through an injected repository and persists the access token… | — | Flutter | reis-mobile |
-
-</details>
-
-<details>
-<summary><strong>Testing</strong> (10)</summary>
-
-| Skill | What it does | Auto-routed for | Stack | Origin |
-|---|---|---|---|---|
-| `testing` | Writes and reviews Flutter/Dart tests. | test | Flutter | evanca/flutter-ai-rules |
-| `dart-add-unit-test` | Write and organize unit tests for functions, methods, and classes using `package:test`. | test | Flutter | dart-lang/skills |
-| `flutter-add-widget-test` | Implement a component-level test using `WidgetTester` to verify UI rendering and user interactions (tapping,… | test | Flutter | flutter/skills |
-| `flutter-add-integration-test` | Configures Flutter Driver for app interaction and converts MCP actions into permanent integration tests. | test | Flutter | flutter/skills |
-| `patrol-e2e-testing` | Generates and maintains end-to-end tests for Flutter apps using Patrol. | test | Flutter | evanca/flutter-ai-rules |
-| `mocktail` | Uses the Mocktail package for mocking in Flutter/Dart tests. | test | Flutter | evanca/flutter-ai-rules |
-| `mockito` | Uses the Mockito package for mocking in Flutter/Dart tests. | test | Flutter | evanca/flutter-ai-rules |
-| `dart-generate-test-mocks` | Define and generate mock objects for external dependencies using `package:mockito` and `build_runner`. | test | Flutter | dart-lang/skills |
-| `dart-collect-coverage` | Collect coverage using the coverage packge and create an LCOV report | test | Flutter | dart-lang/skills |
-| `dart-migrate-to-checks-package` | Replace the usage of `expect` and similar functions from `package:matcher` to `package:checks` equivalents. | migration | Flutter | dart-lang/skills |
-
-</details>
-
-<details>
-<summary><strong>Debug</strong> (4)</summary>
-
-| Skill | What it does | Auto-routed for | Stack | Origin |
-|---|---|---|---|---|
-| `flutter-errors` | Diagnoses and fixes common Flutter errors. | debug | Flutter | evanca/flutter-ai-rules |
-| `flutter-fix-layout-issues` | Fixes Flutter layout errors (overflows, unbounded constraints) using Dart and Flutter MCP tools. | debug | Flutter | flutter/skills |
-| `dart-fix-runtime-errors` | Uses get_runtime_errors and lsp to fetch an active stack trace, locate the failing line, apply a fix, and verify… | debug | Flutter | dart-lang/skills |
-| `dart-resolve-package-conflicts` | Workflow for fixing package version conflicts. | debug, dependency | Flutter | dart-lang/skills |
-
-</details>
-
-<details>
-<summary><strong>Performance</strong> (3)</summary>
-
-| Skill | What it does | Auto-routed for | Stack | Origin |
-|---|---|---|---|---|
-| `flutter-reducing-app-size` | Measures and optimizes the size of Flutter application bundles for deployment. | performance | Flutter | flutter/skills |
-| `flutter-handling-concurrency` | Executes long-running tasks in background isolates to keep the UI responsive. | performance | Flutter | flutter/skills |
-| `flutter-caching-data` | Implements caching strategies for Flutter apps to improve performance and offline support. | — | Flutter | flutter/skills |
-
-</details>
-
-<details>
-<summary><strong>UI, layout and navigation</strong> (8)</summary>
-
-| Skill | What it does | Auto-routed for | Stack | Origin |
-|---|---|---|---|---|
-| `flutter-building-layouts` | Builds Flutter layouts using the constraint system and layout widgets. | — | Flutter | flutter/skills |
-| `flutter-build-responsive-layout` | Use `LayoutBuilder`, `MediaQuery`, or `Expanded/Flexible` to create a layout that adapts to different screen sizes. | — | Flutter | flutter/skills |
-| `flutter-building-forms` | Builds Flutter forms with validation and user input handling. | — | Flutter | flutter/skills |
-| `flutter-animating-apps` | Implements animated effects, transitions, and motion in a Flutter app. | — | Flutter | flutter/skills |
-| `flutter-theming-apps` | Customizes the visual appearance of a Flutter app using the theming system. | — | Flutter | flutter/skills |
-| `flutter-add-widget-preview` | Adds interactive widget previews to the project using the previews.dart system. | — | Flutter | flutter/skills |
-| `flutter-setup-declarative-routing` | Configure `MaterialApp.router` using a package like `go_router` for advanced URL-based navigation. | — | Flutter | flutter/skills |
-| `flutter-adding-home-screen-widgets` | Adds home screen widgets to a Flutter app for Android and iOS. | — | Flutter | flutter/skills |
-
-</details>
-
-<details>
-<summary><strong>Data and networking</strong> (3)</summary>
+Every skill starts with `mobile-`. **Topic** skills cover every stack with one reference per platform; **platform** skills hold what exists only on one stack. A request loads the skill, and the model then opens only the reference for your stack and task.
 
-| Skill | What it does | Auto-routed for | Stack | Origin |
-|---|---|---|---|---|
-| `flutter-use-http-package` | Use the `http` package to execute GET, POST, PUT, or DELETE requests. | — | Flutter | flutter/skills |
-| `flutter-implement-json-serialization` | Create model classes with `fromJson` and `toJson` methods using `dart:convert`. | — | Flutter | flutter/skills |
-| `flutter-working-with-databases` | Manages local data persistence using SQLite or other database solutions. | — | Flutter | flutter/skills |
-
-</details>
-
-<details>
-<summary><strong>Native and plugins</strong> (3)</summary>
+| Skill | Covers | Auto-routed for | References |
+|---|---|---|---|
+| `mobile-architecture` | Layers, state management, modularization, DI, navigation | architecture | Flutter (BLoC, Riverpod, Provider, ChangeNotifier...), Android, iOS, React Native |
+| `mobile-code-review` | Review process and checklists | review, performance | Flutter (PR review, widgets, project audit, static analysis), Android, iOS, React Native |
+| `mobile-debug` | Failing builds and runtime errors | debug, build, dependency, migration | Flutter (build, runtime, layout, packages), Android (Gradle, crashes, ANRs), iOS (Xcode, CocoaPods, crash logs), React Native (Metro, native modules) |
+| `mobile-test` | Unit, UI, integration and end-to-end tests | test | Flutter (widget, integration, Patrol, mocks, coverage), Android, iOS, React Native |
+| `mobile-security` | OWASP MASVS security checks | review, security, release | Flutter (token storage), Android (intents), iOS, React Native |
+| `mobile-firebase` | Firebase setup and 13 products | — | Flutter, Android, iOS, React Native, each with a guide per product |
+| `mobile-flutter` | Flutter and Dart specifics | review, performance, accessibility, migration | UI and navigation, data, native code, performance, accessibility and i18n, Dart, setup |
+| `mobile-android` | Native Android specifics, from the Android team | performance, release, migration, build, dependency | Compose UI, AGP 9 and R8, profiling, Google Play, identity, camera and media, on-device AI, Wear OS, TV, XR |
+| `mobile-ios` | Native iOS specifics | performance, release, accessibility | UI and navigation, data and networking, platform features, performance and release |
+| `mobile-rn` | React Native and Expo specifics | performance, release, accessibility | UI and navigation, data and networking, platform features, performance and release |
+| `mobile-detect-stack` | Deterministic stack detection with the CLI | — | — |
 
-| Skill | What it does | Auto-routed for | Stack | Origin |
-|---|---|---|---|---|
-| `flutter-building-plugins` | Builds Flutter plugins that provide native interop for other apps to use. | — | Flutter | flutter/skills |
-| `flutter-interoperating-with-native-apis` | Interoperates with native platform APIs on Android, iOS, and the web. | — | Flutter | flutter/skills |
-| `flutter-embedding-native-views` | Embeds native Android, iOS, or macOS views into a Flutter app. | — | Flutter | flutter/skills |
+Skills marked — are triggered by Claude Code when the request matches their description, for example *"add push notifications with FCM"* → `mobile-firebase`.
 
-</details>
-
-<details>
-<summary><strong>Security</strong> (3)</summary>
-
-| Skill | What it does | Auto-routed for | Stack | Origin |
-|---|---|---|---|---|
-| `mobile-security-audit` | Security audit for mobile apps based on the OWASP MASVS categories — insecure token storage, hardcoded secrets,… | review, security, release | all | reis-mobile |
-| `flutter-secure-token-store` | Stores JWT access tokens on Flutter with platform secure storage (Keychain on iOS, Keystore-backed storage on… | security | Flutter | reis-mobile |
-| `firebase-app-check` | Integrates Firebase App Check into Flutter apps. | security | Flutter | evanca/flutter-ai-rules |
-
-</details>
-
-<details>
-<summary><strong>Accessibility and internationalization</strong> (2)</summary>
-
-| Skill | What it does | Auto-routed for | Stack | Origin |
-|---|---|---|---|---|
-| `flutter-improving-accessibility` | Configures a Flutter app to support assistive technologies like Screen Readers. | accessibility | Flutter | flutter/skills |
-| `flutter-setup-localization` | Add `flutter_localizations` and `intl` dependencies, enable "generate true" in `pubspec.yaml`, and create an… | — | Flutter | flutter/skills |
-
-</details>
-
-<details>
-<summary><strong>Firebase</strong> (13)</summary>
-
-| Skill | What it does | Auto-routed for | Stack | Origin |
-|---|---|---|---|---|
-| `flutterfire-configure` | Sets up Firebase for Flutter apps using FlutterFire CLI. | — | Flutter | evanca/flutter-ai-rules |
-| `firebase-auth` | Integrates Firebase Authentication into Flutter apps. | — | Flutter | evanca/flutter-ai-rules |
-| `firebase-cloud-firestore` | Integrates Cloud Firestore into Flutter apps. | — | Flutter | evanca/flutter-ai-rules |
-| `firebase-database` | Integrates Firebase Realtime Database into Flutter apps. | — | Flutter | evanca/flutter-ai-rules |
-| `firebase-storage` | Integrates Firebase Cloud Storage into Flutter apps. | — | Flutter | evanca/flutter-ai-rules |
-| `firebase-cloud-functions` | Calls Firebase Cloud Functions from Flutter apps. | — | Flutter | evanca/flutter-ai-rules |
-| `firebase-messaging` | Integrates Firebase Cloud Messaging (FCM) into Flutter apps. | — | Flutter | evanca/flutter-ai-rules |
-| `firebase-in-app-messaging` | Integrates Firebase In-App Messaging into Flutter apps. | — | Flutter | evanca/flutter-ai-rules |
-| `firebase-remote-config` | Integrates Firebase Remote Config into Flutter apps. | — | Flutter | evanca/flutter-ai-rules |
-| `firebase-analytics` | Integrates Firebase Analytics into Flutter apps. | — | Flutter | evanca/flutter-ai-rules |
-| `firebase-crashlytics` | Integrates Firebase Crashlytics into Flutter apps. | — | Flutter | evanca/flutter-ai-rules |
-| `firebase-ai` | Integrates Firebase AI Logic into Flutter apps. | — | Flutter | evanca/flutter-ai-rules |
-| `firebase-data-connect` | Integrates Firebase Data Connect into Flutter apps. | — | Flutter | evanca/flutter-ai-rules |
-
-</details>
-
-<details>
-<summary><strong>Environment</strong> (2)</summary>
-
-| Skill | What it does | Auto-routed for | Stack | Origin |
-|---|---|---|---|---|
-| `flutter-setting-up-on-macos` | Sets up a macOS environment for Flutter development. | — | Flutter | flutter/skills |
-| `detect-mobile-stack` | Detects the mobile stack of the current project (Flutter, Android, iOS, React Native, Kotlin Multiplatform), its… | — | all | reis-mobile |
-
-</details>
-
-Third-party skills keep their original name and license. See [THIRD_PARTY_NOTICES.md](THIRD_PARTY_NOTICES.md).
+About 85 guides come from [flutter/skills](https://github.com/flutter/skills), [dart-lang/skills](https://github.com/dart-lang/skills), [evanca/flutter-ai-rules](https://github.com/evanca/flutter-ai-rules) and [android/skills](https://github.com/android/skills), unchanged and credited in [THIRD_PARTY_NOTICES.md](THIRD_PARTY_NOTICES.md).
 
 ---
 
@@ -533,11 +365,11 @@ Third-party skills keep their original name and license. See [THIRD_PARTY_NOTICE
 
 **Secrets masked.** The diff goes through [`core/security/redact.mjs`](core/security/redact.mjs) before reaching the model. Lock files and generated code (`*.g.dart`, `*.freezed.dart`, `*.pbxproj`) stay out of the diff. Redaction is a protection layer, not a guarantee. See [SECURITY.md](SECURITY.md).
 
-**No telemetry.** `detect`, `doctor`, `route` and `review` make no network calls. Only installation touches the network, to download the package and register the plugin. The AI analysis uses the model of the session you are working in, such as Claude Code or Codex.
+**No telemetry.** `detect`, `doctor`, `route`, `review` and `debug` make no network calls. Only installation touches the network, to download the package and register the plugin. The Google Play policy guide in `mobile-android` runs Python scripts that download your app's public Google Play listing when the model uses it. The AI analysis uses the model of the session you are working in, such as Claude Code or Codex.
 
 **Exception: `/reis-mobile:debate --external`.** This flag, and only this flag, sends the debate context — including excerpts of the files mentioned in the question — to the `codex` and `gemini` CLIs, which are third-party and have their own data policies. Without the flag, nothing leaves your session. The `review` diff is masked by `redact.mjs`, but the context you cite in a debate question does not go through that layer: check what you are sending before using `--external`.
 
-**Context cost.** The descriptions of the 7 agents and 67 skills add up to about 4,800 fixed tokens per session (measured with `claude plugin details reis-mobile`). The full content of each skill is only loaded when it is used.
+**Context cost.** The descriptions of the 16 agents and 11 skills add up to about 3,900 fixed tokens per session, estimated from their length (v0.3 measured about 4,800 with `claude plugin details reis-mobile`). The full content of each skill is only loaded when it is used.
 
 **No hooks.** The plugin does not attach to Claude Code events. It only acts when you call a command or when a skill is relevant.
 
@@ -559,10 +391,10 @@ Third-party skills keep their original name and license. See [THIRD_PARTY_NOTICE
 | v0.3.4 | Back to the `reis-mobile` name after the `mobile` renames of v0.3.2 and v0.3.3 | ✅ |
 | v0.3.5 | Distribution through npm and the Claude Code and Codex plugins only | ✅ |
 | v0.3.6 | `reis-mobile init` installs in Claude Code and Codex | ✅ |
-| v0.4.0 | Native Android and iOS skills, `.reis-mobile/config.yaml` and `/reis-mobile:debug` (Gradle, Xcode, CocoaPods, Flutter) | ⏳ |
-| v0.5.0 | `/reis-mobile:test` and native tests (XCTest, Espresso) | ⏳ |
-| v0.6.0 | `/reis-mobile:release` with quality gates | ⏳ |
-| v0.7.0 | React Native pack | ⏳ |
+| v0.4.0 | Native Android and iOS skills, architect, performance and test agents for Android, iOS and React Native, `.reis-mobile/config.yaml` and `/reis-mobile:debug` (Gradle, Xcode, CocoaPods, Flutter) | ✅ |
+| v0.5.0 | Topic and platform skills (`mobile-*`), with guides for Flutter, Android, iOS and React Native in each; new `mobile-ios` and `mobile-rn` | ✅ |
+| v0.6.0 | `/reis-mobile:test` and native tests (XCTest, Espresso) | ⏳ |
+| v0.7.0 | `/reis-mobile:release` with quality gates | ⏳ |
 | v0.8.0 | MCP server | ⏳ |
 | v0.9.0 | Multi-provider (OpenAI, Gemini, OpenRouter, Ollama) beyond the debate's `--external` | ⏳ |
 | v1.0.0 | First stable version: Flutter, Android, iOS and React Native | ⏳ |
@@ -575,16 +407,22 @@ Third-party skills keep their original name and license. See [THIRD_PARTY_NOTICE
 Not for the review, which only reads code. `/reis-mobile:doctor` shows what is missing in case you want to build.
 
 **My app lives inside a monorepo.**
-Run it from the app folder, or use `--dir apps/mobile` in the CLI. The diff is restricted to that folder.
+Commit a `.reis-mobile/config.yaml` at the repository root pointing at the app:
+
+```yaml
+app: apps/mobile
+```
+
+Every command then analyzes `apps/mobile`, wherever in the repository you run it, and the review diff is restricted to that folder. Without the file, run from the app folder or pass `--dir apps/mobile`.
 
 **Does it work with native Android and iOS?**
-Detection, the doctor, the security skill and the `mobile-code-reviewer`, `mobile-staff-engineer` and `lead-mobile` agents already work. Android- and iOS-specific skills arrive in v0.4.0; the 63 imported skills are for Flutter, Dart and Firebase.
+Yes. Native Android, native iOS and React Native each have architect, performance and test agents, and the cross-platform skills — `mobile-debug`, `mobile-code-review`, `mobile-test` and `mobile-firebase` — have a guide for each of them (Gradle and R8, Xcode and CocoaPods, Metro and native modules). The platform skills `mobile-android`, `mobile-ios` and `mobile-rn` add what exists only on each stack; `mobile-android` includes the Android team's guides from `android/skills` (Compose, AGP 9, R8, Play policy, Wear, TV and more).
 
 **I already have skills with the same names in `~/.claude/skills`.**
 The plugin's skills live in the `reis-mobile:` namespace and do not conflict, but Claude Code loads both descriptions. To save context, remove the global copies the plugin already covers.
 
 **Does it work in Codex?**
-The marketplace and plugin `0.2.1` can be installed straight from GitHub with `codex plugin`. See [installation](#quick-install-claude-code-and-codex) and [using the CLI from Codex](#using-the-cli-from-codex). Installation does not confirm parity with the Claude Code agents and commands; the `reis-mobile` CLI can also be run by Codex to get diagnostics and context.
+Yes: `reis-mobile init eng` installs the plugin in Codex too. See [installation](#install). Installation does not confirm parity with the Claude Code agents and commands; the `reis-mobile` CLI can also be run by Codex to get diagnostics and context.
 
 **Does it work in Cursor?**
 The Cursor integration has not been validated yet. The MCP server remains on the roadmap for v0.8.0.
@@ -625,7 +463,7 @@ Questions: [Discussions](https://github.com/wrsilva/reis-mobile/discussions). Wh
 - **[flutter/skills](https://github.com/flutter/skills)** (BSD-3-Clause): 25 Flutter skills.
 - **[dart-lang/skills](https://github.com/dart-lang/skills)** (BSD-3-Clause): 8 Dart skills.
 - **[evanca/flutter-ai-rules](https://github.com/evanca/flutter-ai-rules)** (MIT): 28 Flutter, testing and Firebase skills.
-- **[OWASP MASVS](https://mas.owasp.org/MASVS/)**: categories used in the `mobile-security-audit` skill.
+- **[OWASP MASVS](https://mas.owasp.org/MASVS/)**: categories used in the `mobile-security` skill.
 
 ---