theyoungastronautstheyoungastronauts/polaris/skills/verify-nextjs-shadcn/SKILL.md

verify-nextjs-shadcn

Skill4 starsChanged 3 months agoMITView on GitHub

ShadCN-specific Next.js verification checklist — components.json, cn(), next-themes.

In this repository53 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- actionableSkill
- astro-bootstrapSkill
- astro-patternsSkill
- autopilotSkill
- axon-code-intelSkill
- brainstormingSkill
- commit-conventionsSkill
- cross-repo-contextSkill
- django-bootstrapSkill
- django-patternsSkill
- executeSkill
- find-sessionSkill
- flutter-bootstrapSkill
- flutter-patternsSkill
- full-featureSkill
- intelSkill
- nextjs-bootstrapSkill
- nextjs-fullstack-bootstrapSkill
- nextjs-fullstack-patternsSkill
- nextjs-mui-bootstrapSkill
- nextjs-patternsSkill
- nextjs-shadcn-bootstrapSkill
- orchestratorSkill
- phase-breakdownSkill
- plan-and-scopeSkill
- prdSkill
- reactSkill
- recallSkill
- reflectSkill
- relaySkill
- rememberSkill
- scaffoldSkill
- scratchSkill
- tailwindSkill
- ux-specSkill
- ux-to-promptsSkill
- verify-astroSkill
- verify-djangoSkill
- verify-flutterSkill
- verify-nextjs-fullstackSkill
- verify-nextjs-muiSkill
- verify-nextjsSkill
- verifySkill
- visual-feedbackSkill
- work-disciplineSkill
- worktreesSkill
- wrapSkill
- write-as-friendSkill
- write-as-humanSkill
- writing-clearlySkill
- writing-skillsSkill

The file

Create a free account to mount

Files

SKILL.md

Skill: Verify Next.js (ShadCN)

Purpose

ShadCN-specific checklist for a Next.js + ShadCN UI project. Run alongside verify-nextjs.md (general concerns) — this file only covers what ShadCN adds. ShadCN is Tailwind-based, so also run the Tailwind v4 section of verify-nextjs.md.

Verification Process

Flag each as PASS, WARN, or FAIL.

1. Configuration

components.json exists and its aliases are correct — notably "ui": "@/components/ui" — so the CLI installs components to the right place
cn() exists in lib/utils.ts as twMerge(clsx(...))

2. Components & className

ShadCN components are imported from @/components/ui/<component>, not relative paths or a barrel
Conditional/merged classNames go through cn() — never string concatenation or template literals for class merging (so conflicting Tailwind classes resolve correctly)

3. Theming (next-themes)

ThemeProvider from next-themes wraps the app with attribute="class" and disableTransitionOnChange
Dark mode is driven by the .dark class (Tailwind v4 @custom-variant dark), not a separate stylesheet

Output

Produce a verification-report.md (same format as verify-django), adding a "ShadCN" section.

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