reis-mobile 0.3.6 → 0.5.0

package/skills/{flutter-setting-up-on-macos/SKILL.md → mobile-flutter/references/setup/macos.md}

@@ -1,14 +1,5 @@
----
-name: flutter-setting-up-on-macos
-description: Sets up a macOS environment for Flutter development. Use when configuring a macOS machine to run, build, or deploy Flutter applications for iOS or macOS.
-metadata:
-  model: models/gemini-3.1-pro-preview
-  last_modified: Thu, 12 Mar 2026 22:12:50 GMT
-routing: manual
-stacks: [flutter]
-source: https://github.com/flutter/skills
-license: BSD-3-Clause
----
+> Adapted from the `flutter-setting-up-on-macos` skill in [flutter/skills](https://github.com/flutter/skills) (BSD-3-Clause). See `THIRD_PARTY_NOTICES.md`.
+
 # Setting Up a macOS Environment for Flutter Development
 
 ## Contents

package/skills/mobile-flutter/references/setup.md

@@ -0,0 +1,7 @@
+# Flutter: Environment
+
+Setting up the development machine. Open only the guide the task needs.
+
+| Guide | What it covers |
+|---|---|
+| [macos](setup/macos.md) | Sets up a macOS environment for Flutter development. |

package/skills/{flutter-animating-apps/SKILL.md → mobile-flutter/references/ui/animations.md}

@@ -1,14 +1,5 @@
----
-name: flutter-animating-apps
-description: Implements animated effects, transitions, and motion in a Flutter app. Use when adding visual feedback, shared element transitions, or physics-based animations.
-metadata:
-  model: models/gemini-3.1-pro-preview
-  last_modified: Thu, 12 Mar 2026 22:16:34 GMT
-routing: manual
-stacks: [flutter]
-source: https://github.com/flutter/skills
-license: BSD-3-Clause
----
+> Adapted from the `flutter-animating-apps` skill in [flutter/skills](https://github.com/flutter/skills) (BSD-3-Clause). See `THIRD_PARTY_NOTICES.md`.
+
 # Implementing Flutter Animations
 
 ## Contents

package/skills/{flutter-building-forms/SKILL.md → mobile-flutter/references/ui/forms.md}

@@ -1,14 +1,5 @@
----
-name: flutter-building-forms
-description: Builds Flutter forms with validation and user input handling. Use when creating login screens, data entry forms, or any multi-field user input.
-metadata:
-  model: models/gemini-3.1-pro-preview
-  last_modified: Thu, 12 Mar 2026 22:15:24 GMT
-routing: manual
-stacks: [flutter]
-source: https://github.com/flutter/skills
-license: BSD-3-Clause
----
+> Adapted from the `flutter-building-forms` skill in [flutter/skills](https://github.com/flutter/skills) (BSD-3-Clause). See `THIRD_PARTY_NOTICES.md`.
+
 # Building Validated Forms
 
 ## Contents

package/skills/{flutter-adding-home-screen-widgets/SKILL.md → mobile-flutter/references/ui/home-screen-widgets.md}

@@ -1,14 +1,5 @@
----
-name: flutter-adding-home-screen-widgets
-description: Adds home screen widgets to a Flutter app for Android and iOS. Use when providing glanceable app information or quick actions on the device home screen.
-metadata:
-  model: models/gemini-3.1-pro-preview
-  last_modified: Thu, 12 Mar 2026 22:23:50 GMT
-routing: manual
-stacks: [flutter]
-source: https://github.com/flutter/skills
-license: BSD-3-Clause
----
+> Adapted from the `flutter-adding-home-screen-widgets` skill in [flutter/skills](https://github.com/flutter/skills) (BSD-3-Clause). See `THIRD_PARTY_NOTICES.md`.
+
 # Implementing Flutter Home Screen Widgets
 
 ## Contents

package/skills/{flutter-building-layouts/SKILL.md → mobile-flutter/references/ui/layouts.md}

@@ -1,14 +1,5 @@
----
-name: flutter-building-layouts
-description: Builds Flutter layouts using the constraint system and layout widgets. Use when creating or refining the UI structure of a Flutter application.
-metadata:
-  model: models/gemini-3.1-pro-preview
-  last_modified: Thu, 12 Mar 2026 22:14:15 GMT
-routing: manual
-stacks: [flutter]
-source: https://github.com/flutter/skills
-license: BSD-3-Clause
----
+> Adapted from the `flutter-building-layouts` skill in [flutter/skills](https://github.com/flutter/skills) (BSD-3-Clause). See `THIRD_PARTY_NOTICES.md`.
+
 # Architecting Flutter Layouts
 
 ## Contents

package/skills/{flutter-build-responsive-layout/SKILL.md → mobile-flutter/references/ui/responsive-layout.md}

@@ -1,14 +1,5 @@
----
-name: flutter-build-responsive-layout
-description: Use `LayoutBuilder`, `MediaQuery`, or `Expanded/Flexible` to create a layout that adapts to different screen sizes. Use when you need the UI to look good on both mobile and tablet/desktop form factors.
-metadata:
-  model: models/gemini-3.1-pro-preview
-  last_modified: Tue, 21 Apr 2026 20:17:40 GMT
-routing: manual
-stacks: [flutter]
-source: https://github.com/flutter/skills
-license: BSD-3-Clause
----
+> Adapted from the `flutter-build-responsive-layout` skill in [flutter/skills](https://github.com/flutter/skills) (BSD-3-Clause). See `THIRD_PARTY_NOTICES.md`.
+
 # Implementing Adaptive Layouts
 
 ## Contents

package/skills/{flutter-setup-declarative-routing/SKILL.md → mobile-flutter/references/ui/routing.md}

@@ -1,14 +1,5 @@
----
-name: flutter-setup-declarative-routing
-description: Configure `MaterialApp.router` using a package like `go_router` for advanced URL-based navigation. Use when developing web applications or mobile apps that require specific deep linking and browser history support.
-metadata:
-  model: models/gemini-3.1-pro-preview
-  last_modified: Tue, 21 Apr 2026 21:08:03 GMT
-routing: manual
-stacks: [flutter]
-source: https://github.com/flutter/skills
-license: BSD-3-Clause
----
+> Adapted from the `flutter-setup-declarative-routing` skill in [flutter/skills](https://github.com/flutter/skills) (BSD-3-Clause). See `THIRD_PARTY_NOTICES.md`.
+
 # Implementing Routing and Deep Linking
 
 ## Contents

package/skills/{flutter-theming-apps/SKILL.md → mobile-flutter/references/ui/theming.md}

@@ -1,14 +1,5 @@
----
-name: flutter-theming-apps
-description: Customizes the visual appearance of a Flutter app using the theming system. Use when defining global styles, colors, or typography for an application.
-metadata:
-  model: models/gemini-3.1-pro-preview
-  last_modified: Thu, 12 Mar 2026 22:14:47 GMT
-routing: manual
-stacks: [flutter]
-source: https://github.com/flutter/skills
-license: BSD-3-Clause
----
+> Adapted from the `flutter-theming-apps` skill in [flutter/skills](https://github.com/flutter/skills) (BSD-3-Clause). See `THIRD_PARTY_NOTICES.md`.
+
 # Implementing Flutter Theming and Adaptive Design
 
 ## Contents

package/skills/{flutter-add-widget-preview/SKILL.md → mobile-flutter/references/ui/widget-previews.md}

@@ -1,14 +1,5 @@
----
-name: flutter-add-widget-preview
-description: Adds interactive widget previews to the project using the previews.dart system. Use when creating new UI components or updating existing screens to ensure consistent design and interactive testing.
-metadata:
-  model: models/gemini-3.1-pro-preview
-  last_modified: Tue, 21 Apr 2026 20:05:23 GMT
-routing: manual
-stacks: [flutter]
-source: https://github.com/flutter/skills
-license: BSD-3-Clause
----
+> Adapted from the `flutter-add-widget-preview` skill in [flutter/skills](https://github.com/flutter/skills) (BSD-3-Clause). See `THIRD_PARTY_NOTICES.md`.
+
 # Previewing Flutter Widgets
 
 ## Contents

package/skills/mobile-flutter/references/ui.md

@@ -0,0 +1,14 @@
+# Flutter: UI, layout and navigation
+
+Layouts, forms, animations, theming, routing and widgets outside the app. Open only the guide the task needs.
+
+| Guide | What it covers |
+|---|---|
+| [layouts](ui/layouts.md) | Builds Flutter layouts using the constraint system and layout widgets. |
+| [responsive-layout](ui/responsive-layout.md) | Use `LayoutBuilder`, `MediaQuery`, or `Expanded/Flexible` to create a layout that adapts to different screen sizes. |
+| [forms](ui/forms.md) | Builds Flutter forms with validation and user input handling. |
+| [animations](ui/animations.md) | Implements animated effects, transitions, and motion in a Flutter app. |
+| [theming](ui/theming.md) | Customizes the visual appearance of a Flutter app using the theming system. |
+| [routing](ui/routing.md) | Configure `MaterialApp.router` using a package like `go_router` for advanced URL-based navigation. |
+| [widget-previews](ui/widget-previews.md) | Adds interactive widget previews to the project using the previews.dart system. |
+| [home-screen-widgets](ui/home-screen-widgets.md) | Adds home screen widgets to a Flutter app for Android and iOS. |

package/skills/mobile-ios/SKILL.md

@@ -0,0 +1,25 @@
+---
+name: mobile-ios
+description: Builds native iOS apps in Swift — SwiftUI and UIKit screens, state and data flow, NavigationStack, lists, forms and accessibility; networking with URLSession and Codable, persistence with SwiftData, Core Data, files and the Keychain; permissions, push notifications, universal links, background tasks, widgets, App Intents and StoreKit 2 purchases; performance with Instruments and MetricKit; and release with signing, TestFlight and App Store Connect. Use when writing or changing native iOS code, adding a platform feature, preparing a build for TestFlight or the App Store, or when the user asks how to do something on iOS, even if they do not name the framework.
+intents: [performance, release, accessibility]
+stacks: [ios]
+---
+
+# Mobile iOS
+
+Guides for building native iOS apps. Cross-platform topics live in their own skills and have iOS references there: architecture in `mobile-architecture`, tests in `mobile-test`, debugging (Xcode, CocoaPods, crashes) in `mobile-debug`, code review in `mobile-code-review`, security in `mobile-security` and Firebase in `mobile-firebase`.
+
+## Pick the topic
+
+| Topic | Read |
+|---|---|
+| SwiftUI and UIKit screens, navigation, lists, forms, accessibility, localization | [references/ui-navigation.md](references/ui-navigation.md) |
+| Networking, JSON, persistence, caching, offline | [references/data-networking.md](references/data-networking.md) |
+| Permissions, push, universal links, background work, widgets, App Intents, in-app purchases | [references/platform-features.md](references/platform-features.md) |
+| Performance, app size, signing, TestFlight and App Store release | [references/performance-release.md](references/performance-release.md) |
+
+## Before writing code
+
+- Check the deployment target (`IPHONEOS_DEPLOYMENT_TARGET`), the Swift language version and the Xcode version: many APIs in these guides need iOS 16 or 17, and Swift 6 changes concurrency checking.
+- Follow the project: SwiftUI or UIKit, its architecture, and dependencies already in `Package.resolved` or `Podfile.lock`.
+- Apple's requirements change every year (minimum SDK for uploads, privacy manifests, review guidelines); check the current ones instead of relying on these guides for dates or version numbers.

package/skills/mobile-ios/references/data-networking.md

@@ -0,0 +1,70 @@
+# iOS data and networking
+
+## HTTP with URLSession
+
+```swift
+struct APIClient {
+    let baseURL: URL
+    let session: URLSession = .shared
+    let decoder: JSONDecoder = {
+        let decoder = JSONDecoder()
+        decoder.keyDecodingStrategy = .convertFromSnakeCase
+        decoder.dateDecodingStrategy = .iso8601
+        return decoder
+    }()
+
+    func get<T: Decodable>(_ path: String, as type: T.Type = T.self) async throws -> T {
+        let (data, response) = try await session.data(from: baseURL.appending(path: path))
+        guard let http = response as? HTTPURLResponse, (200..<300).contains(http.statusCode) else {
+            throw APIError.badStatus((response as? HTTPURLResponse)?.statusCode ?? -1)
+        }
+        return try decoder.decode(T.self, from: data)
+    }
+}
+```
+
+The names are illustrative.
+
+- `URLSession` does not throw for 4xx/5xx responses: check the status code.
+- Async requests are cancelled when their `Task` is cancelled; SwiftUI's `.task` cancels when the view disappears.
+- Configure timeouts on a custom `URLSessionConfiguration` instead of relying on defaults for slow endpoints.
+- Decoding errors (`DecodingError`) should be logged with the key path; silently returning empty data hides API contract changes.
+- Large downloads and uploads that must continue when the app is suspended use a background `URLSessionConfiguration`.
+- Observe connectivity with `NWPathMonitor` to show offline state, but still handle request failures: reachability is only a hint.
+
+## Persistence
+
+| Data | Store |
+|---|---|
+| Secrets, tokens, credentials | Keychain |
+| Small preferences | `UserDefaults` (or `@AppStorage` in SwiftUI) |
+| Structured app data | SwiftData (iOS 17+) or Core Data |
+| Documents, media, caches | Files in Application Support, Documents or Caches, with the right Data Protection class |
+| HTTP response caching | `URLCache` with proper cache headers |
+
+### SwiftData
+
+```swift
+@Model
+final class Note {
+    var title: String
+    var createdAt: Date
+    init(title: String, createdAt: Date = .now) { self.title = title; self.createdAt = createdAt }
+}
+
+// App: .modelContainer(for: Note.self)
+// View: @Query(sort: \Note.createdAt, order: .reverse) private var notes: [Note]
+// Writes: @Environment(\.modelContext) private var context; context.insert(Note(title: "..."))
+```
+
+- Plan migrations (`VersionedSchema` and `SchemaMigrationPlan`) before shipping schema changes.
+- Model contexts are not shared across concurrency domains; use a `ModelActor` for background work.
+- Core Data projects keep Core Data unless there is a reason to migrate; both can coexist during a transition.
+
+## Offline-first
+
+Read from local storage, refresh from the network into it, and show the cached data while refreshing. Queue writes made offline and retry them with backoff; show pending state to the user.
+
+## Images
+
+`AsyncImage` has no persistent cache and decodes at full size. For feeds, use an image library the project already has, or downsample with ImageIO and cache the result.

package/skills/mobile-ios/references/performance-release.md

@@ -0,0 +1,37 @@
+# iOS performance and release
+
+## Measure before optimizing
+
+- **Instruments:** Time Profiler for CPU, Allocations and Leaks for memory, Hangs for main-thread blocks, the SwiftUI template for view updates. Profile a Release build on a device, not the simulator.
+- **In the field:** Xcode Organizer (launch time, hangs, memory, energy, disk writes) and MetricKit (`MXMetricManager`) for diagnostics from users' devices.
+
+## Common fixes
+
+- **Launch:** defer SDK initialization and data loading that the first screen does not need; avoid synchronous work in the `App` initializer or `application(_:didFinishLaunchingWithOptions:)`.
+- **Hangs:** move disk, network, JSON decoding and image decoding off the main actor.
+- **Scrolling:** stable identity in lists, no heavy work in `body` or `cellForItemAt`, downsampled images.
+- **Memory:** break retain cycles (`[weak self]`, weak delegates), bound in-memory caches and clear them on memory warnings.
+- **Size:** check the App Thinning size report from an archive export; keep images in asset catalogs, remove unused resources and dependencies.
+
+## Versioning and signing
+
+- `CFBundleShortVersionString` (Marketing Version) is the user-facing version; `CFBundleVersion` (build number) must increase for every upload of the same version.
+- Automatic signing is simplest for teams; CI usually uses manual signing or an App Store Connect API key with `xcodebuild -allowProvisioningUpdates`. Keep certificates and keys in the CI secret store, never in the repository.
+- Each extension (widgets, notification services) needs its own bundle identifier, prefixed by the app's, and a matching profile.
+
+## Build and upload
+
+```bash
+xcodebuild -scheme App -configuration Release -archivePath build/App.xcarchive archive
+xcodebuild -exportArchive -archivePath build/App.xcarchive -exportOptionsPlist ExportOptions.plist -exportPath build/export
+```
+
+- Upload with Xcode Organizer, Transporter, fastlane, or a tool based on the App Store Connect API; check which command-line upload method Apple currently supports before scripting it.
+- Keep dSYMs for crash symbolication (upload them to the crash reporter).
+
+## TestFlight and App Store
+
+- Internal testers (members of the App Store Connect team) get builds without review; external testers need a Beta App Review for the first build of a version.
+- Before submitting: screenshots and metadata, privacy details (the App Privacy section must match the privacy manifest and SDKs), export compliance (`ITSAppUsesNonExemptEncryption` in `Info.plist` avoids the question on each upload), sign-in credentials for the reviewer when the app requires an account, and account deletion in the app if it allows creating accounts.
+- Check the current App Store Review Guidelines and the minimum Xcode/SDK required for uploads; both change regularly.
+- Use phased release for updates to limit the impact of a bad build.

package/skills/mobile-ios/references/platform-features.md

@@ -0,0 +1,52 @@
+# iOS platform features
+
+## Permissions
+
+- Every protected API needs its usage description in `Info.plist` (`NSCameraUsageDescription`, `NSLocationWhenInUseUsageDescription`, `NSPhotoLibraryUsageDescription`...) with text that explains the benefit; a missing key crashes the app when the API is used.
+- Ask in context, when the user starts the feature, and handle denied and restricted states with a path to Settings (`UIApplication.openSettingsURLString`).
+- Photo picking with `PhotosPicker` (SwiftUI) or `PHPickerViewController` needs no library permission.
+
+## Push notifications
+
+- Enable the Push Notifications capability; request authorization with `UNUserNotificationCenter.current().requestAuthorization(options:)`; register with `UIApplication.shared.registerForRemoteNotifications()`.
+- Implement `UNUserNotificationCenterDelegate` to show notifications in the foreground and handle taps.
+- Rich media needs a Notification Service Extension; silent pushes need the Background Modes → Remote notifications capability and are throttled by the system.
+- With Firebase Cloud Messaging, follow `mobile-firebase`.
+
+## Universal links and URL schemes
+
+- Universal links: add the Associated Domains capability (`applinks:example.com`) and host `apple-app-site-association` on the domain over HTTPS.
+- Handle incoming URLs with `.onOpenURL` (SwiftUI) or the scene delegate, route through the navigation model, and validate parameters before acting.
+- Custom URL schemes can be claimed by other apps; do not use them for authentication callbacks or privileged actions.
+
+## Background work
+
+- `BGTaskScheduler` with `BGAppRefreshTask` for short refreshes and `BGProcessingTask` for longer maintenance; register identifiers in `Info.plist` (`BGTaskSchedulerPermittedIdentifiers`) and schedule again after each run. The system decides when tasks run.
+- Finishing a short task after the app goes to background: `beginBackgroundTask(withName:)` with the matching `endBackgroundTask`.
+
+## Widgets, Live Activities and App Intents
+
+- Widgets use WidgetKit in an extension target with a `TimelineProvider`; share data with the app through an App Group container, and reload timelines from the app when data changes.
+- Live Activities use ActivityKit and need `NSSupportsLiveActivities` in the app's `Info.plist`.
+- App Intents expose actions to Shortcuts, Siri, Spotlight, widgets and controls; define `AppIntent` types and `AppShortcutsProvider` for discoverable shortcuts.
+
+## In-app purchases with StoreKit 2
+
+```swift
+let products = try await Product.products(for: ["com.example.pro.monthly"])
+let result = try await products[0].purchase()
+if case .success(let verification) = result, case .verified(let transaction) = verification {
+    // unlock content, then:
+    await transaction.finish()
+}
+```
+
+- Start listening to `Transaction.updates` at launch to catch renewals, refunds and purchases made on other devices.
+- Only unlock content for `.verified` transactions; validate entitlements on your server for anything valuable.
+- Test with a StoreKit configuration file in Xcode, then in the sandbox and TestFlight.
+- Check the App Store Review Guidelines on digital goods before choosing a payment method.
+
+## Privacy
+
+- Keep the app's privacy manifest (`PrivacyInfo.xcprivacy`) accurate: data collected, tracking domains and required-reason APIs. Third-party SDKs must ship their own.
+- Request App Tracking Transparency (`ATTrackingManager`) before tracking across apps, with `NSUserTrackingUsageDescription`.

package/skills/mobile-ios/references/ui-navigation.md

@@ -0,0 +1,64 @@
+# iOS UI and navigation
+
+## SwiftUI state
+
+| Wrapper | Use for |
+|---|---|
+| `@State` | Value state owned by the view; also owns an `@Observable` model the view creates |
+| `@Binding` | Two-way access to state owned by a parent |
+| `@Observable` class (iOS 17+) | A model; views update only for properties they read |
+| `@Bindable` | Bindings to properties of an `@Observable` model the view does not own |
+| `ObservableObject` + `@StateObject` / `@ObservedObject` | Models before iOS 17: `@StateObject` where created, `@ObservedObject` where passed in |
+| `@Environment` | Values and models injected from an ancestor |
+| `@FocusState` | Keyboard focus in forms |
+
+A view must not recreate a model it does not own on every update; that resets state.
+
+## Navigation
+
+```swift
+enum Route: Hashable { case order(Order.ID), settings }
+
+struct RootView: View {
+    @State private var path: [Route] = []
+
+    var body: some View {
+        NavigationStack(path: $path) {
+            OrdersList(onSelect: { path.append(.order($0)) })
+                .navigationDestination(for: Route.self) { route in
+                    switch route {
+                    case .order(let id): OrderDetail(id: id)
+                    case .settings: SettingsView()
+                    }
+                }
+        }
+    }
+}
+```
+
+- `NavigationStack` with a path (iOS 16+) makes deep links and state restoration possible; `NavigationView` is deprecated.
+- Pass identifiers in routes, not whole models.
+- Sheets and full-screen covers are driven by optional state (`.sheet(item:)`), not booleans plus separate data.
+
+## Lists and forms
+
+- `List` and `LazyVStack` need stable identity: `Identifiable` models, not indices, for data that changes.
+- Heavy work does not belong in `body`: format, sort and filter in the model.
+- Forms: `Form`, `TextField` with `.textContentType` and `.keyboardType`, `@FocusState` to move between fields and dismiss the keyboard, validation in the model.
+
+## UIKit interop
+
+- Use a UIKit view in SwiftUI with `UIViewRepresentable` / `UIViewControllerRepresentable`, coordinating delegates through a `Coordinator`.
+- Embed SwiftUI in UIKit with `UIHostingController`.
+- In UIKit, prefer diffable data sources and compositional layouts for collections.
+
+## Accessibility and localization
+
+- Support Dynamic Type: system text styles (`.font(.body)`), no fixed heights around text.
+- Label icon-only controls (`.accessibilityLabel`), group related elements, and keep touch targets at least 44×44 points.
+- Test with VoiceOver and the largest accessibility text sizes.
+- Localize user-facing strings with String Catalogs (`.xcstrings`) or `String(localized:)`; SwiftUI `Text("key")` literals are localizable automatically.
+
+## Previews
+
+`#Preview { OrdersList(orders: .fixtures) }` with fixture data and injected fake services, so previews never hit the network.

package/skills/mobile-rn/SKILL.md

@@ -0,0 +1,26 @@
+---
+name: mobile-rn
+description: Builds React Native and Expo apps in TypeScript — navigation with React Navigation or Expo Router, lists, forms, styling, gestures and animations with Reanimated, safe areas, accessibility and localization; networking with TanStack Query, response validation, persistence with MMKV, AsyncStorage, SQLite and secure storage; permissions, push notifications, deep links, background tasks, native modules and config plugins; performance with Hermes and the React profiler; and release with EAS Build, EAS Submit and EAS Update or bare Gradle and Xcode builds. Use when writing or changing React Native code, adding a native capability, configuring Expo, preparing a store build or an over-the-air update, or when the user asks how to do something in React Native, even if they do not name the library.
+intents: [performance, release, accessibility]
+stacks: [react-native]
+---
+
+# Mobile React Native
+
+Guides for building React Native and Expo apps. Cross-platform topics live in their own skills and have React Native references there: architecture and state in `mobile-architecture`, tests in `mobile-test`, debugging (Metro, native modules, builds) in `mobile-debug`, code review in `mobile-code-review`, security in `mobile-security` and Firebase in `mobile-firebase`.
+
+## Pick the topic
+
+| Topic | Read |
+|---|---|
+| Navigation, lists, forms, styling, gestures, animations, accessibility, localization | [references/ui-navigation.md](references/ui-navigation.md) |
+| Networking, server state, validation, persistence, offline | [references/data-networking.md](references/data-networking.md) |
+| Permissions, push, deep links, background work, native modules, config plugins | [references/platform-features.md](references/platform-features.md) |
+| Performance, bundle, EAS Build, store submission and over-the-air updates | [references/performance-release.md](references/performance-release.md) |
+
+## Before writing code
+
+- Detect the setup: Expo (managed with Continuous Native Generation, or with committed `android/` and `ios/`) or bare React Native; the React Native and Expo SDK versions; whether the New Architecture is enabled.
+- Install libraries with `npx expo install` in Expo projects, so versions match the SDK.
+- Libraries with native code need a new native build (a development build in Expo); they do not work in Expo Go unless the Expo SDK includes them.
+- Native requirements of each platform still apply; see `mobile-ios` and `mobile-android` for store and platform specifics.

package/skills/mobile-rn/references/data-networking.md

@@ -0,0 +1,59 @@
+# React Native data and networking
+
+## Server state with TanStack Query
+
+```tsx
+const queryClient = new QueryClient({ defaultOptions: { queries: { staleTime: 30_000, retry: 2 } } });
+
+export function App() {
+  return (
+    <QueryClientProvider client={queryClient}>
+      <RootNavigator />
+    </QueryClientProvider>
+  );
+}
+
+export const useOrder = (orderId: string) =>
+  useQuery({ queryKey: ['orders', orderId], queryFn: () => api.orders.get(orderId) });
+
+export function useCancelOrder() {
+  const queryClient = useQueryClient();
+  return useMutation({
+    mutationFn: api.orders.cancel,
+    onSuccess: () => queryClient.invalidateQueries({ queryKey: ['orders'] }),
+  });
+}
+```
+
+The names are illustrative. Use RTK Query instead if the project is built on Redux Toolkit.
+
+- React Native has no window focus or online events: wire `focusManager` to `AppState` and `onlineManager` to NetInfo so queries refetch when the app returns to the foreground or reconnects.
+- Keys include every variable the request depends on.
+
+## HTTP client
+
+- One typed client on `fetch` (or axios, if the project uses it) with a base URL, auth header injection, token refresh and timeouts. `fetch` has no timeout: use an `AbortController` with a timer.
+- `fetch` does not reject on 4xx/5xx; check `response.ok`.
+- Validate or map responses at the boundary (for example with zod) instead of `as` casts in screens.
+- Base URLs and public config come from app config or EAS environment variables; secrets stay on the backend.
+
+## Persistence
+
+| Data | Store |
+|---|---|
+| Tokens, credentials | `expo-secure-store` or `react-native-keychain` (Keychain/Keystore) |
+| Preferences, small key-value data | MMKV (`react-native-mmkv`) or AsyncStorage |
+| Relational or large data | SQLite (`expo-sqlite` or the library the project uses), optionally with an ORM such as Drizzle |
+| Files and media | `expo-file-system` or the file library the project uses |
+| Query cache across launches | TanStack Query persisters, for data that is safe to show stale |
+
+AsyncStorage is unencrypted and asynchronous; do not store secrets there, and avoid large values.
+
+## Offline
+
+- Detect connectivity with `@react-native-community/netinfo` to show offline state, but still handle request failures.
+- For offline-first flows, read from local storage, sync from the network into it, and queue writes with retry and a visible pending state.
+
+## Real-time
+
+WebSockets or server-sent updates must pause or reconnect with `AppState` changes; the OS suspends connections in the background.

package/skills/mobile-rn/references/performance-release.md

@@ -0,0 +1,46 @@
+# React Native performance and release
+
+## Measure before optimizing
+
+- The React profiler in React Native DevTools (or the DevTools version for the project's React Native release) to find components that re-render.
+- The performance monitor for JavaScript and UI frame rates; native profilers (Instruments, Android Studio) for native modules and startup.
+- Test performance in release builds on real devices: development builds are much slower.
+
+## Common fixes
+
+- **Re-renders:** narrow context values, memoize expensive children with stable props, select store slices, keep fast-changing state local.
+- **Lists:** virtualized lists with stable keys and memoized rows (see `ui-navigation.md`).
+- **JavaScript thread:** move animations to Reanimated worklets; defer heavy work until after interactions; avoid large synchronous JSON parsing during navigation.
+- **Startup:** keep Hermes enabled, avoid importing heavy modules at the entry point, show the first screen before loading optional data.
+- **Bundle and size:** remove unused dependencies, check which libraries pull large native SDKs, and remove `console.log` in release builds.
+
+## Versioning
+
+- User-facing version: `version` in the Expo app config, or the native version fields in bare projects (`versionName` on Android, `MARKETING_VERSION` on iOS).
+- Build numbers: iOS `buildNumber` and Android `versionCode` must increase for every store upload. EAS can manage them with `appVersionSource: "remote"` and `autoIncrement` in `eas.json`.
+
+## Building
+
+**Expo / EAS:**
+
+```bash
+eas build --platform ios --profile production
+eas build --platform android --profile production
+eas submit --platform ios --latest
+```
+
+- Build profiles live in `eas.json` (development, preview, production); credentials are managed by EAS or provided by the team.
+- Environment variables per environment are configured in EAS; values available to the app code are public.
+
+**Bare React Native:** `./gradlew bundleRelease` in `android/` for an AAB, and an Xcode archive for iOS; store requirements and signing follow `mobile-android` and `mobile-ios`.
+
+## Over-the-air updates
+
+- EAS Update (or the update service the project uses) ships JavaScript and asset changes only. Anything that changes native code, native config or config plugins needs a new store build.
+- `runtimeVersion` must change whenever the native layer changes, so an update never reaches a binary it is incompatible with; prefer a policy such as `fingerprint` or `appVersion` over manual values when possible.
+- Publish to a preview channel first, then roll out to production; keep a way to roll back.
+- Store rules restrict what updates may change (for example, no new features that bypass review on iOS); check the current guidelines.
+
+## Crash reporting
+
+Upload source maps for release bundles (and dSYMs and R8 mappings for native code) to the crash reporter, so JavaScript and native stack traces are readable.

package/skills/mobile-rn/references/platform-features.md

@@ -0,0 +1,40 @@
+# React Native platform features
+
+## Permissions
+
+- Expo modules expose permission hooks and methods (`useCameraPermissions`, `Location.requestForegroundPermissionsAsync`...); bare projects often use `react-native-permissions`.
+- Declare iOS usage descriptions and Android permissions in native config: in Expo, through the module's config plugin options or `ios.infoPlist` and `android.permissions` in the app config; in bare projects, in `Info.plist` and `AndroidManifest.xml`.
+- Ask in context, handle "denied" and "blocked", and link to settings with `Linking.openSettings()`.
+
+## Push notifications
+
+- **Expo:** `expo-notifications` for permissions, tokens, foreground handling (`setNotificationHandler`) and taps; the Expo push service or your own backend with FCM/APNs credentials. Push does not work in Expo Go on every platform and SDK version; use a development build.
+- **Firebase Cloud Messaging:** follow `mobile-firebase` (React Native Firebase).
+- Android 13+ needs the notification permission; iOS needs the Push Notifications capability and an APNs key.
+- Register background handlers at the app entry, outside components.
+
+## Deep links
+
+- Custom scheme: `scheme` in the Expo app config, or intent filters and URL types in bare projects.
+- Universal links and app links: `ios.associatedDomains` and `android.intentFilters` with `autoVerify` in Expo, plus the `apple-app-site-association` and `assetlinks.json` files on your domain.
+- Route links through the navigator's linking configuration and validate parameters before acting.
+
+## Background work
+
+- Periodic background work is limited and scheduled by the OS. In Expo, use the background task module of the SDK in use (`expo-background-task` replaced `expo-background-fetch`; check the SDK docs) with `expo-task-manager`.
+- Uploads and long jobs that must finish belong on the server or in native background transfer APIs, not in JavaScript timers.
+
+## Native modules and config
+
+- **Expo Modules API:** write native modules in Swift and Kotlin with a typed JavaScript interface; works in Expo and bare projects.
+- **Turbo Modules / Fabric components:** the New Architecture native module system in bare projects; define the spec in TypeScript and generate code with Codegen.
+- **Config plugins:** change native projects (Info.plist, manifest, Gradle, Podfile) reproducibly in Expo projects with Continuous Native Generation. Do not hand-edit `android/` and `ios/` in such projects; changes are lost on `npx expo prebuild --clean`.
+- Wrap each native module once in a typed TypeScript API.
+
+## Device capabilities
+
+Camera (`expo-camera` or `react-native-vision-camera`), location (`expo-location`), media library, biometrics (`expo-local-authentication`), haptics and sensors: prefer the libraries the project already uses, check that they support the New Architecture when it is enabled, and add their permissions.
+
+## In-app purchases
+
+Use a maintained library (for example RevenueCat's SDK or `react-native-iap`) or the store APIs through native modules; verify purchases and entitlements on a server, and test with store sandbox accounts. Store rules for digital goods are in `mobile-ios` and `mobile-android`.