nfs-review-projectlisted

Review an existing project scaffolded with nextjs-fullstack-starter against the architectural invariants and patterns. Use this whenever the user wants to audit project conventions, asks 'does this follow our patterns', wants a pre-PR architecture check, suspects drift, is onboarding a new contributor, or invokes /nfs-review-project. Runs a mechanical check script for fast objective violations (missing server-only, DB queries in src/app/, missing requirePermission on mutations, missing audit, wrong cache primitives, tRPC imports from the wrong stack), then samples files for judgment calls, then produces a categorized report grouped by severity (must fix / should fix / notes / passing).
juncoding/nextjs-fullstack-starter · ★ 0 · Web & Frontend · score 70

Install: claude install-skill juncoding/nextjs-fullstack-starter

# Review project against architecture invariants For projects scaffolded with `nextjs-fullstack-starter`. Detects drift from the patterns established by the scaffolder and the `nfs-architecture-patterns` skill. ## Use this skill when - User asks "does this project follow our conventions?" - Before a PR review or merge. - After a substantial feature lands, to catch newly-introduced drift. - During onboarding — quick health check for an unfamiliar codebase. - User invokes `/nfs-review-project`. - User suspects something feels off architecturally. Do NOT use this skill on: - Projects NOT scaffolded with this plugin (the rules are tuned for the Server Components + Server Actions stack). If structure detection fails, refuse and explain. - Projects in the middle of a partial migration — the noise drowns the signal. ## The flow 1. **Verify project structure.** Confirm we're in a project this skill knows how to review. 2. **Run `scripts/check-conventions.sh`.** Mechanical, deterministic checks that take ~1s. 3. **Parse the script's findings.** Group by check type. 4. **Sample-read flagged files.** For checks that need judgment (e.g. "is this `src/app/` page genuinely thin?"), read 5-10 of the flagged files and verify. 5. **Sample-read passing files too.** Spot-check 3-5 files that the script didn't flag, to catch issues the script can't see (silent permission bypasses, drift in module organization, smuggled state libs). 6. **Produce the report.** Markdown, grouped by severity.