mobile-app-scaffoldlisted

# mobile-app-scaffold ## Purpose Output a complete Expo project tree with AiGNITE conventions baked in. Supabase client wired. MCP client wired. Smoke test wired to real business endpoints. CLAUDE.md with engineering standards seeded at the project root. ## When to trigger Trigger on these user phrases. Match loosely. - "build a mobile app" - "scaffold an Expo project" - "new React Native app" - "start a mobile project" - "Expo scaffold" - "mobile app boilerplate" - "kick off a mobile app" - "set up a React Native repo" ## Inputs to collect Before scaffolding, collect: 1. App name (human readable, e.g. "FloodPulse Mobile") 2. Bundle ID (reverse DNS, e.g. "com.aignite.floodpulse") 3. Target output directory (default: current working directory) 4. Optional MCP server URL the app will talk to If the user has supplied any of these in the trigger message, parse them out and skip the matching prompt. ## What the skill produces A complete Expo project at the target directory containing: - `app.json` and `eas.json` with bundle ID and owner placeholders filled - Folder layout: `app/` (Expo Router), `components/`, `lib/`, `hooks/`, `services/`, `assets/` - `lib/supabase.ts` with client init and RLS-aware query helpers - `services/mcp-client.ts` pointed at the supplied MCP server URL - `.env.local.example` listing every variable the project needs - `CLAUDE.md` at project root with the AiGNITE engineering standards - `Makefile` with three targets: `make check`, `make up`, `ma