frontend-aesthetic-directorlisted

# Frontend Aesthetic Director Implement intentional, usable, responsive UI while preserving the product's approved task flow. Default to focused polish rather than an unsolicited redesign. ## Boundary and Pairing - Use `ui-ux-workflow` or `ui-communication-designer` for conceptual structure, flow, and copy critique before implementation. - Use `$run-ux` for a formal UX scorecard. - Use `devtools-ux-audit` or suitable browser tooling for rendered evidence. - Preserve information architecture, CTA priority, copy intent, trust posture, and state intent unless the current structure demonstrably blocks comprehension or task completion. If an approved concept, screenshot, Figma note, or wireframe is supplied, treat it as upstream source of truth. Refine visual hierarchy, tokens, styling, responsive behavior, semantics, accessibility, interaction states, and defects. If the handoff conflicts with the existing design system or is technically impractical, make the smallest viable adjustment and report it. ## Required Workflow ### 1. Inspect Before Editing Establish: - framework, styling stack, build commands, and component conventions - existing tokens, CSS variables, themes, fonts, icons, motion, and spacing - page/component structure and primary user task - upstream design artifacts and relevant product copy - current loading, empty, error, success, disabled, stale, and long-content states - available rendered-QA path Use `assets/design-brief-template.md` to form a compact