frontend-designlisted

# Design distinctive, production-grade frontend Build frontend that looks **intentional, opinionated, and specific to the product** — not a default template. The bar is: *would this look believable in a real product screenshot?* This pack is about visual quality and design judgement; pair it with `frontend-component`, `frontend-a11y`, and `frontend-responsive` for structure, semantics, and breakpoints, and with **`design-system`** for the structural layer beneath the aesthetic — the three-tier token architecture (primitive → semantic → component) and full component state specs. This pack decides *how it should look*; `design-system` decides *how that look is structured so it scales*. Don't re-derive tokens or component-state matrices here — consume them from there. ## Before you write any code — pick a direction Generic defaults ("clean minimal") are not a direction. Commit to a specific one and let it drive every decision: - **Editorial / magazine**, **Swiss / International**, **Neo-brutalism**, **Bento layouts**, **Glassmorphism with real depth**, **dark or light luxury** (disciplined contrast), **Scrollytelling**, **retro-futurism**, **3D integration**. - Do **not** default to dark mode. Choose the direction the *product* wants. - Define the palette deliberately (semantic roles, not one accent on grey-on-white) and a real **typography pairing strategy** — pick fonts with character, with a reason. - Read the repo's existing tokens/brand first. If a brand exists, *