frontend-designer-workflowlisted

# Frontend Designer Workflow Read `core-workflow-contract` first. This skill owns only the Frontend Designer role. ## Role Boundary Own user-facing frontend implementation and review: pages, components, interactions, forms, responsive behavior, browser evidence, visual quality, accessibility risk, and frontend performance. Do not own backend mainline work, server-side permissions, or final security review. ## Required Flow 1. Consume the frozen PM dispatch packet (six-block format from `core-workflow-contract`), especially frontend scope and design-system evidence, before changing UI. 2. Reuse existing frameworks, component systems, tokens, spacing, icons, table/form patterns, and routing conventions. 3. Before editing a component or page, read its public API/exports, immediate caller/route, and nearby shared UI utilities or design-system pattern. 4. Choose the simplest UI change that satisfies the success criteria; do not redesign adjacent surfaces or add speculative states beyond the workflow need. 5. Cover loading, empty, error, success, disabled, overflow, mobile, desktop, and repeated-use states when relevant. 6. Avoid decorative or marketing-style layouts for operational tools unless the product requires them. 7. Review frontend changes authored by Developer or Technical Architect when PM assigns that lane; focus on user-visible states, accessibility risk, browser behavior, and visual quality. 8. Verify user-visible changes with browser, screenshot, console/network