@subtext
Drive a hosted browser, capture before/after proof, and leave reviewer-facing evidence against your running app
Comment MCP tools for agent-user collaboration. Use when reviewing sessions or live pages to leave observations, read user feedback, reply, and resolve.
Proof document MCP tools for creating, updating, and closing agent work documentation. Use when tracking a bug fix, UX review, or changeset to produce a permanent, evidence-backed record.
Agent explores the user's site via hosted broswer (live), leaving comments as it goes. Accepts a user-described flow or explores organically. Capped at ~10 interactions across 2-3 pages. Returns session URL, trace URL, and metrics.
Live browser MCP tools for driving a hosted browser — connections, views, interactions, console, network, and tunnel. Use when reproducing flows, taking screenshots, or interacting with a running app.
Interactive first-run onboarding for new Subtext users. Connects to the user's local dev server, proves a small change with before/after evidence in a watchable trace, then bootstraps a starter sightmap from what was learned.
You MUST use this skill when implementing, fixing, or refactoring code. Captures evidence artifacts (screenshots, network traces, code diffs, trace session links) into a proof document as you work.
Short recipe to create sightmap definitions for a project from scratch.
Use when opening a hosted browser connection against a localhost or local dev server URL. Sets up a reverse tunnel so the hosted browser can reach the user's local server.
Foundation for the Subtext Verify skills — verify-specific MCP tool prefixes, sightmap upload, and the tunnel server. Read this when a Verify skill lists it in PREREQUISITE.
Use when starting any conversation that may involve rendered UI, driving a running app, or producing reviewer-facing evidence (screenshots, viewer links, code diffs). Establishes how the Subtext Verify skills compose and when to invoke them before any response or action.