npx claudepluginhub xoai/sageThis skill uses the workspace's default tool permissions.
**Layer 2 — Framework Pack**
Provides Next.js 14+ App Router patterns for Server Components, streaming, parallel and intercepting routes, data fetching, caching, and Server Actions. Use for building new apps, migrations from Pages Router, SSR/SSG.
Provides patterns for Next.js 14+ App Router including Server Components, streaming, parallel routes, data fetching, caching, and Server Actions. Use for new apps, migrations, and full-stack features.
Guides Next.js app development with App Router, Server Components, file-system routing, data fetching, caching, revalidation, Server Actions, and file conventions.
Share bugs, ideas, or general feedback.
Layer 2 — Framework Pack
Next.js 14/15 App Router patterns. Server components, data fetching, caching, server actions, and the specific mistakes agents make from Pages Router training data contamination.
Next.js is where the "judgment not knowledge" principle matters most. The framework underwent a fundamental paradigm shift from Pages Router to App Router. Server components changed how data fetching works. Server actions changed how mutations work. The caching model changed between Next.js 14 and 15.
LLMs trained on pre-App-Router content produce code that technically runs but
uses wrong patterns — getServerSideProps in App Router projects, useEffect
for data fetching that should happen on the server, 'use client' on every
component because the agent doesn't understand the server-first model.
This pack establishes the App Router mental model as the default and explicitly corrects the most common Pages Router contamination patterns.
| Type | Files | Coverage |
|---|---|---|
| Patterns | 7 | Server components, data fetching, routing/layouts, server actions, caching, middleware, metadata |
| Anti-patterns | 5 | Pages Router patterns, use-client-everywhere, useEffect data fetching, client-side routing, wrong caching |
| Constitution | 1 | 6 Next.js-specific principles |
| Gate | 1 | Next.js pattern compliance check |
When installed alongside react, this pack overrides React's
data-fetching pattern. In Next.js, data fetching happens in server components,
not via TanStack Query in client components (unless you specifically need
client-side real-time data).
Server-first. Components are server components by default. They run on the
server, have direct access to databases and file systems, and ship zero JavaScript
to the browser. Only add 'use client' when you need interactivity (event handlers,
hooks, browser APIs). Most components (70-90% in a typical app) should remain
server components.