Scaffold a new iOS app with SDLC and submission-safe defaults — diffable project files, app + test targets, deployment-target policy, a git-stamped build number, and the Info.plist keys the pre-flight checker wants so the project passes TestFlight from day one. Use when starting a new iOS project.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Create a new iOS app project that is submission-safe from the first commit — so it doesn't hit the
TestFlight/App Store blockers ios-testflight-release and the pre-flight checker exist to catch.
Belongs to the sdlc-team-ios plugin; pairs with swiftui-architect (structure) and
swift-language-expert (language).
app-name — the app / bundle name (defaults to asking).Prefer a diffable, mergeable project definition over a hand-managed .xcodeproj:
.xcodeproj from a committed manifest (Tuist's Project.swift, or an XcodeGen YAML manifest)
that is committed, so project changes review cleanly and don't cause merge conflicts.Ask which the team prefers; default to XcodeGen/Tuist for an app that needs a real Xcode project.
swiftui-architect..gitignore covering *.xcodeproj (if generated), DerivedData/, .build/, *.xcuserstate,
.DS_Store, and any secrets file.Pre-set the keys the pre-flight checker looks for, so uploads don't stall or get rejected later:
ITSAppUsesNonExemptEncryption = false (if the app uses only exempt encryption such as standard
HTTPS) — skips the export-compliance questionnaire on every upload.NS…UsageDescription placeholder-with-a-real-sentence for each capability the app will use
(add them as you add frameworks; the pre-flight check maps CoreMotion→NSMotionUsageDescription,
etc.). Leave a comment reminding that these must be real human sentences.Package.swift).MARKETING_VERSION fixed pre-1.0 (e.g. 1.0.0) and stamp CFBundleVersion from
git rev-list --count HEAD (optionally plus the short SHA and date) in a build-phase script,
so every build is unique, monotonic, and traceable to a commit.ENABLE_USER_SCRIPT_SANDBOXING = NO (leave it YES
elsewhere) — a script that reads git/the environment fails to archive under the sandbox otherwise..xcconfig/build settings + a secrets mechanism.ios-ci to generate the GitHub Actions workflow (which gates on the pre-flight checks).PrivacyInfo.xcprivacy stub if the app will use required-reason APIs or bundle third-party SDKs.python -m ios_preflight.cli <project>) — it should be clean (or only INFO) on a fresh scaffold.Summarise what was generated, the generation approach chosen, the build-number policy, and confirm the pre-flight checker is clean. Note anything the user must fill in (real purpose strings, signing team).
ios-testflight-release pre-flight on day one — don't leave the
export-compliance key or build-number policy "for later".swiftui-architect; for
idiomatic Swift, to swift-language-expert.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Generate a GitHub Actions workflow for Android — JDK + Gradle caching, build, unit + instrumented tests, Android Lint, run the Android pre-flight checks, and (optionally) sign + upload a signed app bundle to a Play track. Use when setting up CI for an Android app.
The English summary is being prepared. Showing the original description.
Validated Google Play release — runs the pre-flight checks and clears the Play policy gates, builds a signed app bundle with a git-stamped versionCode, uploads to a track, and walks staged rollout (with halt/roll-forward). Use when releasing an Android app to Play.
The English summary is being prepared. Showing the original description.
Scaffold a new Android app with SDLC and Play-safe defaults — Kotlin/Compose Gradle project with version catalog, convention plugins, module layout, a targetSdk that meets the Play mandate, R8 on release, and git-ignored signing so it passes the pre-flight checker from day one. Use when starting a new Android project.
The English summary is being prepared. Showing the original description.
Set up Android app signing safely — generate an upload keystore, enroll in Play App Signing, and wire a Gradle release signingConfig that reads secrets from a git-ignored keystore.properties / CI (never committed). Use when configuring signing for a Play release.
The English summary is being prepared. Showing the original description.
Pick an existing workflow for a task or author a new one — recommends workflow + team formation, or generates a fresh workflow YAML with command prompts and team validation.
The English summary is being prepared. Showing the original description.
Guide the team through writing a change-impact record for IEC 62304 / FDA / ISO 26262 ASIL C+ projects. Surfaces the affected REQ/DES/TEST/CODE artefacts and captures human-attested verification approach.
The English summary is being prepared. Showing the original description.