rnett/gradle-mcp/src/main/skills/verifying-compose-ui/SKILL.md
verifying-compose-ui
Verifying Compose UI by rendering components or previews and inspecting the resulting images and state transitions. Activate for visual behavior that requires runtime rendering; use ordinary tests for nonvisual logic.
- Source repository stars
- 56
- Declared platforms
- 0
- Static risk flags
- 0
- Last source update
- 2026-08-05
- Source checked
- 2026-08-05
Decision brief
What it does—and where it fits
Renders Compose UI components and @Preview functions to images for rapid visual verification, enabling state-transition capture and regression detection without a full device or emulator.
Not for
- For rendering issues, environment problems, and common error patterns, see Troubleshooting. If rendering is slow because the build itself is slow, a published Build Scan (via Develocity) can show where the build time go…
Compatibility matrix
Platform support, with evidence labels
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
Inspect first. Install second.
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/rnett/gradle-mcp --skill "src/main/skills/verifying-compose-ui"Inspect the Agent Skill "verifying-compose-ui" from https://github.com/rnett/gradle-mcp/blob/b61fc9339789879e6d03910cb8c2e71085cec4d8/src/main/skills/verifying-compose-ui/SKILL.md at commit b61fc9339789879e6d03910cb8c2e71085cec4d8. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
What the source asks the agent to do
- 01
Positive Triggers (when to activate)
Rendering a specific Composable function or an @Preview to an image.
Rendering a specific Composable function or an @Preview to an image.Capturing state transitions of UI components via a sequence of images.Troubleshooting visual regressions or rendering issues in Compose. - 02
Negative Triggers (when NOT to activate)
Operating a Gradle build (use using-gradle).
Operating a Gradle build (use using-gradle).Modifying build definitions (use authoring-gradle-builds).Probing non-visual project logic (use interacting-with-project-runtime). - 03
Constitution
ALWAYS use this skill for visual verification of Compose components — never attempt to run a full Android emulator or desktop window for visual checks.
ALWAYS use this skill for visual verification of Compose components — never attempt to run a full Android emulator or desktop window for visual checks.ALWAYS specify the exact Composable or @Preview function to render.NEVER render components that require platform-specific APIs unavailable on the JVM (e.g., Android-only system services). - 04
Directives
1. Determine the fully qualified name of the Composable or @Preview function. 2. Identify the module containing the component (e.g., :app, :ui). 3. Determine the source set (main, debug, or preview if a dedicated preview source set exists).
Determine the fully qualified name of the Composable or @Preview function.Identify the module containing the component (e.g., :app, :ui).Determine the source set (main, debug, or preview if a dedicated preview source set exists). - 05
Identifying the Component
1. Determine the fully qualified name of the Composable or @Preview function. 2. Identify the module containing the component (e.g., :app, :ui). 3. Determine the source set (main, debug, or preview if a dedicated preview source set exists).
Determine the fully qualified name of the Composable or @Preview function.Identify the module containing the component (e.g., :app, :ui).Determine the source set (main, debug, or preview if a dedicated preview source set exists).
Permission review
Static risk signals and limitations
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
Why each signal appears
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 91/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 56 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Provenance and original SKILL.md
- Repository
- rnett/gradle-mcp
- Skill path
- src/main/skills/verifying-compose-ui/SKILL.md
- Commit
- b61fc9339789879e6d03910cb8c2e71085cec4d8
- License
- Apache-2.0
- Collected
- 2026-08-05
- Default branch
- main
View the original SKILL.md
Visual Verification of Compose UI Components
Renders Compose UI components and @Preview functions to images for rapid visual verification, enabling state-transition capture and regression detection without a full device or emulator.
Positive Triggers (when to activate)
- Rendering a specific Composable function or an @Preview to an image.
- Capturing state transitions of UI components via a sequence of images.
- Troubleshooting visual regressions or rendering issues in Compose.
Negative Triggers (when NOT to activate)
- Operating a Gradle build (use
using-gradle). - Modifying build definitions (use
authoring-gradle-builds). - Probing non-visual project logic (use
interacting-with-project-runtime).
Constitution
- ALWAYS use this skill for visual verification of Compose components — never attempt to run a full Android emulator or desktop window for visual checks.
- ALWAYS specify the exact Composable or
@Previewfunction to render. - NEVER render components that require platform-specific APIs unavailable on the JVM (e.g., Android-only system services).
- PREFER desktop Compose rendering over Android rendering when the component is platform-agnostic.
Directives
Identifying the Component
- Determine the fully qualified name of the Composable or
@Previewfunction. - Identify the module containing the component (e.g.,
:app,:ui). - Determine the source set (
main,debug, orpreviewif a dedicated preview source set exists).
Starting a Rendering Session
Call kotlin_repl(command="start", ...) with the appropriate project path and source set, plus Compose-specific dependencies. For general session parameters, lifecycle management, and environment troubleshooting, see REPL Session Setup.
{
"command": "start",
"projectPath": ":ui",
"sourceSet": "main",
"additionalDependencies": [
"org.jetbrains.compose.ui:ui-tooling:1.6.0",
"org.jetbrains.compose.desktop:desktop:1.6.0"
]
}
Rendering to Image
Use the REPL to execute Compose rendering code:
import androidx.compose.ui.unit.*
// Render a composable to a BufferedImage
val image = renderComposable(width = 400.dp, height = 300.dp) {
MyComponent(state = rememberState())
}
// Display the result
displayImage(image)
Capturing State Transitions
Render multiple frames to capture state changes:
// Frame 1: Initial state
val frame1 = renderComposable(width = 400.dp, height = 300.dp) {
MyComponent(state = initialState)
}
displayImage(frame1)
// Frame 2: After interaction
val frame2 = renderComposable(width = 400.dp, height = 300.dp) {
MyComponent(state = afterClickState)
}
displayImage(frame2)
Rendering Existing @Preview Functions
If the component already has an @Preview annotation, render it directly:
val image = renderPreview("com.example.MyPreviewFunction")
displayImage(image)
Troubleshooting
For rendering issues, environment problems, and common error patterns, see Troubleshooting. If rendering is slow because the build itself is slow, a published Build Scan (via Develocity) can show where the build time goes so you can address the underlying cause; if the scan shows the same unchanged work recomputed on every re-render, Build Cache reuses matching task outputs across runs. Develocity publishes an llms.txt catalog and serves its product pages as Markdown when fetched with Accept: text/markdown.
Examples
View a simple Composable
{
"command": "start",
"projectPath": ":app",
"sourceSet": "main"
}
// Then run rendering code:
{
"command": "run",
"code": "val img = renderComposable(width = 200.dp, height = 100.dp) { Text(\"Hello\") }; displayImage(img)"
}
// Then stop:
{
"command": "stop"
}
View an existing @Preview
{
"command": "start",
"projectPath": ":ui",
"sourceSet": "debug"
}
// Then:
{
"command": "run",
"code": "val img = renderPreview(\"com.example.ui.MyComponentPreview\"); displayImage(img)"
}
Capture state transitions
{
"command": "run",
"code": "val f1 = renderComposable(200.dp, 100.dp) { ToggleButton(checked = false) }; displayImage(f1); val f2 = renderComposable(200.dp, 100.dp) { ToggleButton(checked = true) }; displayImage(f2)"
}
Alternatives
Compare before choosing
coreyhaines31/marketingskills
ab-testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
coreyhaines31/marketingskills
churn-prevention
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o
prowler-cloud/prowler
postgresql-indexing
PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing index usage statistics, reindexing, dropping indexes, or working with partitioned table indexes. Also trigger when discussing index strategies, partial indexes, or index maintenance
JasonColapietro/suede-creator-skills
suede-ab-testing
Suede-owned experimentation discipline for hypotheses, sample sizing, test duration, significance, and repeatable experiment programs. Use when comparing variants, deciding whether a result is reliable, or building an experiment backlog and cadence. NOT FOR: analytics instrumentation (use suede-analytics), post-click conversion diagnosis (use suede-site-alchemy), or writing the variant copy itself (use suede-copy).