krutikJain/android-architecture-clean
skills/android-architecture-clean/SKILL.md
Apply clean architecture boundaries, use cases, repositories, and lifecycle-aware presentation models in Android projects.
$ install --global
skillsauthnpx skillsauth add krutikJain/android-agent-skills android-architecture-cleanInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 12:31 PM182.3s6 files scanned
SKILL.md
- name:
- android-architecture-clean
- description:
- Apply clean architecture boundaries, use cases, repositories, and lifecycle-aware presentation models in Android projects.
- version:
- 0.1.0
- category:
- foundations
- tags:
- ["android", "architecture", "clean-architecture", "layers"]
- include:
- ["clean architecture in android", "split use cases and repositories", "untangle presentation and data layer", "android architecture cleanup", "mvvm to cleaner boundaries"]
- exclude:
- ["retrofit config only", "compose animation tweak", "play store release only"]
- owners:
- ["@android-agent-skills/maintainers"]
- test_targets:
- ["examples/orbittasks-compose", "examples/orbittasks-xml", "benchmarks/triggers.jsonl"]
Android Architecture Clean
When To Use
- Use this skill when the request is about: clean architecture in android, split use cases and repositories, untangle presentation and data layer.
- Primary outcome: Apply clean architecture boundaries, use cases, repositories, and lifecycle-aware presentation models in Android projects.
- Handoff skills when the scope expands:
android-modularizationandroid-state-management
Workflow
- Map the request to the current Android stack, module boundaries, and minimum supported API level.
- Inspect the existing implementation for implicit assumptions, duplicate helpers, and outdated patterns.
- Apply the smallest change that improves correctness, readability, and long-term maintainability.
- Validate the result against the relevant showcase app path and repo benchmarks.
- Hand off adjacent work to the next specialized skill only after the core foundation is stable.
Guardrails
- Prefer official Android and Kotlin guidance over custom local conventions when they conflict.
- Keep public APIs boring and explicit; avoid clever abstractions that hide Android lifecycle costs.
- Do not mix architectural cleanup with product behavior changes unless the request explicitly needs both.
- Document any compatibility constraints that will affect old modules or generated code.
Anti-Patterns
- Sprinkling helpers across modules without a clear ownership boundary.
- Introducing framework-specific code into pure domain or data layers.
- Refactoring every adjacent file when only one contract needed to change.
- Leaving migration notes implied instead of writing them down.
Examples
Happy path
- Scenario: Separate OrbitTasks feature state, use case, and repository contracts.
- Command:
cd examples/orbittasks-compose && ./gradlew :app:testDebugUnitTest
Edge case
- Scenario: Keep XML activity actions thin while preserving saved-state behavior.
- Command:
cd examples/orbittasks-xml && ./gradlew :app:testDebugUnitTest
Failure recovery
- Scenario: Catch trigger confusion against modularization and state-management requests.
- Command:
python3 scripts/eval_triggers.py --skill android-architecture-clean
Done Checklist
- The implementation path is explicit, minimal, and tied to the right Android surface.
- Relevant example commands and benchmark prompts have been exercised or updated.
- Handoffs to adjacent skills are documented when the request crosses boundaries.
- Official references cover the chosen pattern and the main migration or troubleshooting path.
Official References
- https://developer.android.com/topic/architecture
- https://developer.android.com/topic/architecture/recommendations
- https://developer.android.com/jetpack/guide
- https://developer.android.com/topic/libraries/architecture/viewmodel
Related Skills
krutikJain/android-testing-ui
testing
VerifiedTrustedCommunity
Validate Android UI behavior with Compose UI tests, Espresso-style checks, screenshot assertions, and accessibility verification.
5SKILL.mdUpdated Apr 25, 2026
krutikJain/android-state-management
data-ai
VerifiedTrustedCommunity
Model screen state, events, reducers, and side effects for Android UIs with predictable lifecycle-aware ownership.
5SKILL.mdUpdated Apr 25, 2026
krutikJain/android-serialization-offline-sync
tools
VerifiedTrustedCommunity
Coordinate serialization, caching, conflict handling, and offline-first sync flows in Android apps.
5SKILL.mdUpdated Apr 25, 2026
krutikJain/android-security-best-practices
development
VerifiedTrustedCommunity
Apply Android app security guidance around secrets, storage, network trust, exported components, and least privilege.
5SKILL.mdUpdated Apr 25, 2026