agentleFS
Sign inStart free
jhonatan-oliveiradevjhonatan-oliveiradev/agent-skills/skills/building-premium-nextjs-interfaces/SKILL.md

building-premium-nextjs-interfaces

Skill1 starsChanged 3 months agoMITView on GitHub

Use when creating or redesigning a polished Next.js or React interface where visual distinction, strong hierarchy, responsive behavior, accessibility, and production readiness matter.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Prefer semantic HTML and Server Components by default.

    line 14
  2. Distinctive:

    Use real content and honest product evidence.

    line 15
  3. Distinctive:

    Write a compact visual thesis: hierarchy, grid, type scale, spacing rhythm, media treatment, interaction tone, and what must remain …

    line 19
  4. Distinctive:

    Add states deliberately: hover, focus, active, loading, disabled, empty, error, selected, touch.

    line 22
  5. Distinctive:

    Add motion only after the static composition works.

    line 23
  6. Very specific:

    Verify in-browser at representative desktop and mobile sizes, then run lint/typecheck/tests/build available in the repo.

    line 24
  7. Distinctive:

    No generic bento-grid filler, random gradient blobs, excessive glass, fake social proof, or decorative UI with no product role.

    line 31
  8. Very specific:

    Do not use this skill for narrow bug fixes, backend-only changes, or exact visual reproduction tasks where …

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Inspect the current page, design references, app architecture, fonts, tokens, breakpoints, and reusable primitives.
  2. Write a compact visual thesis: hierarchy, grid, type scale, spacing rhythm, media treatment, interaction tone, and what must remain unchanged.
  3. Establish layout before decoration. Fix information architecture, section pacing, alignment, density, and responsive collapse order.
  4. Reuse or extend project primitives before creating new components.
  5. Add states deliberately: hover, focus, active, loading, disabled, empty, error, selected, touch.
  6. Add motion only after the static composition works.
  7. 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free