android

Files (17)

• SKILL.md
• openai.yaml · agents/
• android-assets.md · references/
• android-flavors.md · references/
• config-schema.md · references/
• firebase.md · references/
• network-security.md · references/
• __init__.py · scripts/android_mobile_config/
• assets.py · scripts/android_mobile_config/
• cli.py · scripts/android_mobile_config/
• config.py · scripts/android_mobile_config/
• firebase.py · scripts/android_mobile_config/
• gradle_kts.py · scripts/android_mobile_config/
• network_security.py · scripts/android_mobile_config/
• package_name.py · scripts/android_mobile_config/
• resources.py · scripts/android_mobile_config/
• mobile-app-config · scripts/

SKILL.md (first lines)

# Mobile App Config

Use this skill for Android app configuration tasks that are fragile to edit by hand. Prefer the bundled CLI scripts over manual Gradle, manifest, or resource edits.

## Quick Start

Use the bundled CLI at `scripts/mobile-app-config`, resolved relative to this `SKILL.md`. Run it with cwd set to the Android project root.

```bash
mobile-app-config flavors
mobile-app-config package-name --application-id com.example.app
mobile-app-config firebase --mode single --project my-firebase
mobile-app-config assets --type all --image branding/logo.png
mobile-app-config network-security
```

Commands infer Android defaults in memory when `android-app-config.json` is missing. `init` creates the file, and commands that persist explicit options update it.

## Workflow

1. Inspect the current project root and confirm the Android app module.
2. Run the relevant script instead of hand-editing generated sections.
3. Run the matching validation command or Android Gradle task.
4. Re-run the command when checking idempotency; the second run should not duplicate Gradle blocks, resource files, or manifest attributes.
5. After flavor generation, run Gradle Sync in Android Studio; expected variants are `devDebug`, `stgDebug`, `prodDebug`, `devRelease`, `stgRelease`, and `prodRelease`.

## Commands

- `mobile-app-config init`: create `android-app-config.json`; pass `--force` only when intentionally replacing an existing config.
- `mobile-app-config flavors`: configure product flavors and flavor-specific `app_name` resources.
- `mobile-app-config validate-flavors`: validate configured flavors and expected task names.
- `mobile-app-config package-name`: sync `applicationId`, namespace, Kotlin/Java source package declarations, optional `--app-name`, and optional `--root-project-name`.
- `mobile-app-config validate-package-name`: validate package-name sync.
- `mobile-app-config firebase`: configure Firebase `google-services.json` files using Firebase CLI when `firebase.enabled=true` or Firebase flags are provided.
- `mobile-app-config validate-firebase`: validate Firebase config files, package names, and Google Services Gradle plugin wiring.
- `mobile-app-config assets`: generate app icons or splash screens by type.
- `mobile-app-config validate-assets`: validate generated asset resources by type.
- `mobile-app-config network-security`: configure network security only when `networkSecurity.enabled=true`.
- `mobile-app-config validate-network-security`: validate network-security files and manifest references.

Splash resources use Android 12+ platform attrs and Android 11-and-below `windowBackground`. This plugin does not add AndroidX SplashScreen or call `installSplashScreen()`.

## References

- Read `references/config-schema.md` before changing config shape.
- Read `references/android-flavors.md` before changing Gradle flavor behavior.
- Read `references/firebase.md` before changing Firebase behavior.
- Read `references/android-assets.md` before changing asset generation.
- Read `references/network-security.md` before changing network-security behavior.

From dthuy62/mobile-app-config, MIT.

More from dthuy62/mobile-app-config