com um clique
rn-launch-harness
rn-launch-harness contém 17 skills coletadas de tjdrhs90, com cobertura ocupacional por repositório e páginas de detalhe dentro do site.
Skills neste repositório
Phase 7 — Smart AdMob ad placement analysis and integration. Guides user through manual ad unit creation.
Phase 5 — Build the React Native + Expo app in 3 sub-phases (scaffold, API, UI). Self-evaluates before handoff.
Phase 7.5 — Human acceptance gate before store build. Runs an automated Maestro E2E smoke test on a real simulator/emulator, then PAUSES for the user to run the app themselves and explicitly approve before any EAS/local build or store submission.
React Native app launch harness — from market research to App Store & Google Play submission. One command takes you from idea to store review.
Phase 8 (EAS-free alternative) — Build & deploy without EAS. For users whose EAS free-plan project slots are full. Local Gradle (Android AAB) + Xcode/fastlane (iOS IPA), self-hosted OTA, then submit via Google Play API + fastlane/Transporter.
Phase 8 — EAS Build for iOS and Android, plus EAS Update (OTA) configuration.
Phase 10 — Submit to App Store Connect (iOS) and Google Play (Android). iOS fully automated, Android pauses for manual steps.
Phase 9 — Automated store screenshots via Maestro on real simulator/emulator. Hides ads during capture.
Phase 2 — PRD generation with user stories, Expo Router structure, FSD module map, and API design.
Phase 4 — Generator and Evaluator negotiate completion criteria before any code is written.
Phase 3 — Design system with NativeWind theme, colors, typography, and component specs.
Phase 6 — QA verification. Default mode runs functional check only; --strict runs 3-phase progressive QA with Agent Team.
Phase 1 — Market research and idea discovery via store top charts and competitor analysis.
Resume a paused pipeline from saved state (after rate limit or manual action).
Pipeline retrospective — evaluate the completed pipeline against Anthropic's 9 harness principles.
Phase 2.5 — Break PRD into file-level task checklists under docs/specs/ for progress tracking.
Display current pipeline progress, build rounds, scores, and state.