Update to Autonom

{
  "description": "Create, inspect, or modernize native Android modules with Kotlin, Gradle, Compose, SDK configuration, version catalogs, and compatibility checks based on the active repository and official guidance.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 225
    }
  ],
  "name": "android-project-setup",
  "skill_md_contents": "---\nname: android-project-setup\ndescription: Create, inspect, or modernize native Android modules with Kotlin, Gradle, Compose, SDK configuration, version catalogs, and compatibility checks based on the active repository and official guidance.\n---\n\n# Android Project Setup\n\nChange the smallest coherent surface that the repository already uses.\n\n## Workflow\n\n1. Read settings, module builds, version catalogs, wrapper, `gradle.properties`,\n   manifests, build logic, and CI.\n2. Run `scripts/toolchain_snapshot.py` instead of trusting a hardcoded matrix.\n3. Classify: new module, focused dependency change, or toolchain migration.\n4. Keep existing dependency-management and architecture conventions when they\n   are coherent.\n5. Re-check official AGP / Kotlin / Gradle / library docs for version-sensitive\n   work.\n6. Apply a minimal patch and run the narrowest Gradle tasks that prove it.\n\n## Defaults\n\n- Checked-in Gradle wrapper only.\n- Versions live in the existing catalog or shared build logic.\n- Stable production deps unless a required API needs a preview artifact.\n- Prefer KSP when supported; do not mix processor migration with unrelated work.\n- `minSdk` follows product policy; `compileSdk` / `targetSdk` changes need\n  platform review.\n- AGP built-in Kotlin only after verifying the active AGP migration guide.\n\n## Verify\n\n```bash\n./gradlew help --console=plain\n./gradlew :app:assembleDebug --console=plain\n./gradlew :app:testDebugUnitTest --console=plain\n./gradlew :app:lintDebug --console=plain\n```\n\nDiscover tasks with `./gradlew tasks --all`.\n\n## Guardrails\n\n- No dynamic dependency versions.\n- No generic template pasted over a live project.\n- No broad dependency upgrades during a feature-only task.\n- No package rename + architecture rewrite + toolchain bump in one change\n  unless the user asked for all of it.\n- No “latest” claims without an observed snapshot and a dated official source.\n"
}