Frontend Design

Create a working frontend with a clear, subject-specific point of view, then prove it in the rendered UI.

Contract

For a critique, review, or design plan, inspect the relevant product and report the direction without editing files.
For a build or redesign, make the requested in-scope changes and run local, non-destructive validation.
Treat explicit user direction, supplied references, repository instructions, existing product behavior, and the local design system as authoritative. Fidelity requests override this skill's defaults.
Preserve the stack and working behavior. Do not replace the framework or design system, add dependencies, invent features, or fetch or generate media unless the request requires it.
Make the smallest defensible assumption when the subject, audience, or page job is missing. State it before building; ask only when the answer would materially change scope or identity.