Plugin
material-3-skill
A comprehensive skill for AI coding assistants that can load SKILL.md files, covering Google's Material Design 3 (Material You) UI system.
1 skill1.5k
@hamenMobile
Plugin
compose-skill
A strict, evidence-based audit skill for Android Jetpack Compose repositories.
Plugin Signal54/100Fair
maintained55
capable23
documented100
adopted55
Install on Claude Code
> /plugin marketplace add hamen/compose_skill
What's inside
Skill(2 skills)
/compose-agentHelps AI coding assistants write modern Jetpack Compose: correct state, side effects, performance-aware modifiers, Navigation 3, Paging 3 in Compose, coroutines on lifecycle, animations, UI tests, focus/keyboard navigation, Compose Multiplatform boundaries, idiomatic Kotlin, and/jetpack-compose-auditAudit Android Jetpack Compose repositories for performance, animation phase correctness, state management, side effects, composable API quality, and adjacent Android launch UX resource risks such as blurry Android 12+ splash icons. Scans source code, scores each category from
README
compose-agent 4.4.0 · 2026-07-07 — Authoring guidance so the coding-agent skill warns while you write — Never Back-Write Across Phases and Optimizations That Do Nothing — now backed by its own write-mode acceptance evals (CI-enforced to track the audit's rules). The 4.3.0 audit catches these after the fact; compose-agent stops you writing them.
jetpack-compose-audit 4.3.2 · 2026-07-07 — Cross-phase back-write detection (axis 3: layout callbacks writing state read in composition), a related composition-phase self-invalidation check (snapshot collections mutated in a composable body), and a False Leads scoring guard so the auditor stops crediting no-op "recomposition fixes." Adapted from chrisbanes/skills (Apache-2.0).
Version 4.2.0 · 2026-06-17 — Paging 3 in Compose: new paging.md reference (LLM guardrails, not API tour), audit hooks under existing Performance/State categories, planning doc at docs/paging-skill-plan.md. Validated through multi-agent cross-review. Both skills ship as 4.2.0.
Find out where your Compose app is burning frames, by how much, and what to change to win them back — measured against real compiler data, not vibes.
A strict, evidence-based audit for Android Jetpack Compose repositories. Point it at a repo, let it run the build once, and get back a 0-100 score, a 0-10 score per category, an actionable top-three fix list, and a full Markdown report with every deduction cited against an official developer.android.com page.
Built for Claude Code, Codex, Cursor, and any agent that loads the Anthropic skill format.
Authored and cross-reviewed with every frontier model — Claude Opus 4.8, GPT-5.5, and Gemini 3.5 Flash — each used to pressure-test the rubric, prompts, and references so the audit holds up regardless of which model ends up running it.
What's new
4.4.0 — 2026-07-07
compose-agent — write-mode acceptance evals. New skills/compose-agent/evals/evals.json: five cases that ask the skill to write Compose and grade the output (cross-phase back-write avoidance, Strong Skipping false leads, snapshot self-invalidation, phase-correct reads, lifecycle-aware Flow collection). bin/ci now validates every eval suite's structure and asserts the compose-agent cases keep covering the 4.3.x authoring rules — so the authoring path can't drift from the audit path. compose-agent → 4.4.0; jetpack-compose-audit stays 4.3.2.
For release detail, see docs/release-notes-4.4.0.md.
4.3.2 — 2026-07-07
Patch. Fixed one Strong Skipping caveat in jetpack-compose-audit/scoring.md that the 4.3.1 sweep missed (its "opt-out path" wording dodged the string match): @NonSkippableComposable opts a composable out of skipping but does not disable lambda memoization — only @DontMemoize / SSM-off does. Both skills → 4.3.2.
4.3.1 — 2026-07-06
compose-agent — authoring guidance for cross-phase back-writes + false leads.
performance.md. New Never Back-Write Across Phases section (layout callbacks writing composition-read state; snapshot-collection mutation in a@Composablebody, with good/bad Kotlin) and Optimizations That Do Nothing (the false leads). Grep triggers extended foronSizeChanged/onGloballyPositioned/onPlacedand snapshot-collection mutation.SKILL.md. New Core Instruction, review-checklist line, and Review Process step 4 names cross-phase back-writes.- Suite-wide Strong Skipping fix. Removed a false-lead carve-out ("...unless the lambda captures an unstable value") that contradicted the official Strong Skipping docs — SSM memoizes lambdas even with unstable captures, so the only real exception is SSM-off /
@DontMemoize. - Why. Closes the drift the 4.3.0 cross-review flagged: the audit caught these after the fact, but the authoring skill stayed silent while writing the code. Now it warns up front.
- Versions.
compose-agent→4.3.1,jetpack-compose-audit→4.3.1.
For release detail, see docs/release-notes-4.3.1.md.
4.3.0 — 2026-07-06
jetpack-compose-audit — cross-phase back-writes + false-lead guard.
- Cross-phase back-write detector (axis 3). Beyond same-body backwards writes, the audit now flags a layout-phase write into state an earlier composition read:
onSizeChanged/onGloballyPositioned/onPlacedwriting state a sibling reads in composition. New heuristic insearch-playbook.md, matching Performance deduction inscoring.md, triage step 7 indiagnostics.md. Findings cite writer and readerfile:line. - Composition-phase self-invalidation (related, not cross-phase). A
SnapshotStateMap/SnapshotStateListmutated inside a@Composablebody that also reads it. Deduped against the same-body backwards-write rule so it never double-counts. - False Leads guard. New Do Not Credit — False Leads table in
scoring.md: plausible recomposition "fixes" that change nothing. The auditor no longer rewards them and will not suggest them inPrioritized Fixes. - Attribution. Axis 3 and the false-lead cases adapted (reworded, re-cited against
developer.android.com) fromchrisbanes/skillscompose-recomposition-performance(Apache-2.0). Axes 1–2 were already covered by this suite. - Versions.
jetpack-compose-audit→4.3.0.compose-agentunchanged at4.2.1.
For release detail, see docs/release-notes-4.3.0.md. Full history: CHANGELOG.md.
4.2.1 — 2026-06-29
compose-agent — Navigation 3 decision table.
- Workflow entry point. A "when to use" decision table at the top of
navigation.md: Nav3 vs Nav2 type-safe vs plain state, argument passing, ViewModel-triggered navigation (the route mutates the back stack — not a screen ViewModel), results via Nav3'sResultEventBus, per-entryViewModelscope,BackHandler, deep links, andListDetailSceneStrategyvsSinglePaneSceneStrategy. Mirrors thepaging.mdpattern. From android/skills#50. API shapes verified againstandroid/nav3-recipes. - Versions.
compose-agent→4.2.1.jetpack-compose-auditunchanged at4.2.0.
4.2.0 — 2026-06-17
Paging 3 in Compose — guardrails for paged lazy lists.
- New reference.
skills/compose-agent/references/paging.md— decision table, golden path, stable keys,LoadState, hard nos. Targets LLM mistakes, notPagingSourceimplementation. - Review wiring. New step #14 in
compose-agent; scoped entrycompose-agent focus on paging. - Audit hooks. Report signals Paging list correctness (Performance) and Paging load-state handling (State) — no fifth score category.
- Plan.
docs/paging-skill-plan.mdincludes the multi-agent validation checklist. - Versions.
compose-agent→4.2.0.jetpack-compose-audit→4.2.0.
For release detail, see docs/release-notes-4.2.0.md. Full history: CHANGELOG.md.
What you get
Run the skill on a Compose repo and you walk away with:
COMPOSE-AUDIT-REPORT.mdwritten at the target root — per-category scoring, evidence file paths, line numbers, and prioritized fixes.- A chat summary that mirrors the report's top three fixes — same file paths, same doc links, same predicted impact. Act on the chat alone if you're short on time.
- Measured stability numbers from the Compose Compiler — module-wide
skippable%, named-onlyskippable%, the unstable-class list, and the per-module Strong Skipping state inferred from compiler version plus explicit flags. - Android Launch UX findings for static Android 12+ splash icons that can render blurry when a
drawable-v31animated-vector wrapper is missing. - A score you can defend. Every deduction carries an official Android Developers URL. No "trust me" findings.
What the audit looks at
Four categories, weighted for an app repo. Each scored 0-10; overall on 0-100.
| Category | Weight | What it covers |
|---|---|---|
| Performance | 35% | Work in composition, lazy-list keys, state-read timing, stability, Strong Skipping, backwards writes, cross-phase back-writes, animation phase correctness, baseline profiles |
| State management | 25% | Hoisting, single source of truth, rememberSaveable, lifecycle-aware collection, observable collections, ViewModel placement, type-safe navigation |
| Side effects | 20% | Effect API choice, keys, stale captures, cleanup, composition-time work, animation driving via LaunchedEffect |
| Composable API quality | 20% | Modifier conventions, parameter order, slot APIs, CompositionLocal usage, Modifier.Node, animationSpec exposure, @Preview coverage, hardcoded strings / magic numbers |
Score bands: 0-3 fail · 4-6 needs work · 7-8 solid · 9-10 excellent.
Adjacent, non-scored coverage includes UI tests/previews, focus/keyboard, KMP/CMP, and Android Launch UX resources. Those findings do not change the 0-100 score, but they can still show up in Critical Findings and Prioritized Fixes when they are concrete and user-visible.
What it catches (and what fixing it buys you)
Concrete smells the rubric targets, with realistic wins:
| Smell | Expected gain after fix |
|---|---|
Unstable or repeatedly recreated params (List, domain models, ArrayList-backed state, listOf(...), fresh UI models) | On older compiler tracks, can lift named-only skippable% and the Performance ceiling. Under Strong Skipping, usually removes instance-recreation churn or expensive equals() work that was still forcing re-runs despite high skippability. |
Lazy-list items(...) without stable key = | Fewer reallocated compositions on reorder, smoother scroll, fewer IllegalArgumentException: Key already used crashes |
| Rapidly-changing state read high in the tree | Recompositions collapse from "per frame, whole screen" to "per frame, single modifier" |
Animated .value piped into Modifier.offset(x.dp) / Modifier.alpha(a) | Moving to Modifier.graphicsLayer { ... } / Modifier.offset { ... } defers per-frame reads to layout/draw — same animation, fraction of the recomposition cost |
File tree
More plugins by @hamen.
View @hamen’s profile@hamenFAQ
compose-skill is a Claude Code plugin with 2 hand-picked skills, indexed on Flowy in the Mobile category. Install it with the command on its page. It includes compose-agent, jetpack-compose-audit. Its skills do not fire on their own yet. Request auto-invocation to have Flowy route them as you prompt. Free and open source.
- What is compose-skill?
- A strict, evidence-based audit skill for Android Jetpack Compose repositories.
- How do I install compose-skill?
- Run these in Claude Code: /plugin marketplace add hamen/compose_skill. Then prompt normally.
- Does compose-skill auto-invoke its skills?
- Not yet. It is indexed on Flowy as a plain plugin. Request auto-invocation on its page and Flowy will route its skills for you as you prompt.
- Is compose-skill free?
- Yes. Flowy is free and open source, with nothing gated. You can read every skill in full before you install.
Is this plugin yours?
Claim it with GitHubSubmit a pluginPromote it