Android architecture

Skill GDvega/super-android-kotlin-firebase-skill/skills/android-architecture

A modular Agent Skills repository for Android, Kotlin, Jetpack Compose and Firebase development.

Install

npx -y skills add GDvega/super-android-kotlin-firebase-skill --skill android-architecture

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use for Clean Architecture, MVVM, MVI, multimodule design, domain/data/presentation boundaries, repositories, use cases, DTO/entity/domain mapping and offline-first architecture.

SKILL.md

2.9 KB, as published. Nobody here has run it

Purpose

Design or review pragmatic Android architecture for real apps without over-engineering.

When to use

Creating a new app structure.
Refactoring UI, domain and data boundaries.
Introducing multimodule structure or offline-first behavior.
Reviewing repositories, use cases and mappers.

Inputs to inspect

Module tree and dependency graph.
Current package structure.
Data sources and sync requirements.
Tests and build times.

Required workflow

Map current architecture and dependencies.
Identify concrete coupling or testability problems.
Propose the smallest boundary that solves the problem.
Refactor around contracts and tests.
Validate build and affected tests.

Rules

UI must not know Firebase, Room or Retrofit details directly.
Domain should not depend on Android SDK.
Repositories hide local/remote data sources.
Add modules only when they reduce real coupling.
Prefer offline-first when product requirements need resilience.

Related existing skills

Local skills to invoke

kotlin-core
dependency-injection
room-datastore
networking-retrofit-ktor
firebase-core
testing

External companion skills to use when installed

Do not assume these companion skills are installed. Prefer the local skills above first, then consult Companion Skills for install and verification commands.

android/skills — use for official Android workflow alignment around edge-to-edge, adaptive UI, Navigation 3, R8, AGP or testing setup.

Files commonly touched

settings.gradle.kts
feature modules
core/data
core/domain
core/database
core/network
repository and mapper files

Commands to validate

./gradlew projects
./gradlew test
./gradlew assembleDebug
./gradlew lint

Common mistakes to avoid

Adding empty layers for dogma.
Moving everything in one giant refactor.
Creating trivial use cases for every repository call.
Breaking dependency direction.

Checklist

Boundaries named.
Dependencies directional.
Repositories testable.
Offline strategy explicit.
Incremental plan exists.

Example prompts

Use $super-android-kotlin-firebase to review my Android architecture.
Use $super-android-kotlin-firebase to split this feature into UI/domain/data.

Expected response style

Respond with: brief diagnosis, change plan, affected files, code or diff summary, validation commands, tests added or recommended, risks, and next step. For review tasks, lead with findings ordered by severity.

References

../../docs/audits/FUENTES_LOCALES.md
references/clean-architecture-pragmatic.md
templates/feature-module-template.md