agentleFS
ehmoehmo/platform-design-skills/skills/android/AGENTS.md

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.

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
  1. Very specific:

    Never hardcode color hex values — always use MaterialTheme.colorScheme color roles

    line 25
  2. Very specific:

    Never use dp for text sizes — use sp so user font scaling applies

    line 26
  3. Very specific:

    Never override onBackPressed() — use BackHandler (Compose) or OnBackInvokedCallback (View-based) for predictive back

    line 27
  4. Distinctive:

    Never place touch targets below 48x48dp — accessibility violation

    line 28
  5. Distinctive:

    Never request permissions at app launch — request in context with a rationale

    line 29
  6. Distinctive:

    Never use pure black (#000000) for dark theme backgrounds — use Material surface roles

    line 30
  7. Distinctive:

    Never put icon-only items in the navigation bar — labels are required

    line 31
  8. Distinctive:

    Never use a dialog for non-critical information — prefer Snackbar or Bottom Sheet

    line 32
  9. Distinctive:

    Never use more than one FAB on a screen — one FAB for the single primary action

    line 33
  10. Distinctive:

    Never show full-width content on tablet layouts — use list-detail or max-width containers

    line 34

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

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 examples
  • rules/_sections.md — Indexed section breakdown for quick lookup
  • metadata.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.colorScheme color roles
  • Never use dp for text sizes — use sp so user font scaling applies
  • Never override onBackPressed() — use BackHandler (Compose) or OnBackInvokedCallback (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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.