Frontend Engineering Skill — Quick Reference

This skill equips frontend engineers with execution-ready patterns for building modern web applications with Next.js, React, TypeScript, and Tailwind CSS. Apply these patterns when you need component design, state management, routing, forms, data fetching, animations, accessibility, or production-grade UI architectures.

Modern Best Practices (December 2025): Next.js 16 with Turbopack (stable, default bundler), middleware.ts → proxy.ts migration (clarifies network boundary, runs on Node.js runtime), React 19.2 with Server Components, Actions, Activity component, and useEffectEvent hook, enhanced ISR/SSR/SSG, partial prerendering (PPR), stable caching APIs (cacheLife, cacheTag, updateTag), Zustand/Recoil as Redux alternatives, TanStack Query (React Query) for server-state, TypeScript 5.9+ strict mode enforcement (TypeScript 7 "Corsa" Go-based compiler in preview), satisfies operator, Tailwind CSS v4 (CSS-first config, 5x faster builds), Vitest for testing, and progressive enhancement patterns.

Next.js 16 Breaking Changes: Upgrade Guide

Quick Reference

When to Use This Skill

Use this skill when you need:

• Next.js 16 application architecture and setup (Turbopack stable, App Router, React 19)
• React component design and patterns (functional components, hooks, Server Components)
• TypeScript type definitions for UI (strict mode, satisfies operator, discriminated unions)
• Tailwind CSS styling and responsive design (utility-first, dark mode variants)
• shadcn/ui component integration (Radix UI + Tailwind)
• Form handling and validation (React Hook Form + Zod, Server Actions)
• State management (Zustand/Recoil for client state, TanStack Query for server state)
• Data fetching (Server Components, TanStack Query/SWR, Server Actions, streaming)
• Authentication flows (NextAuth.js, Clerk, Auth0)
• Route handling and navigation (App Router, parallel routes, intercepting routes)
• Performance optimization (Turbopack, Image optimization, code splitting, ISR/SSR/SSG)
• Accessibility (WCAG 2.2, ARIA, keyboard navigation, screen reader testing) https://www.w3.org/TR/WCAG22/
• Animation and transitions (Framer Motion, Tailwind animations)
• Testing (Vitest for unit tests, Testing Library for components, Playwright for E2E)

Decision Tree: Frontend Framework Selection

Project needs: [Framework Choice]
    ├─ React ecosystem?
    │   ├─ Full-stack + SEO → Next.js 16 (App Router, React 19.2, Turbopack stable)
    │   ├─ Progressive enhancement → Remix (loaders, actions, nested routes)
    │   └─ Client-side SPA → Vite + React (fast dev, minimal config)
    │
    ├─ Vue ecosystem?
    │   ├─ Full-stack + SSR → Nuxt 4 (auto-imports, Nitro server, file-based routing)
    │   └─ Client-side SPA → Vite + Vue 3.5+ (Composition API, script setup)
    │
    ├─ Angular preferred?
    │   └─ Enterprise app → Angular 21 (zoneless change detection, esbuild, signals)
    │
    ├─ Performance-first?
    │   └─ Minimal JS bundle → SvelteKit 2.49+ (Svelte 5.45 runes, compiler magic)
    │
    ├─ Component library?
    │   ├─ Headless + customizable → shadcn/ui + Radix UI + Tailwind
    │   ├─ Material Design → MUI (Material-UI)
    │   └─ Enterprise UI → Ant Design
    │
    ├─ State management?
    │   ├─ Server data → TanStack Query/SWR (caching, sync)
    │   ├─ Global client state → Zustand (lightweight) or Recoil (React-first)
    │   ├─ Complex state logic → XState (state machines)
    │   └─ URL-based state → useSearchParams (shareable filters)
    │
    ├─ Styling approach?
    │   ├─ Utility-first → Tailwind CSS v4 (CSS-first config, 5x faster builds)
    │   ├─ CSS-in-JS → Styled Components or Emotion
    │   └─ CSS Modules → Built-in CSS Modules
    │
    └─ Testing strategy?
        ├─ Unit/Component → Vitest + Testing Library (fast, modern)
        ├─ E2E → Playwright (cross-browser, reliable)
        └─ Visual regression → Chromatic or Percy

Framework Selection Factors:

• Team experience: Choose what the team knows or can learn quickly
• SSR/SSG requirements: Next.js, Nuxt, Remix for server-side rendering
• Performance constraints: SvelteKit for minimal JS, Next.js for optimization
• Ecosystem maturity: React has largest ecosystem, Vue/Angular are also mature

See resources/ for framework-specific best practices.

Next.js 16 Migration: middleware.ts → proxy.ts

Breaking Change (Dec 2025): The middleware convention is renamed to proxy in Next.js 16.

Why the Change?

• Clarity: "Proxy" better describes the network boundary behavior (runs in front of the app)
• Runtime: proxy.ts runs on Node.js runtime (not Edge by default)
• Avoid confusion: Prevents confusion with Express.js middleware patterns

Migration Steps

# 1. Run the codemod (recommended)
npx @next/codemod@canary upgrade latest

# 2. Or manually rename
mv middleware.ts proxy.ts

// Before (Next.js 15)
export function middleware(request: Request) {
  // ... logic
}

// After (Next.js 16)
export function proxy(request: Request) {
  // ... logic
}

