nfs-scaffold-applisted

Scaffold a brand-new fullstack back-office app on pure Next.js (App Router) — Server Components for reads, Server Actions for writes, services in src/server/modules/. Use this whenever the user wants to start a new internal tool, admin dashboard, back-office app, line-of-business system, lightweight ERP, or CRUD app on Next.js without a separate API service — even if they don't name the stack. Walks the user through an interactive Q&A (project name, location, database, auth, cache, MCP, deployment target), then generates the canonical folder structure, dependencies, sample Server Action, sample service, Prisma schema starter, .env.example, and CLAUDE.md. Always trigger when the user wants a Next.js fullstack starter without tRPC, when they describe building a back office with Server Components, or when they say 'one Next.js app does everything'.
juncoding/nextjs-fullstack-starter · ★ 0 · API & Backend · score 70

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

# Scaffold a new fullstack back-office app This skill bootstraps a brand-new project on the **pure Next.js (App Router) fullstack** stack — no tRPC, no separate API service, no SPA shell. It is the entry point for the `nextjs-fullstack-starter` plugin and is invoked either explicitly via `/nfs-scaffold-app` or when the user expresses intent to start a new back-office system on plain Next.js. ## When to use this skill Use this skill when the user is **starting a brand-new project** in one of these shapes: - Internal admin dashboard / management system - Back-office tool for staff - Line-of-business app with CRUD over rich domain models - Lightweight ERP / operational tool - Solo or small-team SaaS where the main app is auth-walled - Any "one Next.js app does everything" project Do NOT use this skill for: - Adding a feature to an existing project (those have their own skills — `nfs-add-auth`, `nfs-add-cache`, `nfs-add-mcp`). - Projects where the user wants tRPC + SPA mode — use the sibling plugin `nextjs-trpc-prisma-starter` instead. - Public-facing marketing sites or content sites where the patterns don't apply. - Mobile-first products that need a typed HTTP API surface — Server Actions are web-only. ## Why an interactive flow The stack is opinionated but the project has variables (database, auth provider, whether to wire cache from day one, MCP, deploy target). Asking up front means the generated project is **complete and consistent** rather than half-configured. The