nextjs-bootstraplisted

Scaffold a new production-grade Next.js (App Router) + TypeScript + Tailwind + shadcn/ui frontend from scratch, wired to a separate API backend (e.g. Express) via a BFF proxy, with axios, Zod, TanStack Query, and React Hook Form. Use this whenever the user wants to start a new Next.js / React frontend, bootstrap a web client/UI, set up a shadcn starter, or initialize a frontend project — even if they only say "new frontend", "Next.js starter", "React app", "admin dashboard UI", or name the stack loosely. It scaffolds the infrastructure ONCE per project and emits the two source-of-truth files (ARCHITECTURE.md and MODULE_REGISTRY.md) that module-planner, module-builder, test-writer, and code-review depend on. Do NOT use this to add a feature/page to an existing project (that is module-planner + module-builder) or to write tests. This scaffolds a Next.js + React frontend specifically — do NOT use it to bootstrap a backend/API (that is express-ts-bootstrap) or projects in other frontend stacks (Vite/CRA/Remix/Vue
vipincode/exr-agent-skills · ★ 0 · Web & Frontend · score 57

Install: claude install-skill vipincode/exr-agent-skills

# nextjs-bootstrap Scaffold a runnable, production-grade **Next.js (App Router) + TypeScript + Tailwind + shadcn/ui** frontend that talks to a separate API backend through a **BFF proxy**, and — critically — emit `ARCHITECTURE.md` and `MODULE_REGISTRY.md`. Those two files are the shared memory that lets the frontend skills (`module-planner`, `module-builder`, `test-writer`, `code-review`, plus the theme/design builders `font-theme-setup`, `figma-to-component`, `html-to-component`, `project-to-component`) avoid re-asking decisions and stop generating duplicate components. Getting them right matters more than the boilerplate. This skill runs **once per project**. It does NOT build feature pages (auth screens, dashboards with real data, CRUD) — it lays the foundation: the BFF/auth wiring, the DRY shared form + typography components, the data-fetching and HTTP plumbing, and a role-based routing skeleton, so later skills have concrete patterns to copy. This is the frontend twin of `express-ts-bootstrap`. It mirrors that skill's philosophy: **infrastructure once, decisions once, a seeded registry so nothing gets built twice.** Read `../NAMING.md` and `../LAYOUT.md` for how it coexists with a backend in one repo. ## Stack (fixed) Use **latest** for everything — this stack moves fast, so confirm current APIs with **context7 before generating** (see `references/stack-context7.md`). The bundled boilerplate is written against current stable APIs; if context7 shows an API has change