agentleFS
Sign inStart free
krutikJainkrutikJain/android-agent-skills/.github/skills/android-compose-accessibility/SKILL.md

android-compose-accessibility

Skill14 starsChanged 8 months agoMITView on GitHub

Make Compose interfaces accessible with semantics, announcements, contrast, focus order, and adaptive touch targets.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the request is about: compose accessibility review, android semantics issue compose, focus order in compose.

    line 17
  2. Distinctive:

    Do not mix Compose and View system ownership without an explicit interoperability boundary.

    line 33
  3. Distinctive:

    Prefer measured performance work over premature micro-optimizations.

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
SKILL.md

Android Compose Accessibility

When To Use

  • Use this skill when the request is about: compose accessibility review, android semantics issue compose, focus order in compose.
  • Primary outcome: Make Compose interfaces accessible with semantics, announcements, contrast, focus order, and adaptive touch targets.
  • Handoff skills when the scope expands:
  • android-ui-states-validation
  • android-testing-ui

Workflow

  1. Identify whether the target surface is Compose, View system, or a mixed interoperability screen.
  2. Select the lowest-friction UI pattern that satisfies responsiveness, accessibility, and performance needs.
  3. Build the UI around stable state, explicit side effects, and reusable design tokens.
  4. Exercise edge cases such as long text, font scaling, RTL, and narrow devices in the fixture apps.
  5. Validate with unit, UI, and screenshot-friendly checks before handing off.

Guardrails

  • Optimize for stable state and predictable rendering before adding animation or abstraction.
  • Respect accessibility semantics, contrast, focus order, and touch target guidance by default.
  • Do not mix Compose and View system ownership without an explicit interoperability boundary.
  • Prefer measured performance work over premature micro-optimizations.

Anti-Patterns

  • Embedding navigation or business logic directly in leaf UI components.
  • Using fixed dimensions that break on localization or dynamic text.
  • Ignoring semantics and announcing only visual changes.
  • Porting XML patterns directly into Compose without adapting the mental model.

Examples

Happy path

  • Scenario: Add semantics and readable labels to the Compose OrbitTasks cards.
  • Command: cd examples/orbittasks-compose && ./gradlew :app:connectedDebugAndroidTest

Edge case

  • Scenario: Validate font scaling, contrast, and touch targets in narrow layouts.
  • Command: cd examples/orbittasks-compose && ./gradlew :app:assembleDebug

Failure recovery

  • Scenario: Differentiate accessibility requests from general UI validation or theme work.
  • Command: python3 scripts/eval_triggers.py --skill android-compose-accessibility

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

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.

Check your setup, free