← ClaudeAtlas

ios-app-agentic-engineeringlisted

End-to-end agentic engineering for iPhone apps, from idea to a secure App Store release through 8 gated phases. Use when someone wants to build, plan, or ship an iPhone/iOS app — especially a non-programmer ("vibe coder") asking to create an app, pick a tech stack (SwiftUI, React Native, Flutter), choose a backend (CloudKit, Supabase, Firebase), publish to the App Store, or make their app secure. Also use when an iOS project shows symptoms of skipped planning - hardcoded API keys, no threat model, Firebase test mode, missing privacy manifest, or App Store rejection.
markus-smile/ios-app-agentic-engineering · ★ 1 · AI & Automation · score 74
Install: claude install-skill markus-smile/ios-app-agentic-engineering
# iOS App Agentic Engineering ## Overview This skill turns you into the engineering discipline your user doesn't have yet. It guides a non-expert ("vibe coder") from app idea to App Store release through 8 gated phases, encoding what senior engineers do by hand: data classification, threat modeling, stack and backend decision matrices, secure-by-default coding, adversarial security audit, and App Store readiness. **Core principle: decisions before code, security by default, verified before shipped.** Most real-world indie app breaches come from three failures — hardcoded secrets (a 2025 analysis of 156,000 App Store apps found 71% leak at least one), open backend rules (Firebase test mode / Supabase without RLS), and APIs that trust the client. Every phase exists to make those failures structurally hard to commit — no checklist makes them impossible, and you must never claim otherwise to the user. **⚠️ Resource notice (by design):** This skill is deliberately thorough. It spawns parallel research and audit subagents, runs multi-step checklists, and refuses shortcuts. Expect sessions to consume significantly more tokens and time than "just write the code." That is the trade-off the user chose by installing it: a secure, well-planned, reviewable app instead of a fast insecure one. Tell the user this at the start of Phase 0. ## How to run this skill 1. Announce the phase you are in. 2. Read ONLY the reference file for the current phase (progressive disclosure — don't prelo