Skip to content

Agent skills for Jetpack Compose UI

Short answer: a skill is a folder holding a short SKILL.md and some reference files. The agent loads it when the task matches. For Compose, it fixes the main weakness of agents working from memory: they don’t know which API version you’re on. Check a skill by building the code it contains.

  • It loads only when needed. The agent reads a short description on every task and opens the full skill only for Compose UI work, so it doesn’t fill your context.
  • It can be big where it matters. API tables, deprecations and code samples live in reference files that the agent opens on demand.
  • It’s shared and versioned. Everyone on the team gets the same rules, updated in one place.
  1. Does it name the library version it was checked against? Material 3 Expressive changed a lot between 1.4.0, the 1.5.0 alphas and the betas.
  2. Does its code compile? Copy two samples into your project. If they need fixes, the agent’s output will too.
  3. Does it say what’s deprecated? An agent without that keeps writing yesterday’s API.

This skill pins material3 1.5.0-beta02 and compiles its 28 samples in CI.

skills CLI: Claude Code, Codex, Cursor, Copilot and more
npx --yes skills add sanikantv/m3-expressive-skill --skill m3-expressive-compose -y

Listed on skills.sh, the agent skills directory.

Want your agent to get this right every time? Install the skill. If this page helped,star the repo on GitHub.

Built by Sanikant. Set in Google Sans Flex (SIL Open Font License), icons from Material Symbols (Apache 2.0). Material Design is a Google trademark; this project is not affiliated with Google.