tech-nextjs
Skill1 starsChanged 28 days agoMITView on GitHub
Technology skill loaded when working in a Next.js environment.
In this repository29 other files it gives its agents.
- exec-accessibilitySkill
- exec-architectureSkill
- exec-code-reviewSkill
- exec-debuggingSkill
- exec-documentationSkill
- exec-performanceSkill
- exec-refactoringSkill
- exec-repo-patternsSkill
- exec-securitySkill
- exec-testingSkill
- exec-ui-uxSkill
- exec-verificationSkill
- tech-dockerSkill
- tech-flutterSkill
- tech-goSkill
- tech-graphqlSkill
- tech-kotlinSkill
- tech-nodeSkill
- tech-postgresSkill
- tech-pythonSkill
- tech-reactSkill
- tech-rustSkill
- tech-swiftSkill
- tech-tailwindSkill
- tech-typescriptSkill
- tech-vueSkill
- linear-spanks-gitSkill
- linear-spanksSkill
- linear-workflowSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
When working with Next.js, strictly differentiate between server and client environments:
- Very specific: line 13
RSC vs Client Components: Default to React Server Components (RSC).
- Very specific: line 17
Image Optimization: Always use the next/image component for remote and local images to prevent layout shift and optimize load times.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Next.js Best Practices
Apply this skill after inspecting repository conventions and supported versions. Treat its rules as defaults unless they protect a concrete safety property; preserve an established project pattern when it conflicts, and record the reason in the implementation plan.
When working with Next.js, strictly differentiate between server and client environments:
- RSC vs Client Components: Default to React Server Components (RSC). Only add
"use client"when you need interactivity (hooks, event listeners) or browser APIs. - Data Fetching: Fetch data on the server. Avoid using
useEffectfor data fetching unless absolutely necessary (e.g., highly dynamic client-only state). - Routing Paradigm: Determine if the project uses the App Router (
app/) or Pages Router (pages/). Do not mix their routing and fetching patterns. - Caching: Understand Next.js caching behavior (
fetchcache, revalidation). Explicitly opt-out of caching if data must be real-time. - Image Optimization: Always use the
next/imagecomponent for remote and local images to prevent layout shift and optimize load times.
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.