Menu
Test the IronClaw web UI using the Claude for Chrome browser extension.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | web-ui-test |
| version | 0.1.0 |
| description | Test the IronClaw web UI using the Claude for Chrome browser extension. |
| activation | {"keywords":["test web ui","test the ui","browser test","chrome test","test skills tab","test chat","web gateway test"],"patterns":["test.*web.*ui","test.*browser","chrome.*extension.*test"]} |
Use this skill when manually testing the IronClaw web gateway UI via the Claude for Chrome browser extension.
GATEWAY_ENABLED=truehttp://127.0.0.1:3000/) and auth tokenCLI_ENABLED=false GATEWAY_AUTH_TOKEN=<your-token> cargo run
Wait for "Agent ironclaw ready and listening" in the logs before proceeding.
http://127.0.0.1:3000/?token=<token>markdown-viewerhttps://wry-manatee-359.convex.site/api/v1/download?slug=markdown-viewerAfter testing, remove any test-installed skills:
rm -rf ~/.ironclaw/installed_skills/<skill-name>
Stop the server with Ctrl+C or by killing the process.
clawhub.ai is behind Vercel which blocks non-browser TLS fingerprints; the backend uses wry-manatee-359.convex.site directlyconfirm() dialog for install may block browser automation; override with window.confirm = () => true in the console firstUse when adding or reviewing tests for Reborn behavior — choosing a test tier, covering a bug fix, testing model/tool-choice behavior, touching tests/integration or tests/fixtures/llm_traces, or when a test needs Postgres, Docker, or a live LLM.
Navigate building a user-facing feature in the Reborn stack (a capability that crosses product_workflow → composition → webui_v2 → runtime/serve → frontend). Use when planning or implementing any new Reborn settings page, endpoint, facade method, or runtime-backed capability — especially before writing code, to avoid rebuilding what already exists and to wire it in one pass instead of layer-by-layer.
Use when asked to "review the open PRs", review a batch or stack of pull requests, or run a recurring PR-review pass on a repo — especially with many PRs, stacked branches, conflicts, or security-sensitive changes. Covers grouping, fan-out to review subagents, verdict synthesis, and posting.
Generate or update the IronClaw architecture overview video using Remotion. Use when asked to update, regenerate, or modify the architecture video, add/remove scenes, or reflect codebase changes in the video.
Use when writing or reviewing a change in crates/ that adds a trait, a crate, a dependency edge, a re-export, or code in ironclaw_reborn_composition — or when deciding whether an abstraction, layer, or crate boundary is justified in the IronClaw Reborn stack.
Use when starting work in the IronClaw repo, deciding where a feature/fix/prompt/doc belongs, tracing how a request flows, looking up which crate owns a subsystem, or when repo docs, the knowledge graph, or component names seem stale, missing, or contradictory.