SkillsAdd

krutikjain/android-agent-skills

android-material3-design-system

Apply Material 3 tokens, color, type, spacing, adaptive components, and theme ownership in Android apps.

First seen Mar 7, 2026

Installation

$ npx skills add krutikjain/android-agent-skills --skill android-material3-design-system
View on skills.sh ↗ GitHub repository ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

agent-browser Shared topics
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Shared topics
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Shared topics
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Shared topics
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-hosted-copilot-sdk Shared topics
microsoft/azure-skills 440.4K installs
azure-enterprise-infra-planner Shared topics
microsoft/azure-skills

Architect and provision enterprise Azure infrastructure from workload descriptions. For cloud a…

402.8K installs

Also in this package

Other skills from krutikjain/android-agent-skills · top by installs.

npx skills add krutikjain/android-agent-skills
android-di-hilt 335 android-kotlin-core 304 android-gradle-build-logic 303 android-testing-unit 294 android-compose-foundations 292 android-architecture-clean 289 android-coroutines-flow 257 android-networking-retrofit-okhttp 254 android-room-database 121 android-mobile-frontend-design 63

Browse all from krutikjain/android-agent-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 14
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version0.1.0
More metadata
version
0.1.0
category
ui
tags
["android","material3","design-system","compose"]
triggers
{"include":["material3 theme android","design system tokens compose","android typography color system","material components cleanup","adaptive material ui"],"exclude":["room dao issue","agp version mismatch","hilt injection only"]}
owners
["@android-agent-skills\/maintainers"]
test_targets
["examples\/orbittasks-compose","examples\/orbittasks-xml","benchmarks\/triggers.jsonl"]

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,780 B
  • docs SUMMARY.md 143 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 147 installs

SKILL.md

Android Material3 Design System

When To Use

  • Use this skill when the request is about: material3 theme android, design system tokens compose, android typography color system.
  • Primary outcome: Apply Material 3 tokens, color, type, spacing, adaptive components, and theme ownership in Android apps.
  • Handoff skills when the scope expands:
  • android-compose-foundations
  • android-compose-accessibility

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: Apply a coherent Material 3 theme to the Compose showcase screens.
  • Command: cd examples/orbittasks-compose && ./gradlew :app:assembleDebug

Edge case

  • Scenario: Keep XML and Compose surfaces visually aligned during mixed UI migration.
  • Command: cd examples/orbittasks-xml && ./gradlew :app:assembleDebug

Failure recovery

  • Scenario: Avoid routing theme-token work into accessibility or generic Compose foundations.
  • Command: python3 scripts/eval_triggers.py --skill android-material3-design-system

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