Skill: Verify Next.js (MUI)
Purpose
MUI-specific checklist for a Next.js + Material UI project. Run alongside verify-nextjs.md (general Next.js/React concerns) — this file only covers what MUI adds. MUI projects use Emotion, not Tailwind, so skip the Tailwind section of verify-nextjs.md.
Verification Process
Flag each as PASS, WARN, or FAIL.
1. Styling (sx + Emotion)
- Component styling uses the
sxprop (orstyled()), not inlinestyle={{}} - No Tailwind — no
tailwind.config,postcss.config, orglobals.cssutility layer (MUI owns styling via Emotion) - Colors and spacing come from the theme (
primary.main,text.secondary, spacing units), not hardcoded hex/px - Emotion is the only styling engine —
styled-componentsis not mixed in
2. SSR + Theme Setup (layout.tsx)
-
AppRouterCacheProviderwraps the app withoptions={{ enableCssLayer: true }}so Emotion styles are injected correctly during SSR (no style flash / hydration mismatch) -
InitColorSchemeScriptis rendered (matching the theme'sattribute) to prevent a light/dark flash on load -
ThemeProvider+CssBaselinelive inlayout.tsx, not re-declared in nested providers
3. Components
- MUI
Griduses the v6+sizeprop (<Grid size={{ xs: 12, sm: 6 }}>), not the deprecateditem+xs/sm/mdprops
Output
Produce a verification-report.md (same format as verify-django), adding a "MUI" section.