brownfield-onboardinglisted

Use when pointing the team at an EXISTING, already-built app instead of a blank project — detects the stack, reverse-engineers the as-built architecture, and classifies remediation work as safe-to-auto-fix vs risky-needs-approval. Triggered by /app-onboard, /app-audit, and by /app-run when it detects a non-empty app directory.
vmobifystudio/app-dev-team · ★ 4 · AI & Automation · score 75

Install: claude install-skill vmobifystudio/app-dev-team

# Brownfield onboarding Greenfield commands generate vision → PRD → architecture → code. For an app that already exists, you go the other way: **read the code, snapshot what's there, grade it against the House KB, and plan the gap.** This skill is the procedure for the "read and understand" half. ## When to use - `/app-onboard` (adopt an existing codebase) and `/app-audit` (grade it) both start here. - `/app-run` invokes this when the target directory already contains an app (see Detection). ## Step 1 — Detect the app Scan the target directory (not deeper than ~3 levels) to establish ground truth before any agent reasons about it: - **iOS:** `*.xcodeproj` / `*.xcworkspace` / `Package.swift`; read `project.yml` (XcodeGen), `*.xcconfig`, `Info.plist`, `Package.resolved`. Note Swift version, min iOS target, SwiftUI vs UIKit. - **Android:** `settings.gradle*`, `app/build.gradle(.kts)`, `gradle/libs.versions.toml`. Note Kotlin/AGP, `compileSdk`/`minSdk`/`targetSdk`, Compose vs XML, the module list. - **Both / signals:** existing `CLAUDE.md`, `README`, `docs/`, CI under `.github/workflows`, `google-services.json`/`GoogleService-Info.plist` presence (Firebase), ads/billing SDKs in deps. - **Neither iOS nor Android:** that is a normal answer, not a dead end. Read the package manifests — `package.json`, `go.mod`, `Cargo.toml`, `pyproject.toml`, `pom.xml` — plus `Dockerfile`, `Procfile`, and whether there is a UI surface or a binary entry point. `role-activation`'s de