dev-frontendlisted

# Frontend Implementation ## Overview Implement frontend changes with existing-stack alignment, minimal DOM/CSS, clear layout ownership, and explicit verification. Detect the actual framework before applying framework-specific rules. Use `ops-browser` for web runtime evidence and `ops-client` for real desktop-window proof. ## Workflow 1. Read effective repository guidance first, including `AGENTS.md`, `CLAUDE.md`, and host-provided instructions when present. 2. Identify the frontend project class, app boundary, package manager, runtime pin, script contract, directory/naming standard, and documented exceptions. 3. Identify the target page, route, screen, component, framework, UI type, visual source, and required states before editing. Load `references/specification-authorities.md`, resolve applicable product and UI authorities by meaning rather than filename, and read only the shared facts/indexes and target slice contracts needed for this change. 4. Confirm acceptance criteria, non-goals, affected contracts/files, and validation seams from usable approved requirements. Consume existing contracts directly; hand unresolved product decisions to `product-spec` or required selected-source/shared visual decisions to `ui-spec` without treating either Skill as a file detector. For complex work without a usable specification, use the host's built-in planning and effective repository instructions before editing. 5. Consume a current `repo-map` inventory or perform a targeted search