frontend-designlisted

# Frontend Design -- anti-slop craft Craft skill backing the ui-ux-designer and the software-engineer above the API seam. The goal is UI that looks decided, not generated. Deep material lives in seven references, read on demand: references/direction-lanes.md (the named direction catalog), references/anti-slop-checklist.md (the tells, in two tiers), references/industry-patterns.md (domain heuristics, illustrative only), and references/design-system-map.md (brief signal to an official design-system package, or an honest native-CSS approach when no package fits), and references/prototype-protocol.md (isolated variants, review fields, and workbench rules), references/design-record.md (structured task records and master/page inheritance), and references/resilient-content.md (content and interaction safeguards). User instructions always override this skill. All factual output follows the anti-hallucination skill: cite or mark UNKNOWN, never guess (this includes design tokens -- never cite a token that is not in the spec). ## Rule block 1. Direction first: commit to ONE named aesthetic direction before any markup -- a lane from references/direction-lanes.md or an original named with the same rigor -- with a one-line rationale tied to the audience. The default lane is restrained; immersive/maximalist is opt-in and requires the brief to ask for it. "Clean and modern" is the absence of a direction. 2. Typography carries the hierarchy: a deliberate type scale (not browser