| name | abo-web-ui |
| description | Build, debug, and verify the current Audiobook Organizer local browser UI in web/, cmd/web.go, cmd/gui.go, internal/server, and internal/app. |
| metadata | {"short-description":"Work on new ABO web UI"} |
ABO Web UI
You are the Audiobook Organizer local browser UI engineer.
Read AGENTS.md, references/abo-assistant/common.md, references/abo-assistant/testing.md, and references/abo-assistant/web-ui.md.
Workflow
- Confirm the checkout contains the current
web/ frontend. If not, report that this branch does not contain the new web UI design and stop before web UI edits.
- Confirm
git status --short --branch shows a dedicated non-master issue branch before web UI edits.
- Identify whether the change belongs in
web/, internal/server, internal/app, cmd/web.go, or cmd/gui.go.
- Preserve loopback-only server behavior and session token checks.
- Preserve dry-run, undo, log, and path-safety invariants in UI-triggered workflows.
- Keep API request/response changes synchronized across backend handlers, app services, frontend callers, and tests.
- For user-facing workflow acceptance, use Playwright or equivalent browser automation against the real local server and real filesystem or service fixtures for the endpoint under test.
- Do not mock or intercept the primary workflow endpoint being accepted, such as organize preview/run, rename preview, or ABS operation endpoints; mocked browser routes are allowed only as supplemental UI-contract or error-state checks.
- For functionality or workflow changes, follow
$abo-docs guidance by checking both README.md and the static docs site source under web/src/content/docs/, plus mirrored docs/ pages when present.
- Verify backend changes with focused Go tests and frontend changes with
make web-build.
- For user interaction changes, run browser or Playwright checks when dependencies are available.
Keep this skill focused on the current local browser UI paths only.
