All plugins

Next.js v16 operator

10 skills

Next.js 16 App Router, Server and Client Components, Cache Components, mutations, handlers, metadata, deployment, integrations, reference, and troubleshooting.

View this plugin on GitHub
any skills-format agent
$ npx skills add rj11io/11ai --skill 11ai-operator-nextjs-v16-app-router --skill 11ai-operator-nextjs-v16-cheatsheet --skill 11ai-operator-nextjs-v16-data-cache --skill 11ai-operator-nextjs-v16-environment --skill 11ai-operator-nextjs-v16-integrations --skill 11ai-operator-nextjs-v16-metadata-deployment --skill 11ai-operator-nextjs-v16-mutations-handlers --skill 11ai-operator-nextjs-v16-server-client --skill 11ai-operator-nextjs-v16-setup --skill 11ai-operator-nextjs-v16-troubleshooting
claude code
$ claude plugin install 11ai-operator-nextjs-v16@11ai
codex
$ codex plugin add 11ai-operator-nextjs-v16@11ai

First time? Add the marketplace once with claude plugin marketplace add rj11io/11ai or codex plugin marketplace add rj11io/11ai, then install any plugin from it.

11ai-operator-nextjs-v16-app-router

Operate Next.js App Router layouts, pages, route segments, groups, dynamic parameters, loading, error, not-found, parallel routes, intercepting routes, and navigation. Use when adding or moving routes, fixing layouts or navigation, or implementing route-specific loading and errors.

11ai-operator-nextjs-v16-cheatsheet

Look up Next.js commands, project structure, rendering patterns, and focused operations across app router, server and client components, data and caching, mutations and route handlers, metadata and deployment. Use when the user wants a concise reference instead of a guided workflow.

11ai-operator-nextjs-v16-data-cache

Operate Next.js server data fetching, request memoization, use cache, cache tags and lifetimes, revalidation, streaming, Suspense, and dynamic request APIs. Use when adding data access, fixing stale or uncached results, choosing rendering behavior, or invalidating cached output.

11ai-operator-nextjs-v16-environment

Inspect the installed Next.js versions, package manager, renderer or router mode, source tree, build configuration, scripts, and target environments without changing anything. Use before Next.js work, when conventions are unknown, or when the user asks what is configured.

11ai-operator-nextjs-v16-integrations

Connect Next.js to styling, data sources, tests, browser and server runtimes, build tools, CI, observability, and deployment while preserving component and execution boundaries. Use when Next.js crosses another subsystem or must behave consistently through production.

11ai-operator-nextjs-v16-metadata-deployment

Operate Next.js metadata, icons, Open Graph images, robots and sitemaps, image and font assets, environment variables, production builds, previews, and deployment configuration. Use when adding SEO metadata, fixing assets, preparing production, or changing runtime and deployment behavior.

11ai-operator-nextjs-v16-mutations-handlers

Build Next.js Server Functions, form actions, Route Handlers, request validation, authorization, cookies, redirects, revalidation, and error responses. Use when adding mutations or API endpoints, handling forms, setting cookies, or securing server actions and handlers.

11ai-operator-nextjs-v16-server-client

Design Next.js Server and Client Component boundaries, serialization, data access, interactivity, providers, browser APIs, and composition. Use when placing use client, fixing hydration, moving data access, or reducing client JavaScript.

11ai-operator-nextjs-v16-setup

Install and configure Next.js from zero with project-local dependencies, explicit rendering and runtime boundaries, source structure, baseline checks, and one verified feature. Use when a project has no Next.js setup or the user explicitly asks to initialize it.

11ai-operator-nextjs-v16-troubleshooting

Diagnose Next.js failures involving versions, rendering, state, hydration, routing, caching, async behavior, build output, tests, integrations, and performance without masking the original error. Use when Next.js fails a check, behaves differently across environments, or renders unexpected output.