compose-ai-tools

See your Compose UI without opening Android Studio.

compose-ai-tools renders your @Preview composables to PNG from the command line — so your AI coding agent can actually look at the screen it just changed, and so can you. Works with Jetpack Compose (Android, via Robolectric) and Compose Multiplatform Desktop (via ImageComposeScene).

That's the whole idea. Everything else on this page is optional.

📖 Documentation · Install · Reference

Get started

Pick the one that fits you.

🤖 With an AI coding agent

Install the agent skills with the skills CLI, then run the bundled stub once to install the compose-preview CLI:

npx skills add yschimke/skills --global --yes --skill compose-preview --skill compose-ui-builder
~/.agents/skills/compose-preview/scripts/compose-preview --version   # first run installs the CLI and puts it on PATH

Open a new terminal afterwards. To update: compose-preview update (CLI) and npx skills update (skills).

That installs compose-preview and compose-ui-builder. The other skills (compose-preview-review, compose-preview-ci, compose-preview-design-board, compose-design-catalog, figma-catalog-import, design-parity-review) are opt-in: add another --skill <name>; the curl installer takes --skills a,b or --all-skills.

No Node, or want the CLI and skills in one step? Use the installer instead (add -s -- --no-modify-path to leave your shell startup files alone):

curl -fsSL https://raw.githubusercontent.com/yschimke/skills/main/scripts/install.sh | bash

Then just ask your agent to preview a composable. The compose-preview skill is the playbook — it tells the agent how to render, iterate, and check its own work. You don't have to learn the commands; the agent reads the skill. (If your agent can fetch URLs but not run commands, point it straight at the SKILL.md — it bootstraps the CLI itself.)

For agent setup, follow the Compose Agent Plugins quick start. The repository is now yschimke/compose-agent-plugins; existing installs using the old marketplace name should follow its migration steps.

• compose-skills supplies the canonical workflows from yschimke/skills.
• compose-preview supplies local MCP wiring and hooks. Local rendering needs the CLI on PATH, Java 17 or newer, and compose-preview mcp install run once from each Compose project's root.
• compose-catalogs connects to hosted catalogs and the UI Builder without a local toolchain.

The quick start has the commands for Antigravity, Claude Code, Codex and OpenCode. Use one copy of each skill bundle and MCP registration; the single marketplace also installs compose-skills, so a separate skills marketplace is unnecessary.

🧩 In VS Code (or Cursor / Windsurf / VSCodium)

Open the Extensions view (⇧⌘X / Ctrl+Shift+X), search Compose Preview, click Install. It renders previews inline and needs no project changes. (Marketplace · Open VSX)

⌨️ From the command line

Install the CLI (same one-liner as above), then point it at any Compose project — no build edits required:

compose-preview render    # render every @Preview to PNG
compose-preview browse    # open the streamlined component browser

browse includes every preview-bearing module in one catalog. It automatically builds and uses a compatible CMP Wasm browser app (including the common :shared:ui → :webApp split), while JVM/Android-dependent components retain their baked preview and source-code experience. Use --module :app only when you deliberately want to narrow the catalog.

The CLI injects itself into your build at runtime, so projects that already apply com.android.application / com.android.library / org.jetbrains.compose just work.

Prefer a version-pinned Gradle plugin? It's on Maven Central (no auth, no token). See the Install page for that, CI recipes, and the full requirements (Java 17+, Gradle 8.13+, AGP 8.13.0+, Kotlin 2.0.21+).

What else it can do

None of this is required to get value from the tool — it's there when you want more than a PNG.

• Data products — alongside each PNG the renderer can emit structured data: accessibility findings, layout trees, theme tokens, recomposition heat maps, drawn text, resource captures, and more. One page per product.
• Agents & MCP — a push-based, token-frugal agent loop over Compose UI: target by semantic ref, observe semantics instead of pixels, diff renders, turn recordings into tests. The aria-snapshot story for Compose. The same native MCP process can optionally connect agents to a concurrent preview-server UI-builder session; see the MCP design reference.
• **[Daem