platform-design-skills / android
AGENTS.md603 starsChanged 8 months agoMITView on GitHub
Material Design 3 guidelines and Android platform conventions for Jetpack Compose and XML layouts. Apply these guidelines when: - Building or reviewing Android UI code - Implementing Material You / dynamic color - Designing navigation, layout, or component architecture - Auditing accessibility or platform compliance Rules marked CRITICAL must never be violated. Rules marked HIGH should be followed unless there is a documented reason. Rules marked MEDIUM are recommended best practices.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,439 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/ios/AGENTS.mdAGENTS.md
- skills/ipados/AGENTS.mdAGENTS.md
- skills/macos/AGENTS.mdAGENTS.md
- skills/tvos/AGENTS.mdAGENTS.md
- skills/visionos/AGENTS.mdAGENTS.md
- skills/watchos/AGENTS.mdAGENTS.md
- skills/web/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- android-design-guidelinesSkill
- ios-design-guidelinesSkill
- ipados-design-guidelinesSkill
- macos-design-guidelinesSkill
- tvos-design-guidelinesSkill
- visionos-design-guidelinesSkill
- watchos-design-guidelinesSkill
- web-design-guidelinesSkill
The file
We split this AGENTS.md into the rules it gives an agent
10 rules. About 0 are common, 7 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
Never hardcode color hex values — always use MaterialTheme.colorScheme color roles
- Very specific: line 26
Never use dp for text sizes — use sp so user font scaling applies
- Very specific: line 27
Never override onBackPressed() — use BackHandler (Compose) or OnBackInvokedCallback (View-based) for predictive back
- Distinctive: line 28
Never place touch targets below 48x48dp — accessibility violation
- Distinctive: line 29
Never request permissions at app launch — request in context with a rationale
- Distinctive: line 30
Never use pure black (#000000) for dark theme backgrounds — use Material surface roles
- Distinctive: line 31
Never put icon-only items in the navigation bar — labels are required
- Distinctive: line 32
Never use a dialog for non-critical information — prefer Snackbar or Bottom Sheet
- Distinctive: line 33
Never use more than one FAB on a screen — one FAB for the single primary action
- Distinctive: line 34
Never show full-width content on tablet layouts — use list-detail or max-width containers
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Android Design Skill
Material Design 3 guidelines and Android platform conventions for Jetpack Compose and XML layouts.
Structure
SKILL.md— Full guideline rules with code examplesrules/_sections.md— Indexed section breakdown for quick lookupmetadata.json— Version and reference metadata
Usage
Apply these guidelines when:
- Building or reviewing Android UI code
- Implementing Material You / dynamic color
- Designing navigation, layout, or component architecture
- Auditing accessibility or platform compliance
Priority
Rules marked CRITICAL must never be violated. Rules marked HIGH should be followed unless there is a documented reason. Rules marked MEDIUM are recommended best practices.
Never Do
- Never hardcode color hex values — always use
MaterialTheme.colorSchemecolor roles - Never use
dpfor text sizes — usespso user font scaling applies - Never override
onBackPressed()— useBackHandler(Compose) orOnBackInvokedCallback(View-based) for predictive back - Never place touch targets below 48x48dp — accessibility violation
- Never request permissions at app launch — request in context with a rationale
- Never use pure black (#000000) for dark theme backgrounds — use Material surface roles
- Never put icon-only items in the navigation bar — labels are required
- Never use a dialog for non-critical information — prefer Snackbar or Bottom Sheet
- Never use more than one FAB on a screen — one FAB for the single primary action
- Never show full-width content on tablet layouts — use list-detail or max-width containers
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.

