rn-launch-harness

RN Launch Harness

A Claude Code plugin that automates the entire React Native mobile app lifecycle — from market research to App Store & Google Play submission.

One command takes you from idea to store review. Market research, planning, design system, development, AdMob integration, EAS build, store screenshots, and submission — all automated.

No idea yet? Run without arguments — the harness researches App Store/Google Play top charts and recommends solo-developer-friendly apps that need no backend.

Inspired by Anthropic's Harness Design for Long-Running Apps.

한국어

flowchart LR
    A["💡 Idea<br/>/rn-harness 'app'"] --> B[🔍 Research]
    B --> C[📋 Plan<br/>PRD + FSD]
    C --> D[🎨 Design System<br/>NativeWind]
    D --> E[🤝 Contract<br/>Gen↔Eval]
    E --> F[🛠 Build<br/>3 sub-phases]
    F --> G{QA}
    G -->|FAIL| F
    G -->|PASS| H[💰 AdMob]
    H --> I[📦 EAS Build<br/>iOS + Android]
    I --> J[📸 Screenshots<br/>Maestro]
    J --> K[🚀 Submit<br/>ASC + Play API]
    K --> L([✓ Under Review])

    style A fill:#1e293b,color:#fff,stroke:#3b82f6
    style L fill:#065f46,color:#fff,stroke:#10b981
    style G fill:#f59e0b,color:#fff,stroke:#f59e0b

Install

claude plugins marketplace add tjdrhs90/rn-launch-harness
claude plugins install rn-launch-harness@rn-launch-harness

Quick Start

# With an idea
/rn-harness "daily coffee subscription tracker"

# No idea — discover from store top charts
/rn-harness

# With a reference site/image
/rn-harness "calendar app" --ref https://cal.com

# Check progress
/rn-harness --status

# Resume after rate limit
/rn-harness --resume

Pipeline

Default Mode (~$30-60, Claude Max friendly)

/rn-harness "app idea"
    |
    v
 Phase 1: Market Research → competitor analysis, monetization
 Phase 2: Planning → PRD, user stories, FSD module map
 Phase 3: Design System → NativeWind theme, components
 Phase 4: Contract → 1-pass criteria (no multi-round negotiation)
 Phase 5: Build (3 sub-phases)
    |  5a: Feature/Entity scaffolding → Quick QA
    |  5b: API integration → Quick QA
    |  5c: Screen/UI development → Quick QA
 Phase 6: QA — Functional only (typecheck, lint, FSD, contract)
    |  FAIL → fix → re-evaluate (max 3 rounds)
 Phase 7: AdMob → smart placement + code injection
 Phase 8: EAS Build → iOS + Android
 Phase 9: Screenshots → Maestro + metadata
 Phase 10: Store Submission → ASC API + Google Play API

--strict Mode (~$100-160, thorough)

/rn-harness "app idea" --strict
    |
 + Phase 2.5: Spec Planning → file-level task checklists
 + Phase 4: Contract → multi-round Generator↔Evaluator negotiation
 + Phase 6: 3-Phase Progressive QA
    |  6.1 Functional — Does it WORK?
    |  6.2 Quality — Is it GOOD? (design 4-axis scoring)
    |  6.3 Edge Cases — Can it SURVIVE? (6 Agent Team + simulator)
 + Phase 11: Retrospective → Anthropic principles evaluation

Requirements

• Claude Code (latest)
• Node.js 20+
• EAS CLI (npm install -g eas-cli)
• Maestro (screenshots, optional) — curl -Ls "https://get.maestro.mobile.dev" | bash
• gh CLI (GitHub integration)

Setup — Keys & Environment Variables

Project Directory Structure

my-app/
├── credentials/              # Key files (NOT committed to git)
│   ├── asc-api-key.p8        # App Store Connect API Key
│   └── google-play-sa.json   # Google Play Service Account
├── .env                      # Environment variables (NOT committed)
├── .env.example              # Template (committed)
└── .gitignore                # Excludes credentials/, .env

Environment Variables (.env)

# ── App Store Connect API (iOS submission) ──
ASC_KEY_ID=XXXXXXXXXX
ASC_ISSUER_ID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
ASC_PRIVATE_KEY_PATH=./credentials/asc-api-key.p8

# ── Google Play Developer API (Android submission) ──
GOOGLE_PLAY_SA_JSON=./credentials/google-play-sa.json

# ── AdMob ──
ADMOB_IOS_APP_ID=ca-app-pub-XXXX~YYYY
ADMOB_ANDROID_APP_ID=ca-app-pub-XXXX~ZZZZ

# ── AI Image Generation (optional, for store assets) ──
GEMINI_API_KEY=

# ── EAS (optional, for CI) ──
EXPO_TOKEN=

Key Provisioning Guide

App Store Connect API Key (.p8)

1. Go to App Store Connect
2. Users and Access → Integrations → App Store Connect API
3. Team Keys tab → Generate API Key
4. Set name, role: Admin or App Manager
5. Download .p8 file → save to credentials/asc-api-key.p8
6. Record Key ID and Issuer ID in .env

The .p8 file can only be downloaded once. If lost, you must generate a new key.

Google Play Service Account (.json)