AGENT SKILL

react-nextjs-development

React and Next.js 14+ application development with App Router, Server Components, TypeScript, Tailwind CSS, and modern frontend patterns.

License 许可
MIT
最近更新
2026-11-10
Stars
★ 1
Forks
0

01 前言 Front Matter

name
react-nextjs-development
risk
safe
source
personal
category
granular-workflow-bundle
date_added
2026-02-27
description
React and Next.js 14+ application development with App Router, Server Components, TypeScript, Tailwind CSS, and modern frontend patterns.

03 SKILL.md 正文

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 framework
  2. Write unit tests
  3. Create component tests
  4. Implement E2E tests
  5. Configure CI integration

Copy-Paste Prompts

Use @javascript-testing-patterns to write Vitest tests
Use @playwright-skill to create E2E tests for critical flows

Phase 8: Build and Deployment

Skills to Invoke

  • vercel-deployment - Vercel deployment
  • vercel-deploy-claimable - Vercel deployment
  • web-performance-optimization - Performance

Actions

  1. Configure build settings
  2. Optimize bundle size
  3. Set up environment variables
  4. Deploy to Vercel
  5. Configure preview deployments

Copy-Paste Prompts

Use @vercel-deployment to deploy Next.js app to production

Technology Stack

Category Technology
Framework Next.js 14+, React 18+
Language TypeScript 5+
Styling Tailwind CSS v4
State Zustand, React Query
Forms React Hook Form, Zod
Testing Vitest, Playwright
Deployment Vercel

Quality Gates

  • [ ] TypeScript compiles without errors
  • [ ] All tests passing
  • [ ] Linting clean
  • [ ] Performance metrics met (LCP, CLS, FID)
  • [ ] Accessibility checked (WCAG 2.1)
  • [ ] Responsive design verified

Related Workflow Bundles

  • development - General development
  • testing-qa - Testing workflow
  • documentation - Documentation
  • typescript-development - TypeScript patterns

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

04 同仓库更多 Skills

YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

vercel-sandbox

Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

slack

Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

electron

Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

dogfood

Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

shadcn

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.

★ 1