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.
See how to installReview the instructions the agent will receive before you install.
Create a new Android app project that is Play-safe and build-fast from the first commit — so it
doesn't hit the submission/build issues android-play-release and the pre-flight checker exist to
catch. Belongs to the sdlc-team-android plugin; pairs with jetpack-compose-architect (UI),
android-app-architect (structure), gradle-build-specialist (build), and language-kotlin-expert.
app-name — the app / applicationId (defaults to asking).app + feature:* + core:* + data:*; features depend
on core/data, never other features) — see android-app-architect..gitignore covering /build, .gradle, local.properties, *.jks/*.keystore,
keystore.properties, .idea (except shared), *.iml.build.gradle.kts), a version catalog (gradle/libs.versions.toml) as the single
source of truth, and convention plugins in a build-logic included build for shared android {}
config (à la Now in Android). See gradle-build-specialist.namespace + applicationId set; compileSdk = latest stable; targetSdk = the
current Play minimum (the pre-flight checker's --play-min-target) so the app isn't hidden on new
devices; a sensible minSdk.versionName fixed pre-1.0; versionCode stamped from
git rev-list --count HEAD (unique & monotonic — every upload needs this) in a Gradle snippet.gradle.properties.isMinifyEnabled = true + isShrinkResources = true (R8) with a
proguard-rules.pro; a release signingConfig reading secrets from a git-ignored
keystore.properties / CI (never the debug keystore, never committed secrets) — see
android-signing-setup.BuildConfig flag
that is off in release.android:exported=false); avoid usesCleartextTraffic (use a network-security-config allowlist if
genuinely needed).android-ci to generate the GitHub Actions workflow (gates on the pre-flight checker +
./gradlew lint)../gradlew assembleDebug once; run the unit-test source set; and run the pre-flight checker
(python -m android_preflight.cli <project>) — it should be clean (or only INFO) on a fresh scaffold.Summarise what was generated, the module layout, the versionCode policy, and confirm the pre-flight checker is clean. Note anything the user must fill in (real keystore, Data Safety, privacy policy).
android-play-release pre-flight on day one — don't leave targetSdk,
R8, or signing "for later".jetpack-compose-architect; for app architecture to
android-app-architect; for idiomatic Kotlin to language-kotlin-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.
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.
Generate boilerplate `# implements:` annotation for a function based on the artefact ID, inserting it as the first line of the function body.
The English summary is being prepared. Showing the original description.