Frontend Implementation

Overview

Implement frontend changes with existing-stack alignment, minimal DOM/CSS, clear layout ownership, and explicit verification. Use this after repository context is clear; route browser evidence to ops-browser and real desktop-window proof to ops-client.

Workflow

1. Read repo guidance first: root AGENTS.md, nearest subproject AGENTS.md, AGENT.md, or chat-supplied rules.
2. Identify the target page, route, screen, component, framework, UI type, visual source, and required states before editing.
3. Inspect only the target page, route, component, service, hook, style, shared UI, and layout owner files needed for the requested change.
4. Classify the existing UI system and layout model: component library, utility/CSS strategy, shell/content/page boundaries, panels, and scroll regions.
5. Preserve typography, spacing, density, routing, state, API contracts, accessibility, and visual system unless the task explicitly asks to change them.
6. Implement with the smallest component, DOM, CSS, and ownership surface that matches existing patterns.
7. Remove stale wrappers, duplicate declarations, late overrides, and temporary layout patches made obsolete by the change.
8. Run matching project-defined checks, then use ops-browser or ops-client when runtime UI evidence is required.

Modes