Prevue plugin
A plugin that shows the agent and you Compose Previews in a browser, redrawn a second after each save, with no Android Studio.
- 100 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- The plugin starts a local daemon and Gradle, and on first setup the agent may install a JDK and tools under `~/.prevue`.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/prevueDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The plugin starts a local daemon and Gradle, and on first setup the agent may install a JDK and tools under `~/.prevue`.
This is third-party code. Review the repository files before installing.
What it does
Prevue starts a lightweight daemon that renders the `@Preview` functions of a Jetpack Compose or Compose Multiplatform file and hands the picture to the agent. The agent edits, saves, gets a new render about a second later, compares it with a Figma frame or screenshot and repeats without you. You open the same preview in a browser and accept the result. Clicking an element gives the agent a `file#Lline` path, so a request to tighten the padding is unambiguous. There is an interactive mode with touches, device and screen-size switching, and a separate daemon for each git worktree. By the author's measurement the daemon takes about 1.4 GB against 8.1 GB for Android Studio.
Who it is for. Android developers on Compose who give screen layout to an agent and are tired of acting as its eyes after every edit.
Good fit when
- An agent lays out a screen from a design and has to compare the result itself.
- Three agents work in three worktrees and three Android Studios do not fit in memory.
- A problem spot is shown on the preview with a click instead of words.
- A screen is checked on several devices, foldables included, without an emulator.
Not a fit when
- The module is pure JVM or KMP without an Android target: such builds are not supported.
- You need release variants, member previews inside a class or files with `expect` and `actual`.
- A preview depends on a DI container or `AndroidView`: Prevue flags them with a `DI` or `ANDROID_VIEW` failure.
Example request
Show the Previews in ForYouScreen.kt and match the header to the attached screenshot. Compare each render yourself until it matches closely.Limitations
Android modules (app and library) and KMP modules with an Android target on Gradle work, and Amper is not supported. JDK 21 or newer (the JDK from a recent Android Studio will do) and the Android SDK are required, and the README paths are for macOS. The agent performs first-time setup and puts tools under `~/.prevue`, and Gradle runs once per module. After saving a file with `expect` and `actual` the picture stays old until a Gradle build. The speed figures come from one project on one Mac.
How to disable. Stop the daemons with `prevue stop --all`. For Claude Code remove the plugin with `claude plugin uninstall prevue@prevue`, and for Codex disable it in `/plugins`. The `~/.prevue` toolchain directory is deleted by hand.
FAQ
How do I install the plugin?
For Claude Code: `claude plugin marketplace add https://github.com/kakao/prevue.git`, then `claude plugin install prevue@prevue`. For Codex: `codex plugin marketplace add` with the same URL and `codex plugin add prevue@prevue`.
How do I invoke the skill?
With `/prevue` in Claude Code or `$prevue:prevue` in Codex, then name a file such as `Show the Previews in ForYouScreen.kt`. Calling it directly is more reliable than waiting for auto-trigger.
What about Compose Multiplatform?
It works the same: name a file in `commonMain`. Previews are drawn from the module's Android compilation, as Android Studio does.
Does Prevue change project files?
No. Build files, plugins and tasks stay as they are, and no files are added to the project.
How do I update the plugin?
First `claude plugin marketplace update prevue`, then `claude plugin update prevue@prevue`. Without the first step the plugin reports it is already current.
Discussion
No questions or reviews yet.
Related
PluginsLets an agent render Jetpack Compose previews to PNG and see its UI edits: plugin, CLI, VS Code extension and MCP.
MCP server and CLI that renders SwiftUI previews to PNG on chosen devices, so an agent can check a screen after editing it
Two Jetpack Compose skills: a repository audit scored 0–100 from compiler data and a coding helper that warns as you write.
A skill for Jetpack Compose and Compose Multiplatform: the agent writes UI from references and checks it against androidx source
A set of 26 skills on Jetpack Compose performance, from a measured audit to Baseline Profiles and R8
A Callstack plugin that shows simulators and devices beside the agent chat and lets it control the mobile app.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Prevue (this card) | no | 100 | |
| Compose Agent Skill | no | 602 | reference material and rules for writing Compose code; here preview rendering and an image for the agent to check |
| Compose Skill Suite | no | 379 | a repository audit and a coding helper; here a live view of the layout result |
README in short
The README shows the agent-edits, Prevue-renders loop with measurements against Android Studio, then covers a two-command install, updating, `prevue` commands and a table of supported setups.