Building Premium Next.js Interfaces
Core principle
Build a coherent visual system, not a collection of attractive components. Preserve product clarity first; premium treatment comes from disciplined typography, spacing, media, interaction, and restraint.
Defaults
- Existing repo conventions win.
- For a new application, load
bootstrapping-modern-web-apps first; this skill owns art direction and interface quality rather than project scaffolding.
- Prefer semantic HTML and Server Components by default; add client boundaries only where interaction requires them.
- Use real content and honest product evidence. Never invent testimonials, clients, partnerships, or metrics.
Workflow
- Inspect the current page, design references, app architecture, fonts, tokens, breakpoints, and reusable primitives.
- Write a compact visual thesis: hierarchy, grid, type scale, spacing rhythm, media treatment, interaction tone, and what must remain unchanged.
- Establish layout before decoration. Fix information architecture, section pacing, alignment, density, and responsive collapse order.
- Reuse or extend project primitives before creating new components.
- Add states deliberately: hover, focus, active, loading, disabled, empty, error, selected, touch.
- Add motion only after the static composition works.
- Verify in-browser at representative desktop and mobile sizes, then run lint/typecheck/tests/build available in the repo.
Quality bar
- Strong first viewport without sacrificing readability.
- Typography has intentional scale, line-height, measure, and weight contrast.
- Images use deliberate aspect ratios and crop rules.
- Components align to a repeatable spacing system.
- No generic bento-grid filler, random gradient blobs, excessive glass, fake social proof, or decorative UI with no product role.
- Accessibility is part of polish: visible focus, keyboard access, labels, contrast, reduced motion.
When not to use
Do not use this skill for narrow bug fixes, backend-only changes, or exact visual reproduction tasks where implementing-reference-faithful-ui is the better primary skill.
1---2name: building-premium-nextjs-interfaces3description: Use when creating or redesigning a polished Next.js or React interface where visual distinction, strong hierarchy, responsive behavior, accessibility, and production readiness matter.4---56# Building Premium Next.js Interfaces78## Core principle9Build a coherent visual system, not a collection of attractive components. Preserve product clarity first; premium treatment comes from disciplined typography, spacing, media, interaction, and restraint.1011## Defaults12- Existing repo conventions win.13- For a new application, load `bootstrapping-modern-web-apps` first; this skill owns art direction and interface quality rather than project scaffolding.14- Prefer semantic HTML and Server Components by default; add client boundaries only where interaction requires them.15- Use real content and honest product evidence. Never invent testimonials, clients, partnerships, or metrics.1617## Workflow181. Inspect the current page, design references, app architecture, fonts, tokens, breakpoints, and reusable primitives.192. Write a compact visual thesis: hierarchy, grid, type scale, spacing rhythm, media treatment, interaction tone, and what must remain unchanged.203. Establish layout before decoration. Fix information architecture, section pacing, alignment, density, and responsive collapse order.214. Reuse or extend project primitives before creating new components.225. Add states deliberately: hover, focus, active, loading, disabled, empty, error, selected, touch.236. Add motion only after the static composition works.247. Verify in-browser at representative desktop and mobile sizes, then run lint/typecheck/tests/build available in the repo.2526## Quality bar27- Strong first viewport without sacrificing readability.28- Typography has intentional scale, line-height, measure, and weight contrast.29- Images use deliberate aspect ratios and crop rules.30- Components align to a repeatable spacing system.31- No generic bento-grid filler, random gradient blobs, excessive glass, fake social proof, or decorative UI with no product role.32- Accessibility is part of polish: visible focus, keyboard access, labels, contrast, reduced motion.3334## When not to use35Do not use this skill for narrow bug fixes, backend-only changes, or exact visual reproduction tasks where `implementing-reference-faithful-ui` is the better primary skill.
jhonatan-oliveiradev