jaw-dev-frontend

name	jaw-dev-frontend
description	MUST USE for any frontend, web UI, or visual implementation work — building, styling, or redesigning pages/components, responsive layouts, motion, component architecture, and production-surface polish. Triggers: frontend, UI, component, CSS, responsive, animation, React, Vue, Svelte, Tailwind, layout, styling, redesign, mockup, anti-slop, 프론트엔드, UI 작업, 반응형, 디자인 수정.
metadata	{"short-description":"Frontend implementation with responsive, accessible, anti-slop UI guidance.","keywords":"frontend, UI, component, CSS, responsive, layout, animation, design implementation","last-verified":"2026-07-02"}

Dev-Frontend — Domain-Correct Frontend Engineering

Build distinctive, production-grade interfaces that fit the product domain, locale, interaction model, and real visual evidence. This skill has modular references for specialized guidance — read the relevant ones before coding. It activates by change surface whenever the work is primarily frontend, UI, styling, responsive layout, or animation.

Role separation: For design judgment — typography/color/layout direction, UX decision gates, product personalities, or vague visual briefs — load dev-uiux-design first. This skill implements the chosen direction; dev-uiux-design makes the design decisions. Implementation anti-slop tell detection and enforcement stays here (concrete rendered tells in UI); design-level concept/taste judgment lives in dev-uiux-design.

Role boundary (canonical — identical in dev and dev-uiux-design): dev owns universal process, evidence, and safety rules. dev-uiux-design owns design intent, direction, and concept judgment. owns concrete frontend implementation and rendered tell enforcement. Anti-slop has three layers: = output/process hygiene (FAMILY-SLOP-01), = concept/taste judgment (is this direction generic or domain-wrong?), = rendered implementation tell detection and removal (FE-AI-TELL-01).