Orqestria Download
← Zurück zu Team für plattformübergreifende mobile Apps

Skill · Version 1.0.0

Mobiles Projekt erfassen

Erfasst tatsächliche mobile Technologien, Auslieferungsziele und Zustandsverantwortung vor Implementierungsänderungen.

mobile-project-discovery

Teammitglieder mit diesem Skill

Entdecke, wie der Skill hilft

Wann ist der Skill hilfreich?

Nutze dies beim Einstieg in vorhandene React-Native-, Flutter- oder native Projekte.

Wobei hilft er dir?

  • Identifiziert Frameworkversionen, Buildablauf und Plattformziele.
  • Verfolgt Navigation, Zustand, API und Speicherverantwortung.
  • Koordiniert gemeinsame Grenzen mit nativer, Backend- und Designarbeit.

Das könntest du fragen

Untersuche unser Repository und ordne Benachrichtigungsrouting, Anmeldung und gespeicherte Entwürfe zu. Verfolge eine Benachrichtigung von beendeter App über Anmeldung bis zum Ziel. Benenne vor Umsetzung Verantwortliche für Routing, Zugangsdaten und wiederhergestellte Entwürfe.

Ausführliche Dokumentation

Hier findest du die ursprüngliche Anleitung, Beispiele und Prüfschritte des Skills in ihrer Originalsprache.

Details…Weniger anzeigen

Mobile Project & Platform Discovery

Adapt to the project's actual mobile stack, target OS versions and architectural boundaries before writing code. Never mix frameworks or introduce a competing state/navigation library; for a brand-new app, agree the stack with the architect based on product goals, hardware needs and release workflow.

1. Fingerprint the stack, workflow and deployment targets

Stack Manifests & Config to Inspect Key Version & Architecture Signals
React Native / Expo package.json, app.json / app.config.ts, eas.json, metro.config.js, babel.config.js Expo SDK version, CNG / Prebuild (generated ios/ & android/) vs Bare RN, New Architecture (newArchEnabled, Fabric/TurboModules), Hermes engine, runtimeVersion policy.
Flutter pubspec.yaml, analysis_options.yaml, build.yaml, l10n.yaml, lib/main_*.dart Dart SDK constraint, Impeller renderer config, flavors, codegen (build_runner, freezed, json_serializable, riverpod_generator, pigeon).
Native iOS *.xcodeproj, *.xcworkspace, Package.swift, Podfile, Info.plist, *.entitlements IPHONEOS_DEPLOYMENT_TARGET, Swift language mode (Swift 5 vs Swift 6 strict concurrency), SwiftUI vs UIKit lifecycle, App Groups / Keychain sharing.
Native Android settings.gradle(.kts), app/build.gradle(.kts), gradle/libs.versions.toml, AndroidManifest.xml minSdk, targetSdk, compileSdk, Kotlin & Compose compiler versions, build flavors/variants, ProGuard/R8 rules (proguard-rules.pro).

2. Map existing architecture and state ownership

  • Trace how a feature flows end-to-end: Screen / Widget -> ViewModel / Notifier / Hook -> Repository / Service -> HTTP Client / Local DB / Native Bridge.
  • Identify the single owner for each data category:
    1. Server cache: TanStack Query / RTK Query / Riverpod AsyncNotifier / Repository cache.
    2. Encrypted credentials: iOS Keychain / Android Keystore (expo-secure-store, react-native-keychain, flutter_secure_storage).
    3. Structured local persistence: SQLite (expo-sqlite, WatermelonDB, Drift, Room, SwiftData/CoreData) vs fast KV (MMKV, SharedPreferences, UserDefaults).
    4. Ephemeral UI & route state: local component state and serializable route parameters.
  • Locate existing design tokens, safe-area wrappers, keyboard-avoiding containers, localization catalogs and test harnesses.

3. Coordinate cross-cutting boundaries

  • Never hand-edit generated native folders in Expo CNG or generated .g.dart / .freezed.dart files in Flutter.
  • When a task requires native toolchain changes, new OS entitlements or API contract changes, align with the architect, backend developers or security reviewer before coding.

Before you finish

  • Stack, SDK version, New Architecture/Impeller status and minSdk / iOS deployment target verified.
  • Managed/CNG vs bare/native workflow and codegen pipeline identified.
  • Existing router, state store, API client, secure storage and design primitives mapped.
  • Exact commands for typecheck, static analysis, codegen and tests confirmed.

Enthaltene Dateien 2

  • LICENSE.txt
  • SKILL.md