Skip to content
Agentmart
Submit a tool

nextjs

Build and maintain modern Next.js applications with TypeScript, App Router conventions, clear server/client boundaries, accessible UI, and production…

Skill by PHENOMVALENCE

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/phenomvalence-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

Build and maintain modern Next.js applications with TypeScript, App Router conventions, clear server/client boundaries, accessible UI, and production performance.

Use cases: design, frontend, backend

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/nextjs

What's inside

Skill name
nextjs
Description
Build and maintain modern Next.js applications with TypeScript, App Router conventions, clear server/client boundaries, accessible UI, and production performance.
License
MIT
Instructions
22 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Next.js Engineering

## Workflow
1. Inspect Next.js/React/TypeScript versions, package manager, App/Pages Router, styling system, data layer, auth, deployment target, and tests.
2. Prefer Server Components by default in App Router projects; use Client Components only where browser state/effects/interactivity require them.
3. Keep data fetching close to the server boundary when practical and avoid unnecessary client waterfalls.
4. Use route handlers/server actions according to the project's established architecture.
5. Validate external input and enforce authorization on the server.
6. Keep components focused; extract reusable primitives only when there is genuine reuse.
7. Use typed API/domain boundaries and avoid `any` unless justified.
8. Handle loading, empty, error, and not-found states explicitly.
9. Optimize images, fonts, bundle size, caching, and rendering based on measured needs.
10. Verify accessibility and responsive behavior.
11. Run configured lint, typecheck, tests, and production build.

## Rules
- Do not move secrets into client bundles.
- Do not mark large trees `use client` merely for convenience.
- Preserve SEO/metadata behavior for public pages.
- Avoid duplicated fetching and hydration-heavy patterns when server rendering is sufficient.

From PHENOMVALENCE/engineering-agent-skills, MIT.

More from PHENOMVALENCE/engineering-agent-skills

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Sep 16, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

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

More from PHENOMVALENCE

Cite this page

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