loom-frontend-ui-engineeringlisted

# loom-frontend-ui-engineering Frontend UI engineering is a Loom playbook for user-facing interface work. It turns design intent into specs, slices implementation through tickets and ticket-owned Ralph runs, records browser evidence, and routes accessibility, performance, and visual risks through audit. ## Loom Routing Common routes use these Loom skills for durable records or follow-up workflow: `loom-specs`, `loom-tickets`, `loom-ralph`, `loom-evidence`, `loom-audit`, `loom-knowledge`, and `loom-retrospective`. Follow any named Loom skill fully. This playbook adds workflow pressure; it does not shorten target-skill requirements. Keep broad product or design intent in outer-loop shaping until the operator-facing direction, scope and exclusion choices, information hierarchy, state boundaries, quality bar, evidence posture, and ticket boundary are clear enough to route. ## Use This Playbook When Use this playbook when: - creating or modifying UI components, pages, flows, layouts, or interactions - visual quality, responsive behavior, or accessibility matters - browser runtime state must be observed - frontend state, data fetching, loading, error, or empty states are in scope - design system adherence or existing UI patterns constrain the work - UI work needs screenshots, DOM inspection, console/network checks, or performance observations ## Route Use this route: ```text intent -> contract -> slice -> build -> observe -> review -> preserve ``` ## Intent Clarify: