Claude Skill MartBrowse skillsQuick linesLearn by videoTerminal guideWhat is a Skill?
 
← Back to list

Compose Architecture Contract

Architecture guardrails for Jetpack Compose / Compose Multiplatform apps: module graph, MVI contract, error tiers and state ownership.

Dev & CodingAdvanced★ 300⑂ 25AI score 9/10Last updated: Oct 2, 2026

What it does

Defines the house contract Claude must follow when writing or reviewing Compose / Compose Multiplatform code.

  • Module graph: one-way :feature:* → :data:*/:core:* dependencies; no feature-to-feature imports
  • MVI contract: every ViewModel extends BaseViewModel<Action, State, Effect>; Contract.kt holds exactly UiState, UiAction, UiEffect
  • Error tiers: cold-load failure is inline with Retry, refresh failure is a popup, silent only for named background polls
  • State ownership: one owner per piece of state, no rememberSaveable mirrors, drafts live in SavedStateHandle
  • DI & navigation: Koin annotations flavour, Navigation 3 only with per-feature sealed NavKey
  • Verification gates: run-checks script exits 0, modules compile, JVM tests pass, banned patterns self-audited

A "when NOT to use" table routes screen work to compose-feature, composables to compose-ui, repositories to compose-data, and so on.

Who it's for

  • Teams running multi-module Compose or KMP apps
  • Tech leads who want AI-generated code to stop drifting into a new pattern every session
  • Projects already standardised on MVI + Koin + Navigation 3

Examples

  1. Adding a ViewModel — you get a single onAction entry point and all async work routed through launchGuarded(onError = …).
  2. Asking for a PR review — cross-feature imports, hand-rolled try/catch, Result wrappers and mixed error tiers come back as blocking items.
  3. Asking to "drop one MVI screen into this MVVM feature" — the skill declines in one plain sentence, builds in the feature's existing pattern, and proposes migration separately.

· · · Install guide · · ·

Try it now, no install

Paste this into Claude to use the skill without installing anything.

Read the instructions in this file and follow them to help me:
https://raw.githubusercontent.com/Meet-Miyani/compose-skill/HEAD/skills/compose-architecture/SKILL.md

What I want: (describe your task here)

If Claude can't open the link, open it yourself and paste the contents instead.

↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.

Install in the Claude app (no terminal)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
↓ Download ZIP
Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on Claude Skill Mart.
Copy the skills/compose-architecture folder from the GitHub repo Meet-Miyani/compose-skill into my ~/.claude/skills/compose-architecture/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/Meet-Miyani/compose-skill.git /tmp/compose-skill && mkdir -p ~/.claude/skills && cp -r /tmp/compose-skill/skills/* ~/.claude/skills/

⚠ This is a third-party skill. Check the source repository before installing.

  1. Open a terminal.
  2. Clone the repo: git clone https://github.com/Meet-Miyani/compose-skill.git
  3. Create the skills folder: mkdir -p ~/.claude/skills
  4. Copy the skills across: cp -r compose-skill/skills/* ~/.claude/skills/ — copy all of them, since this skill expects the compose entry point plus siblings like compose-feature and compose-ui.
  5. Confirm the references/ and templates/core/ folders came along.
  6. Restart Claude Code and try: "Review this ViewModel against the Compose architecture contract."
View source on GitHub ↗License: MIT