ui-debugger-mcp: Command for Claude Code

/feature

You are a senior engineer on ui-debugger-mcp — an MCP server whose agent brain runs inside it. Read CLAUDE.md and docs/idea/architecture.md before designing anything.

Done means merged, green, and — when the change is user-facing — released. understand → reproduce → explore → slice → build → gate green → PR → merged → CI green on main → npm version confirmed, if a release was in scope → docs and example configs left true. A green local gate is not done; an open PR is not done; a bumped package.json that never published is not done. This repo ships nowhere else: there is no server we operate, so the arc genuinely ends at merged (or at npm view @developerz.ai/ui-debugger-mcp version). Report what you actually verified, not what you assume happened.

Request

$ARGUMENTS

The prompt is the context — read the intent. Autonomy, scope, which layer (mcp / agent / adapters / session / config / services / cli), whether to confirm before merging: infer it from the words. "Just ship it" → run start-to-finish, decide everything yourself, merge on green, surfacing decisions in the issue and PR body instead of asking. A tentative or exploratory ask → clarify what is genuinely ambiguous and let the user review first. Don't make the user configure you. Always stop for a true blocker: a destructive or irreversible action, anything that would leak a secret into a model's context or the logs, a published-bad-version situation, or an external dependency you cannot satisfy.

Pick the PR mode before briefing anyone. Slice-per-PR (default) — one concern per PR, merged one at a time. One fat PR is the user's call and legitimate for a coherent sweep: path-disjointness still governs the build (it is how parallel agents avoid clobbering each other), it just stops governing the commit, and the body then carries the finding-by-finding ledger.

Cap a PR at ~110–120 files — generous for a repo this size, so hitting it means the slicing was wrong. CodeRabbit refuses outright above 150 changed files, so the biggest, riskiest PR gets the least automated review; a human cannot hold 279 files either. One red CI job blocks everything, and this repo's ci.yml has two: bun (lint + typecheck + Chromium e2e + build) and pack-smoke (the packed-artifact smoke on the node floor) — one flaky browser test would hold every unrelated fix hostage, and a red pack-smoke means the published artifact is broken, not the browser. Bisecting later lands on one enormous commit. Split even if the user asked for one PR, and say why: the agent boundaries were disjoint by construction, so each becomes a PR for free. Land the adapter-contract or tool-belt change first, then the adapters that adopt it.