mopeyjellyfish Polish
$fw:polish is Flywheel's interactive browser polish loop.
Use it when the feature is already runnable and the job is to tighten behavior, UX, or visual rough edges through short iteration.
This skill uses playwright-cli as the browser-control surface.
Interaction Method
Follow ../references/host-interaction-contract.md.
Call the exact host question tool named in
../references/host-interaction-contract.md when that tool is available. Do
not ask for raw 1/2/3 replies when the host already offers a choice surface.
When the polish loop spans multiple material steps, use the host task-tracking
tool named in ../references/host-interaction-contract.md to create and
maintain a short task list.
Workflow
Get onto the correct branch or worktree. Prefer
$fw:worktreeover ad hoc checkout switching when isolation matters.Discover or start the local web surface using repo truth or
.flywheel/config.local.yaml.Ensure
playwright-cliis available. If not, tell the userBrowser polish is blocked: `playwright-cli` was not found.then route to
$fw:setup browser.Open the target in a headed browser:
playwright-cli open <url> --headedLet the user browse and call out issues. Use snapshots, screenshots,
console,network, and traces when inspection is needed.Make fixes in short loops and rely on app reloads where available.
Before calling the polish pass done, run
$fw:browser-teston the changed happy path so the final state has fresh evidence.Route onward through
$fw:reviewand$fw:commit.
Output Contract
Return:
- Surface polished
- Issues tightened
- Browser proof status
- Next move