cmp-inspectlisted
Install: claude install-skill kvdm-co-pilot/create-cmp
# cmp-inspect — read a live Compose UI as structured design data
Your job: answer "what did this Compose screen actually render, and does it match the design system?"
by inspecting **structured JSON** — hierarchy + geometry + resolved design tokens — **never a
screenshot**. Screenshots burn tokens, degrade to pixel-guessing for colours/spacing, and can't read
theme tokens at all. This skill drives the `cmp-inspector` MCP over a fixed JSON tree contract.
## Before any inspector call: confirm the capability (fail loud)
The cmp-inspector MCP tools are a capability, not a given. Before your first call, confirm
they resolve (ToolSearch for "cmp-inspector"). If no tools match, **STOP — do not fall back
to screenshots, raw adb, or manual Gradle silently.** Diagnose in order and REPORT to the human:
1. **Plugin enabled?** Check `enabledPlugins` in `~/.claude/settings.json` (or the project's
`.claude/settings.json`).
2. **Session older than the plugin's enablement?** MCP servers attach at session START — a
session born without the plugin never gains its tools, and no amount of in-session
retrying will surface them. The fix is restarting the session.
3. **Plugin copy stale or server broken?** Run cmp-doctor's inspector-MCP check group.
Only after reporting may the documented degraded path be used — and the report must name what
is lost: structured trees and change proofs replaced by pixels.
> **No-pixels rule.** Do not screenshot the app to reason about layout, colour, o