Skip to content
Skills Library
Programming · Building & coding

react-nextjs

/react-nextjs

Build and review React and Next.js (App Router) apps: components, server vs client, data fetching, state, forms, performance, testing. Use when the chosen frontend stack is React or Next.js.

Licence
MIT
Last repository change
11.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 11.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Build and review React and Next.js (App Router) apps: components, server vs client, data fetching, state, forms, performance, testing. Use when the chosen frontend stack is React or Next.js.

Original author description

Build and review React and Next.js (App Router) apps: components, server vs client, data fetching, state, forms, performance, testing. Use when the chosen frontend stack is React or Next.js.

How it works

  1. Components
  2. Next.js App Router
  3. State & forms
  4. Performance
  5. Security
  6. Testing
  7. Review checklist
Original SKILL.md headings · 31 lines, 406 words
SKILL.md preview
---
name: react-nextjs
description: "Build and review React and Next.js (App Router) apps: components, server vs client, data fetching, state, forms, performance, testing. Use when the chosen frontend stack is React or Next.js."
license: MIT
metadata:
  version: "1.0.0"
---

# React & Next.js

React counterpart to `angular-*` skills. Quality bar for UX/a11y is `ui-design-a11y`; security: `secure-by-design-coding` (XSS, CSRF, auth).

## Components
- Function components + hooks; small, single-purpose, composition over props explosion. TypeScript strict; props typed; no `any`.
- Derive state instead of syncing it (compute during render); `useEffect` is for synchronizing with external systems only, not for data derivation or event handling. Keys stable and unique (never array index for dynamic lists).
- Memoization (`useMemo`, `useCallback`, `React.memo`) only after profiling; prefer fixing structure. Check whether the React Compiler is enabled before hand-memoizing.

## Next.js App Router
- **Server Components by default**; add `"use client"` only for interactivity, browser APIs or client state, and push it to the leaves. Never import server-only code (secrets, DB) into client modules (`server-only` package).
- Data: fetch in Server Components (`async` component) close to where it is used; parallelize with `Promise.all`; stream with `Suspense` + `loading.tsx`; caching/revalidation explicit (`revalidate`, tags, `revalidateTag`) and verified for the installed major version (caching defaults changed across releases - read the docs for your version).
- Mutations: Server Actions or route handlers; **validate input with Zod on the server**, check authn/authz inside every action, return typed results, handle errors with `error.tsx` and `useActionState`.
- Routing: layouts for shared UI, route groups, parallel/intercepting routes only when needed, `generateMetadata` for SEO, `next/image` and `next/font`, dynamic imports for heavy client widgets.

## State & forms
Server state via TanStack Query (or RSC + revalidation); local state with `useState`/`useReducer`; global client state sparingly (Zustand/Context for truly global, split contexts to avoid rerenders). Forms: React Hook Form + Zod resolver or native form + Server Actions with progressive enhancement; accessible labels and errors.

## Performance
Measure first (React Profiler, Lighthouse, Web Vitals LCP/INP/CLS). Ship less JS: server rendering, code-splitting, tree-shakeable imports, avoid large client libs. Virtualize long lists; debounce inputs; reserve image space; avoid layout thrash.

## Security
No `dangerouslySetInnerHTML` without sanitization (DOMPurify); validate and escape URLs (`javascript:`); CSP via middleware/headers; httpOnly+SameSite cookies for sessions; CSRF protection for cookie auth; env vars: only `NEXT_PUBLIC_*` reach the browser.

## Testing
Vitest/Jest + React Testing Library (query by role/label, test behavior), MSW for network, Playwright for critical journeys + axe a11y checks, Storybook for component states.

## Review checklist
Server/client boundary minimal - no effect-driven derived state - server-side validation and authz in actions - Suspense/error boundaries present - bundle size checked - a11y checks pass - tests cover user-visible behavior.

Versions

RepositoryScoreLicence
This page · swap-cameroon/kuro-antigravity-config90MIT
j4flmao/agent-skills95MIT
helx0071/skillsmo90MIT

Database snapshot: 13.11.2026 · package version b812801e8dd2 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90nextjs-react-expert
    Advanced Next.js (App Router) and React engineering for architecture, server/client boundaries, data fetching, caching, performance, and production operations. Use when building, reviewing, or debugging modern React/Next.js applications.
  • 90NextJS
    Builds Next.js apps with App Router — server components, caching, Server Actions, auth, deployment. Use for any Next.js routing, data, cache, or build issue.
  • 100react-frontend
    React, TypeScript, and Next.js patterns for frontend development. Use when building React components, managing state, fetching data, optimizing performance, or working with Next.js App Router. Covers React 18-19, hooks, Server Components, and type-safe patterns.
  • 100react-development
    Use when implementing or reviewing React components, hooks, state ownership, forms, rendering performance, error boundaries, or component tests. Use nextjs-app-router for Next.js server boundaries and ux-content-strategy for product content systems.
  • 95nextjs-app-router-patterns
    Master Next.js 14+ App Router with Server Components, streaming, parallel routes, and advanced data fetching. Use when building Next.js applications, implementing SSR/SSG, or optimizing React Server Components.
  • 90nextjs-modern
    Build, migrate, and debug Next.js 16 App Router applications with React 19, Server Components, Server Actions, explicit caching, and production deployment. Use when implementing Next.js routes, upgrading to the latest stable Next.js, or fixing rendering and cache behavior.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.