Skip to content
Agentmart
Submit a tool

adapter-nextjs

Next.js adapter guidance for App Router structure, route handlers, rendering boundaries, and middleware constraints.

Skill by JahacksV1

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/jahacksv1-adapter-nextjs

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Next.js adapter guidance for App Router structure, route handlers, rendering boundaries, and middleware constraints. Use when working in Next.js projects.

Use cases: frontend

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/adapter-nextjs

What's inside

Skill name
adapter-nextjs
Description
Next.js adapter guidance for App Router structure, route handlers, rendering boundaries, and middleware constraints. Use when working in Next.js projects.
License
MIT
Instructions
25 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Adapter: Next.js

## Focus

- App routing conventions and server/client boundaries.
- API route handler placement and behavior.
- Middleware and deployment caveats.

## Starter Checklist

- [ ] Route and component placement follows project conventions.
- [ ] Server/client component boundaries are intentional.
- [ ] API handlers include validation and auth where required.
- [ ] Environment variable usage aligns with public vs server-only rules.

## Implementation Pattern

Evidence: 4-repo field extraction — see `.ai/MERGE_REPORT.md`. Router choice itself was split
2/2 between App Router and Pages Router across repos, but consistency-with-existing-choice was
unanimous.

- Whichever routing system the project already uses (App Router or Pages Router) is the one to
  keep using. Never introduce the other router style ad hoc, and never migrate route-by-route
  without an explicit decision to do so.

From JahacksV1/day-one-agent-kit, MIT.

More from JahacksV1/day-one-agent-kit

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Jul 13, 2026 (3 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from JahacksV1

Cite this page

adapter-nextjs skill. Agent Mart. https://agentmart.dev/skills/jahacksv1-adapter-nextjs (last updated 2026-10-24)