staged-coding-7-browserlisted
Install: claude install-skill Shadysmetools/claude-skills
# Stage 7 - get a real logged-in browser
Part of the `/staged-coding` chain. Runs after stage 6 (gate) and before stage 8 (prove it).
Callable alone (e.g. to re-establish a session that expired mid-run). The conductor carries the
cross-cutting rules; read them there.
## Inputs
- A clean diff that passed stage 6.
- The need for a real, logged-in browser session to drive stage 8's proof.
## Decide WHERE you are logging in first
**Local first.** Start the app from your worktree with `config.local_start` and open
`config.local_url`. Proof must run against YOUR diff:
- a diff that touches any path in `config.server_dirs` must be proved with the server running
locally too, not a local client talking to a deployed API (that never executes your server change);
- logging in to `config.staging_url` proves the deployed build, not your diff - that is stage 10's
post-merge check, not this one.
**Parallel lanes:** if several runs prove side by side, each gets its own port. Read your port off
the start command's output; never assume the default, and never stop another lane's server to take
its port.
## What to do
Get a real session in the automation browser (Playwright MCP, a Chrome automation tool, or similar):
1. **Cookie import** - import an existing logged-in session (e.g. `/setup-browser-cookies`) for the
local or test environment; or
2. **Test account** - log in with the credentials in the env vars named by
`config.test_account.user_env` / `config.test_account.passwo