iterating-with-ai-and-mcp

Drives Compose HotSwan MCP tools to edit, reload, screenshot, and iterate Android UI.

1|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/citytexi/team-yg-pesonal-agent --skill iterating-with-ai-and-mcp-citytexi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: iterating-with-ai-and-mcp
Source: https://github.com/citytexi/team-yg-pesonal-agent/tree/main/.claude/skills/iterating-with-ai-and-mcp
Command: npx skills add https://github.com/citytexi/team-yg-pesonal-agent --skill iterating-with-ai-and-mcp-citytexi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents editing Jetpack Compose UI code normally cannot see whether their changes worked, forcing a human to verify every iteration. This Skill gives the agent a closed loop: edit a Kotlin file, trigger a hot reload, capture a device screenshot, and evaluate the result against the design intent without human involvement. ## Core Features & Use Cases - Canonical agent loop: Status check, snapshot session, edit, reload with tier reporting, screenshot evaluation, and loop exit criteria. - Seven verbatim MCP tools: hotswan_get_status, hotswan_reload, hotswan_take_screenshot, hotswan_start_snapshot, hotswan_stop_snapshot, hotswan_select_variant, hotswan_build_and_install. - Snapshot-based rollback: Record every iteration and roll the source back to the best variant when the final state regresses. - Use Case: A developer tells Claude Code to tune a Compose screen until it matches a mockup. The agent edits the composable, reloads in seconds, screenshots the device, compares against the mock, and iterates autonomously. ## Quick Start Ask the agent to tune this Compose screen until it matches the attached mockup using the HotSwan MCP tools, starting with a status check and a snapshot session.

Frequently Asked Questions about iterating-with-ai-and-mcp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I let an AI agent iterate on Jetpack Compose UI automatically?▼

Connect an MCP-capable client like Claude Code or Cursor to the HotSwan plugin's HTTP MCP server. The agent then runs a loop: edit the Kotlin file, call hotswan_reload, call hotswan_take_screenshot, and evaluate the result against the design intent.

What MCP tools does Compose HotSwan expose?▼

HotSwan exposes exactly seven tools: hotswan_get_status, hotswan_reload, hotswan_take_screenshot, hotswan_start_snapshot, hotswan_stop_snapshot, hotswan_select_variant, and hotswan_build_and_install. Agents must not invent additional tool names.

Can Claude Code or Cursor take screenshots of an Android device?▼

Yes, through the hotswan_take_screenshot MCP tool, which captures the current device screen and returns image bytes the agent can inspect. This lets the agent visually verify its own edits instead of guessing whether a change worked.

Why does hotswan_reload do nothing when the agent calls it?▼

The reload silently no-ops if the app is not running or the watcher is not in WATCHING state. Always call hotswan_get_status first and confirm watcher equals WATCHING before issuing edits or reloads.

When should I use hotswan_build_and_install instead of hotswan_reload?▼

Use hotswan_build_and_install only for schema changes such as adding a parameter, changing a constructor, or adding a new resource ID, which hot reload cannot handle. It is a fallback, not a default, since full installs destroy the speed advantage of the hot reload loop.

How do I roll back to an earlier UI iteration with HotSwan?▼

Wrap the iteration loop in hotswan_start_snapshot and hotswan_stop_snapshot so every reload auto-captures a screenshot and source state. Then call hotswan_select_variant to roll the source code back to the preferred intermediate variant.