frontend-reviewlisted

# Frontend Review Self-review of a React/Next.js frontend before merge. A project-local `frontend-review` skill, if present, takes precedence over this one. ## Arguments - No arguments: **diff mode**, review files changed on the current branch vs the default branch, fix 🔴 Critical findings after reporting. - `full`: **full mode**, audit the entire codebase. - `--fix all`: also apply 🟡 Important and 🔵 Suggestion fixes. - `--fix none`: report only, change nothing. --- ## Step 0: Detect the stack Read `package.json`, the lockfile, and the project's `CLAUDE.md` (and `docs/dev-guide.md` or similar, if CLAUDE.md points to one). Build a stack profile; it gates which checklist sections apply: | Signal | How to detect | |--------|---------------| | Framework | `next` dep + `app/` dir = Next.js App Router; `app/` absent = Pages Router; `vite` dep = Vite SPA | | Router | `react-router-dom` dep (note major version) vs Next built-in | | Tailwind | v4: `@import "tailwindcss"` / `@theme` in global CSS, usually no config file; v3: `tailwind.config.{ts,js}` | | Dark mode | `dark:` variant configured, `class` strategy, `[data-theme]` attribute selectors, or none. Grep the global CSS and config | | shadcn/ui | `components/ui/` directory, `components.json` | | Class merging | `cn()` helper in `lib/utils`, or `clsx`/`tailwind-merge` deps. If absent, do not demand them | | Animation | `framer-motion` / `motion` dep | | Package manager | lockfile: `bun.lock*`, `pnpm-lock.yaml`, `yarn.lock