Skip to content
Back to skills

React Nextjs Patterns

ASecurity

Modern React + Next.js patterns. Use when building Next.js apps (App Router, Server Components, streaming, parallel routes), implementing React state management (Redux Toolkit, Zustand, Jotai, React Query), or applying Next.js framework best practices (file conventions, RSC boundaries, metadata, image/font optimization).

  • 69 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 5, 2026
ai-agentsreactnextjsapifrontend

Works with

  • cli
  • api

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned September 5, 2026

npx -y skills add The-AIOS/aios --skill react-nextjs-patterns --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of React Nextjs Patterns?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for React Nextjs Patterns
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/the-aios-react-nextjs-patterns/badge)](https://www.skillsdirectory.com/skills/the-aios-react-nextjs-patterns)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: react-nextjs-patterns
description: Modern React + Next.js patterns. Use when building Next.js apps (App Router, Server Components, streaming, parallel routes), implementing React state management (Redux Toolkit, Zustand, Jotai, React Query), or applying Next.js framework best practices (file conventions, RSC boundaries, metadata, image/font optimization).
---

# React + Next.js Patterns

Modern Next.js (App Router) + React state-management practices for production apps.

## When to load which reference

| Working on | Read |
|---|---|
| Next.js framework conventions (file structure, metadata, RSC, async APIs) | [references/next-best-practices.md](references/next-best-practices.md) |
| Next.js 14+ App Router (Server Components, streaming, parallel routes, data fetching) | [references/nextjs-app-router-patterns.md](references/nextjs-app-router-patterns.md) |
| React state management (Redux Toolkit, Zustand, Jotai, React Query, server state) | [references/react-state-management.md](references/react-state-management.md) |

## Core decisions

- **Server Components first** — only opt into client (`'use client'`) when you actually need state/effects/handlers.
- **State management hierarchy:** local `useState` → context only for true app-wide concerns → React Query for server state → Zustand for client-shared state → Redux only if the codebase is already there.
- **File-system as router** — App Router conventions are load-bearing; respect them.

For frontend design quality beyond patterns, see [anthropic/frontend-design](../../anthropic/frontend-design/SKILL.md).

Files in this skill

  • SKILL.md1.6 KB
  • references/next-best-practices.md3.9 KB
  • references/nextjs-app-router-patterns.md13.3 KB
  • references/react-state-management.md11.5 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…