android-app-factory

Plan, build, test, and release native Android apps through Google Play with evidence gates.

123|10|Updated May 24, 2026
One-click install
npx skills add https://github.com/JasonColapietro/suede-creator-skills --skill android-app-factory-jasoncolapietro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: android-app-factory
Source: https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/android-app-factory
Command: npx skills add https://github.com/JasonColapietro/suede-creator-skills --skill android-app-factory-jasoncolapietro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Shipping a production Android app requires coordinating Kotlin/Compose architecture, Play policy compliance, privacy disclosures, billing, testing, and staged rollout — and a single missed requirement can block or sink a release. This Skill turns that into a structured pipeline with verifiable evidence at every stage. ## Core Features & Use Cases - End-to-end release pipeline: Ten phases from product validation through policy verification, architecture, scaffolding, core-loop build, quality proof, monetization, trust surfaces, store assets, and staged rollout. - Dated Play policy baseline: Live-checkable target-API timeline, 16 KB page-size rules, Data Safety, account deletion, and Play Billing requirements with official source URLs. - Release evidence gate: A copyable gate template that produces a ship / ship-with-caveats / hold verdict backed by build, test, accessibility, performance, privacy, and signing evidence. - Use Case: Ask the agent to take a new app idea to Play: it scaffolds a Kotlin + Jetpack Compose project, verifies current target-SDK policy, builds the core loop with tests, reconciles Data Safety and Billing behavior, generates truthful store assets, and halts for your confirmation before any Play Console upload or rollout. ## Quick Start Use the android-app-factory skill to plan and build my Android app idea, verify current Google Play policy requirements, and prepare a signed release bundle with a completed release-gate checklist before any Play Console submission.

Frequently Asked Questions about android-app-factory

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I release an Android app to Google Play with an AI agent?

Use this skill to run a ten-phase pipeline: validate the product, verify live Play policy, design architecture, scaffold Kotlin and Jetpack Compose, build the core loop, prove quality with tests, then complete trust surfaces, store assets, and a staged rollout. Every Play Console mutation requires your explicit confirmation.

What target API level should a new Android app use for Google Play?

On the skill's dated baseline, general phone and tablet apps should build with API 36, since Play requires Android 16 (API 36) for new apps and updates starting 2026-08-31. The skill instructs re-checking the official target-SDK page live before every release rather than trusting memory.

Does this skill support iOS app development?

No. iOS work is explicitly out of scope and handled by a separate private companion skill. This skill covers only native Android with Kotlin and Jetpack Compose through Google Play.

Can the agent upload my app to Play Console automatically?

No. The skill's boundaries prohibit uploads, track promotions, product creation, pricing changes, and production rollouts without explicit user confirmation. When a confirmation gate fires, the agent names the exact package ID, track, and rollout percentage, then waits for your decision.

What evidence is required before an Android release is approved?

The release gate requires a signed bundleRelease build, passing tests and lint, a device/API matrix including 16 KB page-size verification for Android 15+ targets, accessibility and performance evidence, reconciled Data Safety and account deletion flows, Billing lifecycle proof when relevant, and truthful store listing assets.

When should I use a code review skill instead of this app factory?

Use a findings-only code review skill when you want an existing app audited without building or releasing anything. This factory skill is for creating, shipping, monetizing, or modernizing an app through the full Play release pipeline.