What they did
Ashwin, an Android engineer, built verify-ui so a coding agent could see the Jetpack Compose screens it writes. It has two halves: a Gradle plugin that renders previews on the JVM with Robolectric (no emulator), including 2x font, dark theme and RTL variants, and checks the layout for clipped text, touch targets under 48dp, missing accessibility labels, low contrast and broken mirroring; and a Claude Code skill. Running /ui-verify on a composable has Claude Code read its parameters, generate previews for meaningful states, run the render, read the JSON report and fix what it finds, then run validation again until it is clean.
How it went
On a sample app with 11 planted bugs the loop flagged 10 with no false positives; the miss, a Switch with a null callback in a clickable row, needed a visual checklist added to the skill. The first evaluation was invalid because comments in the code gave the agent the answers. Claude Code once turned a Column into a LazyColumn to fix a clipped row, so the skill now asks for minimal, local fixes. On a production app it rendered first time but hit a manifest merge failure and missed text clipped by maxLines, which became a new rule in version 0.2.1.
Worth knowing
It is an early prototype. It cannot reach state held inside a composable with remember, covers about six control states per screen, and judges measurable faults only, not whether a design looks right. Projects without a Compose BOM must pin Compose test dependency versions themselves.