Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →aiskillstore/next-js-patterns
Best practices and patterns for Next.js App Router, Server Actions, and Routing in this project.
Passed 22 of 22 test cases with the skill, and 21 of 22 without it.
1 fixed21 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
Where should optimized font classes or CSS variable references be applied in the layout HTML structure?
| Checked | Without skill | With skill |
|---|---|---|
| Applies the font variable or class to the body tag in app/layout.tsx | Missed | Passed |
The instructions your model reads when the skill loads.
We use the Next.js 15 App Router located in app/.
app/[route]/page.tsx"use client" directive at the top for components requiring state (useState, useEffect) or browser APIs. otherwise default to Server Components.app/layout.tsx (Root), app/[route]/layout.tsx (Nested).Link from next/link for internal navigation.useRouter from next/navigation for programmatic navigation (inside Client Components).import Link from "next/link";
import { useRouter } from "next/navigation";
// Link
<Link href="/dashboard">Dashboard</Link>
// Router
const router = useRouter();
router.push('/login');
await fetch() or DB calls.useEffect or SWR/TanStack Query (if added later). Currently using standard fetch in useEffect.next/font/google (e.g., Poppins) in app/layout.tsx.body className.export const metadata: Metadata = { ... } in page.tsx or layout.tsx for SEO.test cases passed, vs 21 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.