cc-skill:nextjs-app-router-conventions

Claude Code skill · anthropic · active

last 30 days

0 calls

0 of 30 days active

explain like I am new to this

what it does

This skill guides you on how to organize and build Next.js routes, pages, and API endpoints the way Jay does it. It tells you where files go, which parts should run on the server versus the browser, and when to use Server Actions instead of API routes.

who it is for

A developer building web pages or API endpoints in a Next.js project.

when it fires

When you mention Next.js routes, App Router, page.tsx, layout.tsx, server actions, API routes, route handlers, loading states, or error boundaries.

say something like

"How do I set up a new authenticated page in the app directory?"
"Should this be a Server Action or an API route?"
"Where should I put my component files?"

what you might get back

Create your page at app/(app)/dashboard/page.tsx as a server component. Fetch your Supabase data there with the service client. For the interactive parts (like a button that filters), split that into a separate client component in components/dashboard-filters.tsx and import it into your page. Keep pages server-only unless you need browser APIs.

how to know it worked

You know it worked because you get clear guidance on file structure, which components should have 'use client' at the top, and whether to use a Server Action or API route for your specific use case.

is this skill working for me

never used

cloud runs

0 deployments

local fires

Claude Code (optional)

posts published

from drafts

attributed

$0.00

signups + revenue

Deploy this skill as a cloud automation to put it to work — runs on a schedule, dispatches output to Telegram or email, and logs every result here.

How this performs

Cloud-automation runs, real outputs, and feedback.

No cloud runs yet for this skill.

Once you deploy it (above), every run will show up here with the actual output, exact cost, and a thumbs button so you can rate quality over time.

what this is

Claude Code skill at /Users/olanrewajukareem/.claude/skills/nextjs-app-router-conventions/SKILL.md. Auto-triggered by description matching when you type in Claude Code, OR embedded into agent system prompts (LeadFlow framework skills are wired this way). Auto-synced from disk every 6h via launchd.

Use this skill when building Next.js routes, pages, layouts, server components, server actions, or API routes in any Jay project. Triggers on "Next.js route", "App Router", "page.tsx", "layout.tsx", "server action", "API route", "route handler", "loa

Local Claude Code use (optional)

Install the SKILL.md file locally so this skill is available the next time you open Claude Code on your Mac. Most users skip this and just use cloud deployments above.

Install on your machine

Save this skill to ~/.claude/skills/nextjs-app-router-conventions/SKILL.md so Claude Code auto-loads it whenever its description matches your prompt.

30-day activity

never used

2026-04-03today

cost model

unitincluded

capabilities

{
  "source": "global",
  "description": "Use this skill when building Next.js routes, pages, layouts, server components, server actions, or API routes in any Jay project. Triggers on \"Next.js route\", \"App Router\", \"page.tsx\", \"layout.tsx\", \"server action\", \"API route\", \"route handler\", \"loading state\", or \"error boundary\". Applies Jay's App Router conventions for component placement, server vs client splits, and when to use which primitive."
}

how it gets called

{
  "method": "embed_in_prompt",
  "skill_path": "/Users/olanrewajukareem/.claude/skills/nextjs-app-router-conventions/SKILL.md"
}

This tool has never been called in the last 30 days.

That means either: (a) the system has not had a task that matched its strengths, (b) a more cost-effective alternative was picked by the router, or (c) the related automation is toggled OFF on /automations. The Recommender reviews idle tools weekly and may suggest killing it.