What problem does it solve? Running and iteratively testing the T3 Code web app locally is error-prone: dev servers die between turns, one-time pairing tokens get consumed accidentally, and shared state directories get corrupted. This Skill manages the full lifecycle of isolated T3 test environments so browser-based UI testing stays reproducible. ## Core Features & Use Cases - Isolated environment launch: Start the full web stack with worktree-local or temporary base directories, keeping shared state untouched. - First-try browser authentication: Handle one-time pairing URLs correctly, and recover consumed or expired tokens via the auth CLI. - SQLite inspection and seeding: Query or seed projection tables in state.sqlite for UI fixtures using a backup-protected helper script. - Use Case: An agent needs to verify a UI change with a human reviewer. It starts a dev server in a worktree-local .t3 directory, authenticates the controlled browser with a fresh pairing token, keeps the environment alive across turns, and only tears down when the reviewer confirms completion. ## Quick Start Use the test-t3-app skill to launch an isolated T3 dev environment and authenticate the browser so we can iterate on the web UI.