// next.config.ts - Update config option
const nextConfig: NextConfig = {
  skipProxyUrlNormalize: true, // was: skipMiddlewareUrlNormalize
}

Runtime Considerations

⚠️ Keep using middleware.ts if you need Edge Runtime. The proxy convention does NOT support Edge.

Related Changes in Next.js 16

• Async Request APIs: cookies(), headers(), params, searchParams are now async
• Turbopack default: Remove --turbopack flags from scripts
• Parallel routes: Require explicit default.js files
• Image changes: domains deprecated (use remotePatterns), new default cache TTL

React 19.2 Patterns (Dec 2025)

Security Note (React Server Components)

• Track and patch React Server Components vulnerabilities quickly (RCE/DoS/source exposure advisories in Dec 2025) https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components and https://react.dev/blog/2025/12/11/denial-of-service-and-source-code-exposure-in-react-server-components

Partial Prerendering (PPR)

Pre-render static shell, stream dynamic content.

// Next.js 16 with PPR enabled
// next.config.js
export default {
  experimental: {
    ppr: true, // Enable Partial Prerendering
  },
};

// Page component
export default async function Page() {
  return (
    <main>
      <Header /> {/* Static: pre-rendered */}
      <Suspense fallback={<Skeleton />}>
        <DynamicContent /> {/* Dynamic: streamed */}
      </Suspense>
      <Footer /> {/* Static: pre-rendered */}
    </main>
  );
}

use() Hook Pattern

Promise resolution in components with Suspense.

// Before: useEffect + useState
const [data, setData] = useState(null);
useEffect(() => {
  fetchData().then(setData);
}, []);

// After: use() hook (React 19+)
const data = use(fetchDataPromise);

Error Boundary Patterns

'use client';

import { ErrorBoundary } from 'react-error-boundary';

function ErrorFallback({ error, resetErrorBoundary }) {
  return (
    <div role="alert">
      <p>Something went wrong:</p>
      <pre>{error.message}</pre>
      <button onClick={resetErrorBoundary}>Try again</button>
    </div>
  );
}

export default function App() {
  return (
    <ErrorBoundary FallbackComponent={ErrorFallback}>
      <MyComponent />
    </ErrorBoundary>
  );
}

Performance Budgets

Optional: AI/Automation Extensions

Note: AI design and development tools. Skip if not using AI tooling.

AI Design Tools

AI-Powered Testing

Optional Related Skills

• ../ai-llm/SKILL.md — Optional: AI-powered features and LLM integration patterns

Navigation

Resources (Framework-specific best practices)

• resources/fullstack-patterns.md — Universal patterns: Server vs client components, data fetching, TypeScript
• resources/vue-nuxt-patterns.md — Vue 3 Composition API, Nuxt 3, Pinia state management
• resources/angular-patterns.md — Angular 18 standalone components, signals, RxJS patterns
• resources/svelte-sveltekit-patterns.md — Svelte 5 runes, SvelteKit loaders/actions
• resources/remix-react-patterns.md — Remix loaders, actions, progressive enhancement
• resources/vite-react-patterns.md — Vite setup, React hooks, TanStack Query
• resources/artifacts-builder.md — React/Tailwind/shadcn artifact workflow and bundling to single HTML
• README.md — Folder overview and usage notes
• data/sources.json — 106 curated resources for all frameworks (Next.js, Vue/Nuxt, Angular, Svelte, Remix, Vite)
• Shared checklist: ../software-clean-code-standard/templates/checklists/frontend-performance-a11y-checklist.md

Shared Utilities (Centralized patterns — extract, don't duplicate)

• ../software-clean-code-standard/utilities/error-handling.md — Effect Result types, correlation IDs
• ../software-clean-code-standard/utilities/config-validation.md — Zod 3.24+, Valibot for client validation
• ../software-clean-code-standard/utilities/logging-utilities.md — Structured logging patterns
• ../software-clean-code-standard/utilities/testing-utilities.md — Vitest, MSW v2, factories, fixtures
• ../software-clean-code-standard/utilities/observability-utilities.md — OpenTelemetry SDK, tracing, metrics
• ../software-clean-code-standard/resources/clean-code-standard.md — Canonical clean code rules (CC-*) for citation

Templates (Production-ready starters by framework)

• Next.js: templates/nextjs/template-nextjs-tailwind-shadcn.md
• Vue/Nuxt: templates/vue-nuxt/template-nuxt3-tailwind.md
• Angular: templates/angular/template-angular21-standalone.md
• Svelte/SvelteKit: templates/svelte/template-sveltekit-runes.md
• Remix: templates/remix/template-remix-react.md
• Vite + React: templates/vite-react/template-vite-react-ts.md

Related Skills

• ../dev-api-design/SKILL.md — REST/GraphQL API patterns, OpenAPI, versioning
• ../git-workflow/SKILL.md — Git branching, PR workflow, commit conventions
• ../software-backend/SKILL.md — Backend API development, Node.js, Prisma, authentication
• ../software-architecture-design/SKILL.md — System design, scalability, microservices patterns
• ../software-code-review/SKILL.md — Code review best practices, PR workflow
• ../ops-devops-platform/SKILL.md — Deployment, CI/CD, containerization, Kubernetes
• ../data-sql-optimization/SKILL.md — Database design, SQL optimization, Prisma/Drizzle

Operational Playbooks

• resources/operational-playbook.md — Framework-specific architecture patterns, TypeScript guides, and security/performance checklists