Make your AI coding tool actually understand Compose.
Backed by real androidx/androidx source code — not vibes.
AI coding tools generate Compose code that compiles but gets the details wrong. Incorrect remember usage, unstable recompositions, broken modifier ordering, deprecated navigation patterns, hallucinated APIs that don't exist. They guess at behavior instead of knowing it.
This skill fixes that by giving your AI assistant two things:
- 13 reference guides covering every major Compose topic with do/don't examples and common pitfalls
- 5 source code files pulled directly from
androidx/androidxso the agent can check how things actually work
Think of it as the Compose equivalent of AvdLee/SwiftUI-Agent-Skill — same idea, Android/Kotlin world.
| Area | Without the skill | With it |
|---|---|---|
| State | Uses remember { mutableStateOf() } everywhere, even when derivedStateOf or rememberSaveable is the right call |
Picks the right state primitive for each situation |
| Performance | Generates code that recomposes every frame | Applies stability annotations, deferred reads, key {} on lists |
| Navigation | String-based routes (deprecated) | Type-safe routes with @Serializable route classes |
| Modifiers | Random ordering, misses clickable before padding bugs |
Correct ordering with reasoning |
| Side effects | Wrong coroutine scope, bad LaunchedEffect keys |
Correct effect selection and lifecycle-aware keys |
| APIs | Hallucinates parameters that don't exist | Checks against actual source before suggesting |
| Topic | What the agent learns |
|---|---|
| State management | remember, mutableStateOf, derivedStateOf, rememberSaveable, state hoisting, snapshotFlow |
| View composition | Structuring composables, slot APIs, @Preview patterns, extraction rules |
| Performance | Recomposition skipping, @Stable/@Immutable, deferred reads, baseline profiles, benchmarking |
| Navigation | Type-safe routes, NavHost, deep links, shared element transitions, back stack |
| Animation | animate*AsState, AnimatedVisibility, Crossfade, updateTransition, shared transitions |
| Lists and scrolling | LazyColumn/LazyRow/LazyGrid, Pager, key {}, contentType, scroll state |
| Side effects | LaunchedEffect, DisposableEffect, SideEffect, rememberCoroutineScope |
| Modifiers | Ordering rules, custom modifiers, Modifier.Node migration |
| Theming | MaterialTheme, ColorScheme, dynamic color, Typography, shapes, dark theme |
| Accessibility | Semantics, content descriptions, traversal order, touch targets, TalkBack |
| CompositionLocals | LocalContext, LocalDensity, custom locals, when to use vs. parameter passing |
| Deprecated patterns | Removed APIs, migration paths from older Compose versions |
| Styles API (experimental) | Style {}, MutableStyleState, Modifier.styleable(), composition, theme integration, alpha06 gotchas |
| Source code | Actual .kt from androidx/androidx for runtime, UI, foundation, material3, navigation |
You ask about Compose
|
v
AI reads SKILL.md (workflow + checklists)
|
v
Consults the right reference file
|
+-- state-management.md
+-- performance.md
+-- navigation.md
+-- ... (12 guides total)
|
+-- source-code/
+-- runtime-source.md
+-- material3-source.md
+-- ... (5 source files)
Layer 1: guidance docs (13 files, ~130KB) — practical references with patterns, pitfalls, and do/don't examples. This is what the agent reads first.
Layer 2: source code receipts (5 files, ~2.3MB) — the actual Kotlin source from androidx/androidx (branch: androidx-main). When the agent needs to verify an implementation detail rather than guess, it reads these.
jetpack-compose-expert-skill/
├── SKILL.md # Main workflow + checklists
└── references/
├── state-management.md # State, remember, hoisting, derivedStateOf
├── view-composition.md # Structuring composables, slots, previews
├── modifiers.md # Modifier ordering, custom modifiers, Modifier.Node
├── side-effects.md # LaunchedEffect, DisposableEffect, SideEffect
├── composition-locals.md # CompositionLocal, LocalContext, custom locals
├── lists-scrolling.md # LazyColumn/Row/Grid, Pager, keys, contentType
├── navigation.md # NavHost, type-safe routes, deep links
├── animation.md # animate*AsState, AnimatedVisibility, transitions
├── theming-material3.md # MaterialTheme, ColorScheme, dynamic color
├── performance.md # Recomposition, stability, benchmarking
├── accessibility.md # Semantics, content descriptions, testing
├── deprecated-patterns.md # Removed APIs, migration paths
├── styles-experimental.md # Styles API (@ExperimentalFoundationStyleApi)
└── source-code/ # Actual .kt source from androidx/androidx
├── runtime-source.md # Composer, Recomposer, State, Effects
├── ui-source.md # AndroidCompositionLocals, Modifier, Layout
├── foundation-source.md # LazyList, BasicTextField, Gestures
├── material3-source.md # MaterialTheme, all M3 components
└── navigation-source.md # NavHost, ComposeNavigator
The skill is just markdown files. Every tool below reads the same content. Pick yours.
Skills are file-based — Claude Code discovers them automatically from ~/.claude/skills/ (personal) or .claude/skills/ (project-specific).
Personal skill (available in all your projects):
# Clone the repo
git clone https://github.com/aldefy/compose-skill.git /tmp/compose-skill
# Copy into your personal skills directory
mkdir -p ~/.claude/skills
cp -r /tmp/compose-skill/jetpack-compose-expert-skill ~/.claude/skills/Project-specific skill (just one project):
# Clone the repo
git clone https://github.com/aldefy/compose-skill.git /tmp/compose-skill
# Copy into your project's .claude/skills directory
mkdir -p .claude/skills
cp -r /tmp/compose-skill/jetpack-compose-expert-skill .claude/skills/No CLI command or config file needed. Claude Code picks up SKILL.md from these directories automatically and triggers when you mention Compose, @Composable, remember, LazyColumn, NavHost, etc.
Add an AGENTS.md file to your project root:
# AGENTS.md
## Jetpack Compose
For all Compose/Android UI tasks, follow the instructions in
`jetpack-compose-expert-skill/SKILL.md` and consult the reference
files in `jetpack-compose-expert-skill/references/` before answering.Add the skill to your project as a submodule:
git submodule add https://github.com/aldefy/compose-skill.git .compose-skillCodex discovers AGENTS.md files automatically from the git root down to the current directory.
Add to GEMINI.md in your project root:
# GEMINI.md
## Jetpack Compose Expert
For all Jetpack Compose tasks, follow the workflow and checklists in
`jetpack-compose-expert-skill/SKILL.md`.
Before answering any Compose question, consult the relevant reference:
- State management -> `jetpack-compose-expert-skill/references/state-management.md`
- Performance -> `jetpack-compose-expert-skill/references/performance.md`
- Navigation -> `jetpack-compose-expert-skill/references/navigation.md`
- (see SKILL.md for the full topic -> file mapping)
For implementation details, check actual source code in
`jetpack-compose-expert-skill/references/source-code/`.Add as a submodule:
git submodule add git@github.com:aldefy/compose-skill.git .compose-skillCreate .cursor/rules/compose-skill.mdc:
---
description: Jetpack Compose expert guidance
globs: **/*.kt
---
Follow the instructions in `jetpack-compose-expert-skill/SKILL.md`
for all Compose-related code. Consult reference files in
`jetpack-compose-expert-skill/references/` before suggesting patterns.Or paste the contents of SKILL.md into Settings > Rules for AI.
Add to .github/copilot-instructions.md:
## Jetpack Compose
For Compose/Android UI work, follow the skill instructions in
`jetpack-compose-expert-skill/SKILL.md`. Consult reference files in
`jetpack-compose-expert-skill/references/` for patterns, pitfalls,
and source-code-backed guidance.Create .windsurf/rules/compose-skill.md in your project root:
For all Jetpack Compose tasks, follow the workflow in
`jetpack-compose-expert-skill/SKILL.md` and consult the reference
files in `jetpack-compose-expert-skill/references/` before answering.Note: The legacy
.windsurfrulesfile also works but.windsurf/rules/is the current approach.
Add to .amazonq/rules/compose.md:
For all Jetpack Compose tasks, follow the workflow in
`jetpack-compose-expert-skill/SKILL.md` and consult the reference
files in `jetpack-compose-expert-skill/references/` before answering.It's just markdown. Clone this repo into your project (or add as a submodule), then point your tool's instruction file at jetpack-compose-expert-skill/SKILL.md. The agent reads SKILL.md for the workflow and pulls from references/ as needed.
After setup, just talk to your AI assistant normally:
"My LazyColumn is janky when scrolling — help me fix it"
What happens:
- Agent reads
SKILL.mdfor the workflow - Pulls in
references/lists-scrolling.mdandreferences/performance.md - Checks your code for missing
key {}, unstable item types, heavy compositions in item blocks - If something's unclear, verifies against
references/source-code/foundation-source.md - Gives you a fix based on the actual
LazyListimplementation
No hallucinated APIs. No guessed behavior.
All source code comes from androidx/androidx under Apache License 2.0. The guidance docs are original analysis of those sources plus official Android documentation.
PRs welcome, especially:
- Coverage for new Compose APIs or patterns
- Corrections based on newer Compose releases
- Additional source files for gaps
- Compose Multiplatform (Desktop, iOS, Web) guidance
- Auto-update tooling for tracking new
androidxreleases
MIT — see LICENSE.
Source code from androidx/androidx is Apache License 2.0, copyright The Android Open Source Project.