android-engineering
Skill1 starsChanged 6 months agoNo licenceView on GitHub
Senior Android engineering standards for Kotlin + Jetpack Compose apps. Covers architecture (MVVM, layers, StateFlow), platform norms (battery, background, clock, permissions), Material Design 3, accessibility, security, and ecosystem conventions. Use this skill whenever writing, reviewing, or designing Android/Kotlin code — including ViewModels, Repositories, Composables, Services, and data layer components. Also trigger when discussing architecture decisions, UI patterns, or Android-specific constraints.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- PhoenixNest/AGENT-GLOBAL-BASEtheir own version, first seen Oct 20, 2026
- foreturn/product-studiotheir own version, first seen Oct 14, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- foreturn/product-studio★ 3same name
- PhoenixNest/AGENT-GLOBAL-BASE★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- code-integrity-guardrailSkill
- compressSkill
- coverageSkill
- ctx-loadSkill
- database-migrationSkill
- go-engineeringSkill
- integration-testingSkill
- observability-implementationSkill
- patch-claudeSkill
- python-engineeringSkill
- requirements-engineeringSkill
- resource-managementSkill
- session-handoffSkill
- software-development-orchestratorSkill
- spec-auditSkill
- spec-contract-methodologySkill
- spec-driven-testingSkill
- spec-driverSkill
- system-designSkill
- test-runnerSkill
The file
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.