Polish

Put a working feature in front of the user and turn their live observations into focused UX fixes on the running page. Two ways to collect those observations: traditional, where the user types what could be better; and live, where they talk and draw on the page while a voice interviewer turns speech into units and you act on them at checkpoints.

Done: the user ends the polish loop, every requested fix is reflected in the live feature or reported as blocked, and the in-scope changes are saved in local commit(s). A live session also ends with a residual list of the units that were not applied and the path of its session log. A server or checkout blocker also ends the run when it is reported with the evidence needed to resume.

Boundaries: the user drives what to inspect and change; do not invent an autonomous checklist or expand into general QA. Never work on the repository's default branch. This workflow may edit and locally commit the requested polish, and in live mode the disclosed riffrec setup commit, but it never pushes or opens a PR.

Run

1. Ask live or traditional. Ask once, before any server starts. Include this disclosure with the question: live mode needs an OpenAI key in the environment, runs a voice interviewer in the page that hears the user, is told what they click and draw on, and looks at their screen when they point at something or ask it to, streams the session to a local endpoint this skill runs, and, when riffrec is not yet in the app, adds the riffrec dependency and a provider mount as a setup commit on the current branch that stays after the session. Traditional continues with steps 2–5 unchanged. Live: read references/live-start.md; it owns preconditions, install, the endpoint, and the URL handoff, applies the workspace and server rules of references/run.md itself, then routes to references/live-loop.md for the session and its close. Steps 2–5 do not run for a live session.
2. Get the live page ready. Read references/run.md before resolving the requested ref or starting anything. It owns existing-worktree safety, dev-server discovery, the bundled-script calls, reachability, and the browser handoff.
3. Wait for observations. Tell the user where the server is running and ask what could be better. Do not start a review pass while they browse.
4. Iterate. For each requested change, inspect only as needed, edit the in-scope surface, and let hot reload update the page. When the user asks you to inspect the result, use a browser capability available in the active harness; if none exists, ask them to describe what they see.
5. Close locally. When the user says they are done, invoke ce-commit for the polish changes, then report the commit(s), the still-running server URL, and any residual blocker.