
React Nextjs Development
Run a phased React/Next.js 14+ build workflow with App Router, Server Components, TypeScript, and Tailwind instead of improvising setup and architecture in chat.
Overview
React Nextjs Development is an agent skill most often used in Build (also Build backend patterns for full-stack Next.js) that runs a multi-phase React and Next.js 14+ workflow with App Router, Server Components, TypeScri
Install
npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill react-nextjs-developmentWhat is this skill?
- Phased workflow starting with project setup (scaffold, TypeScript, ESLint/Prettier) then component architecture
- Next.js 14+ App Router and Server Components with copy-paste @ skill invocations (e.g. app-builder, nextjs-app-router-pa
- Supports React SPA or Next.js targets with Vite, Next.js, or CRA-style tooling choices
- Bundles senior-fullstack, typescript-pro, and frontend-developer guidance for modern full-stack Next.js
- Explicit When to Use triggers: new React apps, App Router projects, TypeScript + React, Tailwind styling
- Documented workflow phases include at least Project Setup and Component Architecture
- Targets Next.js 14+ with App Router, Server Components, TypeScript, and Tailwind CSS
- Phase 1 names four companion skills: app-builder, senior-fullstack, nextjs-app-router-patterns, typescript-pro
Adoption & trust: 661 installs on skills.sh; 40.1k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You want a modern Next.js 14 App Router codebase but lack a consistent order of operations for scaffold, TypeScript, and component architecture across agent sessions.
Who is it for?
Solo builders starting or restructuring a Next.js 14+ app who already use Claude Code, Cursor, or Codex and want workflow phases instead of ad-hoc UI coding.
Skip if: Teams with an approved design system and CI-only scaffolding, or projects that are not React/Next.js (use a different stack skill).
When should I use this skill?
Building new React applications; creating Next.js 14+ projects with App Router; implementing Server Components; setting up TypeScript with React; styling with Tailwind CSS; building full-stack Next.js applications.
What do I get? / Deliverables
You get a structured build workflow with named skill handoffs (e.g. app-builder, nextjs-app-router-patterns, frontend-developer) and copy-paste prompts for setup and Server Components.
- Scaffolded React or Next.js 14+ project with TypeScript and lint/format config
- App Router layout and Server Component structure
- Component architecture aligned with frontend-developer patterns
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
The skill is a build-time application workflow—scaffolding, App Router patterns, and component work—so the canonical shelf is the Build phase rather than validate or ship. Primary work is UI and Next.js frontend architecture (App Router, Server Components, Tailwind); full-stack touches stay secondary under frontend-led delivery.
Where it fits
Spin a quick Next.js 14 prototype with App Router to validate UI flows before committing to full backend design.
Follow Phase 1 setup and Phase 2 component architecture with @nextjs-app-router-patterns for Server Components.
Extend the same full-stack Next.js project using senior-fullstack guidance for API routes and server data patterns.
Reuse the established Next.js structure when preparing a first deployable build after local feature completion.
How it compares
Use as a phased skill workflow for Next.js greenfield builds, not as a single lint rule pack or an MCP server integration.
Common Questions / FAQ
Who is react-nextjs-development for?
It is for solo and indie developers and small teams using AI coding agents to create React or Next.js 14+ applications with App Router, Server Components, TypeScript, and Tailwind.
When should I use react-nextjs-development?
Use it during Build when starting a new React SPA or Next.js app, configuring App Router and Server Components, wiring TypeScript and Tailwind, or standing up a full-stack Next.js surface; it is less relevant during Idea research or Launch SEO work.
Is react-nextjs-development safe to install?
The bundle is labeled safe risk in its metadata, but you should still review the Security Audits panel on this Prism page and inspect the skill files in your repo before granting shell or network access to your agent.
Workflow Chain
Then invoke: nextjs app router patterns, app builder
SKILL.md
READMESKILL.md - React Nextjs Development
# React/Next.js Development Workflow ## Overview Specialized workflow for building React and Next.js 14+ applications with modern patterns including App Router, Server Components, TypeScript, and Tailwind CSS. ## When to Use This Workflow Use this workflow when: - Building new React applications - Creating Next.js 14+ projects with App Router - Implementing Server Components - Setting up TypeScript with React - Styling with Tailwind CSS - Building full-stack Next.js applications ## Workflow Phases ### Phase 1: Project Setup #### Skills to Invoke - `app-builder` - Application scaffolding - `senior-fullstack` - Full-stack guidance - `nextjs-app-router-patterns` - Next.js 14+ patterns - `typescript-pro` - TypeScript setup #### Actions 1. Choose project type (React SPA, Next.js app) 2. Select build tool (Vite, Next.js, Create React App) 3. Scaffold project structure 4. Configure TypeScript 5. Set up ESLint and Prettier #### Copy-Paste Prompts ``` Use @app-builder to scaffold a new Next.js 14 project with App Router ``` ``` Use @nextjs-app-router-patterns to set up Server Components ``` ### Phase 2: Component Architecture #### Skills to Invoke - `frontend-developer` - Component development - `react-patterns` - React patterns - `react-state-management` - State management - `react-ui-patterns` - UI patterns #### Actions 1. Design component hierarchy 2. Create base components 3. Implement layout components 4. Set up state management 5. Create custom hooks #### Copy-Paste Prompts ``` Use @frontend-developer to create reusable React components ``` ``` Use @react-patterns to implement proper component composition ``` ``` Use @react-state-management to set up Zustand store ``` ### Phase 3: Styling and Design #### Skills to Invoke - `frontend-design` - UI design - `tailwind-patterns` - Tailwind CSS - `tailwind-design-system` - Design system - `core-components` - Component library #### Actions 1. Set up Tailwind CSS 2. Configure design tokens 3. Create utility classes 4. Build component styles 5. Implement responsive design #### Copy-Paste Prompts ``` Use @tailwind-patterns to style components with Tailwind CSS v4 ``` ``` Use @frontend-design to create a modern dashboard UI ``` ### Phase 4: Data Fetching #### Skills to Invoke - `nextjs-app-router-patterns` - Server Components - `react-state-management` - React Query - `api-patterns` - API integration #### Actions 1. Implement Server Components 2. Set up React Query/SWR 3. Create API client 4. Handle loading states 5. Implement error boundaries #### Copy-Paste Prompts ``` Use @nextjs-app-router-patterns to implement Server Components data fetching ``` ### Phase 5: Routing and Navigation #### Skills to Invoke - `nextjs-app-router-patterns` - App Router - `nextjs-best-practices` - Next.js patterns #### Actions 1. Set up file-based routing 2. Create dynamic routes 3. Implement nested routes 4. Add route guards 5. Configure redirects #### Copy-Paste Prompts ``` Use @nextjs-app-router-patterns to set up parallel routes and intercepting routes ``` ### Phase 6: Forms and Validation #### Skills to Invoke - `frontend-developer` - Form development - `typescript-advanced-types` - Type validation - `react-ui-patterns` - Form patterns #### Actions 1. Choose form library (React Hook Form, Formik) 2. Set up validation (Zod, Yup) 3. Create form components 4. Handle submissions 5. Implement error handling #### Copy-Paste Prompts ``` Use @frontend-developer to create forms with React Hook Form and Zod ``` ### Phase 7: Testing #### Skills to Invoke - `javascript-testing-patterns` - Jest/Vitest - `playwright-skill` - E2E testing - `e2e-testing-patterns` - E2E patterns #### Actions 1. Set up testing f