<div align="center">

Compose Skill (Compose Kit)

A Compose skill for AI coding agents: seven agent skills that make Claude Code, Codex, Cursor, Copilot and Gemini write better Jetpack Compose and Compose Multiplatform code.<br> One consistent house style, measured on five models in real agent CLIs.

Works with Claude Code · Codex · Cursor · OpenCode · Copilot · Gemini CLI · Antigravity

Website: compose.avinya.dev · Install guides per agent · Results

</div> <table> <tr> <td align="center" width="25%"><h2>+25.6</h2>points for<br><b>Gemini 3.8 Flash</b><br>with the kit</td> <td align="center" width="25%"><h2>+18.6</h2>points for<br><b>Sonnet 5.5</b><br>with the kit</td> <td align="center" width="25%"><h2>120</h2>agentic runs<br>on 8 never-seen tasks</td> <td align="center" width="25%"><h2>2</h2>blind graders from other vendors<br>must agree on every item</td> </tr> </table> <p align="center"> <picture> <source media="(prefers-color-scheme: dark)" srcset="docs/assets/v5-kit-lift-dark.svg"> <img alt="Held-out v5: rubric score with and without the kit. Gemini 3.8 Flash 51.2% to 76.7% (+25.6), Sonnet 5.5 55.8% to 74.4% (+18.6), Opus 5.5 65.1% to 74.4% (+9.3), GPT-6-Sol 72.1% to 76.7% (+4.6), GPT-6-Luna 65.1% to 67.4% (+2.3)." src="docs/assets/v5-kit-lift-light.svg" width="760"> </picture> </p>

Why

AI agents write Compose that compiles and then drifts: state ends up in the wrong place, every screen gets its own pattern, error handling changes from file to file, and reviews flag perfectly fine code as blocking. Compose Kit gives the agent one house style plus the reasoning behind it, and only loads the parts the current task needs.

• One consistent style: MVI on a shared BaseViewModel contract, Koin annotations, Navigation 3, feature-owned data/domain/presentation layers, and typed error handling.
• Progressive loading: a ~1.3k-token entry tree picks the task path and the exact reference files. The full kit is about 127k tokens; in the v5 test, 35 of 40 kit runs loaded under 20k.
• Respects your project: in a coherent existing codebase (Hilt, MVVM, Navigation 2, your own base class), the kit follows your pattern and proposes migration separately.
• Checked, not trusted: 11 shell guard scripts catch drift in CI, backed by 90 fixture tests.

What's inside

| Skill | What it owns | |---|---| | compose | The entry decision tree (~1.3k tokens): task kind → affected area → exact reference files | | compose-architecture | Module graph, MVI/BaseViewModel contract, error tiers, state ownership, naming, Koin DI, Navigation 3, coroutines | | compose-feature | A screen or feature slice end to end: contract, ViewModel, UI, navigation, DI and tests; review mode | | compose-ui | Composables: Route/Screen split, stability, loading/empty/error states, lists, animation, accessibility, resources | | compose-data | Repositories, Ktor, Room, DataStore, Paging 3, offline-first, data-layer tests | | compose-project | New projects, adopting the kit, modules, convention plugins, version catalog, CI and agent hooks | | compose-platform | commonMain vs expect/actual, iOS/Swift interop, desktop and web targets, platform lifecycle |

Also included: project and feature templates, and the guard scripts (compose-architecture/scripts/).

How it works

flowchart TD
    P["Your prompt"] --> E["compose entry tree · ~1.3k tokens"]
    E --> K{"What kind of task?<br/>new feature · change · bug fix · review<br/>conform · setup · question"}
    K --> A{"Which areas does it touch?<br/>architecture · feature · ui<br/>data · project · platform"}
    A --> F["Load one reference file per affected area"]
    F --> C["Code in the house style"]

Install

Install all seven skills. compose is the entry point, and it hands each task to the other six. Step-by-step pages for each agent are on the website: Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI and Antigravity, OpenCode.

Every option below can install for one project (lives in the repo, so your team gets it too) or globally (for you, in every project on your machine).

npx skills

Needs Node 22.20+. Works with Claude Code, Codex, Cursor, OpenCode, Copilot, Gemini CLI, Antigravity and 70+ other agents.

# This project only (run it in the repo root)
npx skills add Meet-Miyani/compose-skill --skill '*' -a claude-code

# Globally, for every project
npx skills add Meet-Miyani/compose-skill --skill '*' -a claude-code -g

Swap claude-code for your agent: codex, cursor, opencode, github-copilot, gemini-cli, antigravity. Repeat -a to install for several at once. Leave it out and you get an interactive picker.

| Agent | This project | Global | |---|---|---| | Claude Code | .claude/skills/ | ~/.claude/skills/ | | Codex, Cursor, OpenCode, Copilot, Gemini CLI, Antigravity | .agents/skills/ | the agent's own folder, e.g. ~/.codex/skills/ |

gh skill

Needs GitHub CLI 2.90+. Pass --pin: without it, gh skill takes the latest stable release, which is still the old v5.1.0. Pass --agent too: without it, a non-interactive run installs for GitHub Copilot.

