nextjs
Skill2 starsChanged 6 days agoMITView on GitHub
Next.js framework guidance for routing, typegen, typed routes, build tooling, async Request APIs, configuration, and Next.js 15.5/16 migrations. Use for version-specific Next.js implementation or review after resolving the target package. Not for standalone React APIs or generic JS tooling. Output: target-scoped guidance, migration traps, and verification evidence.
39 other projects use a version of this.
Adopted by
Most recently taken up by
- RuneStone-Tech/optimize-anythingtheir own version, first seen Nov 8, 2026
- LuisSambrano/antigravity-configtheir own version, first seen Nov 8, 2026
- davidvornholt/mail-mcptheir own version, first seen Nov 5, 2026
- davidvornholt/mailboxtheir own version, first seen Nov 5, 2026
- thongdn-it/react-agent-skillstheir own version, first seen Nov 1, 2026
- Firzus/agent-skillstheir own version, first seen Oct 23, 2026
Used with
Projects with it also use nuqs, msw and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
thongdn-itSkillnuqs
nuqs (type-safe URL query state) best practices for Next.js applications. This skill should be used when writing, reviewing, or refactoring code that uses nuqs for URL state management. Triggers on tasks involving useQueryState, useQueryStates, search params, URL state, query parameters, nuqs parsers, or Next.js routing with state.
Also in 3 projects that use this
thongdn-itSkillmsw
MSW (Mock Service Worker) best practices for API mocking in tests (formerly test-msw). This skill should be used when setting up MSW, writing request handlers, or mocking HTTP APIs. This skill does NOT cover general testing patterns (use test-vitest or test-tdd skills) or test methodology.
Also in 3 projects that use this
hfzarslanSkillfastapi
FastAPI web framework skill for building REST APIs and web applications. Use when building FastAPI projects, creating APIs, adding features like database integration or authentication, structuring FastAPI applications, or when users ask to build/modify FastAPI code. Triggers include requests to create APIs, add endpoints, implement CRUD operations, set up authentication, integrate databases, add testing, or deploy FastAPI applications.
Also in 4 projects that use this
MicrosoftSkilltypescript
TypeScript best practices for this monorepo. Use this skill when: (1) writing new TypeScript code, (2) reviewing TypeScript code, (3) working with API responses, fetch calls, or JSON parsing, (4) adding or modifying types and interfaces.
Also in 5 projects that use this
klauswgSkillshadcn-ui
Expert guidance for integrating and building applications with shadcn/ui components, including component discovery, installation, customization, and best practices.
Also in 4 projects that use this
nilecuiSkillarchitecture-patterns
Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use when architecting complex backend systems or refactoring existing applications for better maintainability.
Also in 3 projects that use this
- +3 more from thongdn-it
Other versions39 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 39
- openai/plugins★ 7.8ksame name
- udecode/better-convex★ 452same name
- leonvanzyl/agentic-coding-starter-kit★ 447same name
- kid-sid/claude-spellbook★ 190same name
- faqndo97/ai-skills★ 33same name
- nimadorostkar/Claude-Skills-collection★ 33same name
- PyModel/react-frontend-skills★ 23same name
- G1Joshi/Agent-Skills★ 15same name
- ulpi-io/browse★ 15same name
- wpank/ai★ 11same name
29 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository39 other files it gives its agents.
- AGENTS.mdAGENTS.md
- change-verdictSkill
- code-simplifySkill
- code-traceSkill
- create-prSkill
- deploy-listSkill
- doc-maintainSkill
- feature-verifySkill
- flow-driveSkill
- flow-guideSkill
- git-smart-commitSkill
- git-worktreeSkill
- harness-setupSkill
- issue-analyzeSkill
- js-static-checksSkill
- laravelSkill
- legacy-characterization-testsSkill
- library-authorSkill
- merge-prepSkill
- module-designSkill
- openspec-artifact-guardSkill
- opsx-apply-resumeSkill
- phpSkill
- phpunitSkill
- precommitSkill
- project-auditSkill
- project-briefSkill
- proposal-analyzeSkill
- pr-summarySkill
- pythonSkill
- reactSkill
- release-creatorSkill
- repo-intakeSkill
- repo-verifySkill
- swiftSkill
- tdd-workflowSkill
- ui-ux-verifySkill
- vue-2-notesSkill
- yii1Skill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 35 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Target: Read target-selection.md, then resolve the package/subproject and Next.js version from explicit task inputs and that package's …
“Common” is measured: kept by at least 6 in 10 of the 35 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Next.js
Describe the framework task directly, for example: “Review build scripts in
apps/store” or “Migrate apps/store from Next.js 15.5 to Next.js 16.”
Optional review or migrate prefixes express the same tasks.
- Target. Read target-selection.md, then resolve the package/subproject and Next.js version from explicit task inputs and that package's evidence. Complete its clarification gate before reading a version resource or taking a version-dependent action. Finish this step with a read plan naming the package, requested task, compatibility target, and allowed version resource(s). Complete the plan before issuing any read that includes a version resource.
- Load. For a resolved Next.js 15.5 target, read 15.5.md.
For Next.js 16, read 16.md. Read both only for an explicit
15.5-to-16 migration or multiple resolved targets, grouping notes by target.
Execute the read plan only. For a single-target compatibility review, an
explicit override selects exactly one version resource; the installed or
manifest version is evidence, not permission to read its resource. A review
targeting 16.0.10 with a 15.5.9 manifest reads only
16.md. Source-plus-target loading requires a requested migration comparison with both roles resolved. - Apply. Match framework APIs, environment floors, build configuration, and migration traps to the selected target. Confirm the target package's React compatibility separately before any React-dependent advice. Standalone React implementation belongs to the separate React family; a Next.js task can finish from this directory without finding a peer skill.
- Verify. Report the package path, target/version evidence (including an
intentional override), selected references, recommendations or applied
changes, and actual checks. Distinguish guidance from verified runtime
behavior; report unavailable checks as
NOT_RUN.
Resource boundary
Resolve bundled links relative to this skill's real directory. Before loading
a selected resource, verify that it exists and its real path stays within this
directory. Missing, absolute, traversal, or symlink-escaping required resources
return BLOCKED_RESOURCE_MISSING; stop the dependent action without searching
the checkout, predecessor skills, sibling skills, or environment for a copy.
Target project manifests and source files are explicit task inputs, not bundled
fallback resources.
Output
Return target-scoped Next.js guidance or changes, the relevant migration traps, and verification evidence. For unresolved targets, return one grouped clarification and wait; provide no version-specific recommendation yet.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

