agentsclimarketplace

Nextjs styling

Skill FilippoDeSilva/skills/skills/nextjs/nextjs-styling

Skills for my agentic development workflow.

Install
npx -y skills add FilippoDeSilva/skills --skill nextjs-styling

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Implement zero-runtime CSS with Tailwind, CSS Modules, and the cn() utility for RSC-compatible styling in Next.js. Use when choosing a styling library, creating dynamic class utilities, or optimizing fonts with next/font.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.7 KB, as published. Nobody here has run it

Styling & UI Performance

Priority: P1 (HIGH)

Prioritize Zero-Runtime CSS for Server Components.

Workflow: Set Up Styling

  1. Choose library — Tailwind/shadcn (preferred), CSS Modules (scoped), or Ant Design (with client wrappers).
  2. Create cn utility — Combine clsx + tailwind-merge for dynamic classes.
  3. Configure fonts — Use next/font for zero-CLS self-hosted fonts.
  4. Set image dimensions — Always specify width/height or fill on <Image>.

cn Utility Example

See implementation examples

Library Selection

LibraryVerdictReason
Tailwind / shadcnPreferred (P1)Zero-runtime, RSC compatible. Best for App Router.
CSS Modules / SCSSRecommendedScoped, zero-runtime. Good for legacy projects.
Ant DesignSupportedUse with Client Component wrappers for RSCs.
MUI / Chakra (Runtime)AvoidForces use client widely. Degrades performance.

Library Patterns

For specific library setups, see:

Patterns

  1. Dynamic Classes: Use clsx + tailwind-merge (cn utility).
  1. Font Optimization: Use next/font to prevent Cumulative Layout Shift (CLS).
  1. CLS Prevention: Always specify width/height on images.

Anti-Patterns

  • No runtime CSS-in-JS with RSC: MUI/Chakra force 'use client'; prefer Tailwind or CSS Modules.
  • No <img> without dimensions: Always set width/height or use fill to prevent CLS.
  • No hardcoded conditional classes: Use clsx+tailwind-merge (cn) for dynamic styles.
  • No Google Fonts <link> tag: Use next/font for zero-CLS self-hosted fonts.

Gives 1 of the 12 instructions most css styling skills give

Counted across 586 of the 596 authors here whose files we hold, read 2026-08-06

  • avoid excessive centered layoutsin 55 of 586, across 12 files
  • bundle code into single HTML filein 54 of 586, across 14 files
  • Respect prefers-reduced-motion user settingsin 52 of 586, across 35 files
  • avoid purple gradientsin 51 of 586, across 11 files
  • avoid uniform rounded cornersin 51 of 586, across 11 files
  • avoid Inter fontin 51 of 586, across 11 files
  • edit generated files to develop artifactin 50 of 586, across 10 files
  • animate only transform and opacity propertiesin 43 of 586
  • Make touch targets at least 44x44 pixelsin 41 of 586, across 15 files
  • Ensure minimum color contrast of 4.5:1in 39 of 586, across 10 files
  • use tailwind csshere, and in 39 of 586, across 24 files
  • Use SVG icons instead of emojisin 38 of 586, across 11 files

Said here and by no other author read

  • prioritize zero-runtime css
  • set image width height or fill
  • use client wrappers for ant design

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.