for s in compose compose-architecture compose-feature compose-ui compose-data compose-project compose-platform; do
  gh skill install Meet-Miyani/compose-skill "$s" --pin v6.0.0-preview.1 --agent claude-code --scope project
done

Use --scope user to install globally. Agent IDs: claude-code, codex, cursor, opencode, gemini-cli, antigravity, github-copilot.

Claude Code plugin

/plugin marketplace add Meet-Miyani/compose-skill
/plugin install compose-kit@compose-kit

From a terminal, the same with a scope: user (the default, every project), project (shared through the repo) or local (this project, just you).

claude plugin marketplace add Meet-Miyani/compose-skill
claude plugin install compose-kit@compose-kit --scope project

Codex plugin

codex plugin marketplace add Meet-Miyani/compose-skill
codex plugin add compose-kit@compose-kit

Codex plugins install for your user, so they're available in every project.

Then point your agent at it

Add this line to the project's AGENTS.md or CLAUDE.md:

Compose/CMP work: load the compose skill first; it picks the path and the files to read.

The skills also trigger on their own; the line just makes sure the entry tree loads first.

Coming from the old single compose skill (v5.x or the composekit CLI)? Delete the old compose folder from your agent's skills directory, then install with any option above. The old CLI's update can't fetch v6.

Optional: install the guard scripts into a project to catch drift in CI:

bash <skills dir>/compose-architecture/scripts/install-guards.sh <project>

Results: held-out v5

This is the test v6.0.0-preview.1 shipped on. Five models got 8 tasks they had never seen, in a fresh app, inside their own agent CLIs. Each task ran three times: with no kit, with a short generic "senior engineer" prompt, and with the kit. That's 120 runs. Two models from the other vendors graded every answer blind, and an item only counts if both of them pass it. The rules were written down before the tasks existed, and the grades were frozen before anything was scored.

| Model | No kit | Generic prompt | With the kit | Kit − no kit | Verdict | |---|---:|---:|---:|---:|---| | Gemini 3.8 Flash | 51.2% | 46.5% | 76.7% | +25.6 | ✅ Recommended | | Sonnet 5.5 | 55.8% | 60.5% | 74.4% | +18.6 | ✅ Recommended | | Opus 5.5 | 65.1% | 62.8% | 74.4% | +9.3 | ✅ Recommended (see erratum) | | GPT-6-Sol | 72.1% | 74.4% | 76.7% | +4.6 | ➖ Neutral: within noise | | GPT-6-Luna | 65.1% | 60.5% | 67.4% | +2.3 | ❌ Not yet: engineering items fell (−11.1) | | Muse Spark 1.3 (add-on) | 58.1% | 62.8% | 60.5% | +2.4 | No lift |

• House-style items rose for every model, from 37-50% without the kit to 56-69% with it.
• On engineering-only items, Sonnet (+11.1) and Flash (+40.8) beat the generic prompt by 8+ points; for Opus, Sol and Luna a short generic prompt does about as well.

By task type, all five panel models together (both graders agree):

| Task type | No kit | Generic prompt | With the kit | | |---|---:|---:|---:|---| | New features (3 tasks) | 43.5% | 47.1% | 70.6% | The biggest win: where data lives, navigation results, background work | | Bug fixes (2) | 80.0% | 88.6% | 82.9% | Every setup fixed the bugs; the kit adds little here | | Reviews (2) | 72.9% | 64.3% | 84.3% | These two tasks had flawed setups, see the erratum below | | "Match our conventions" (1) | 68.0% | 60.0% | 44.0% | Worse with the kit: models restructured too much. This is the main v6.1 fix |

Computed from the frozen grades by v5-by-task-type.py.

Erratum (2026-10-01). Two review tasks had flawed setups. No pre-registered outcome changes, but Opus's +9.3 depends on those two tasks (+3.4 without them). The Claude model was Sonnet 5.5, first published as "Sonnet 5". Details: VERDICT.md.

<p align="center"> <picture> <source media="(prefers-color-scheme: dark)" srcset="docs/assets/v5-kit-context-dark.svg"> <img alt="Most kit tokens any single task loaded: Opus 5.5 9.9k, Sonnet 5.5 14.0k, GPT-6-Luna 18.3k, GPT-6-Sol 26.4k, Gemini 3.8 Flash 26.5k, against a 20k design budget." src="docs/assets/v5-kit-context-light.svg" width="760"> </picture> </p>

Every panel model opened compose first on every task. Kit context is an upper bound (the full size of every kit file opened). Details: kit-tokens.txt.

How we test

• New tasks every round. A separate model writes them in a new app domain without ever seeing the kit, and they're sealed before the first run.
• A gate, not a promise. A script builds every task's setup and runs its hidden behaviour tests. Tasks that fail the gate or a manual content check go back to the author or get repaired, and every repair is written down.
• Real agents on a real app. Claude Code, Codex, Antigravity and OpenCode, each driving its own model headless on a Kotlin Multiplatform project.
• Blind, cross-vendor grading. Answers are shuffled and stripped of anything that gives away the model or the setup. Two graders from the other vendors score each one.
• Pre-registered. Pass/fail rules come before the tasks, grades are frozen before scoring, and mistakes get a pub