stack-nextjs
Skill0 starsChanged 2 months agoMITView on GitHub
Optional guidance for Next.js repositories, using their existing router/rendering/data-fetching conventions and project-native validation without making Next.js a dependency of this project.
In this repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- elixir-docsSkill
- feature-planSkill
- independent-reviewSkill
- multi-repo-changeSkill
- package-readinessSkill
- parallel-deliverySkill
- safe-refactorSkill
- security-reviewSkill
- stack-elixirSkill
- stack-phoenix-liveviewSkill
- stack-rustSkill
- stack-svelteSkill
- systematic-debuggingSkill
- technical-writingSkill
- ui-validationSkill
- unslopSkill
- worktree-integrationSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
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 8
Use this skill only in repositories that already use Next.js.
- Distinctive: line 14
Follow the repository's existing App Router / Pages Router conventions rather than migrating routers opportunistically.
- Distinctive: line 16
Treat caching, revalidation, redirects, error/loading states, hydration, and route behavior as part of correctness when affected.
- Distinctive: line 17
Avoid assuming a specific hosting provider or deployment architecture.
- Distinctive: line 18
Use semantic, accessible markup and established styling/component conventions.
- Distinctive: line 22
Use repository-declared scripts and its selected package manager.
≈ “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 (optional)
Use this skill only in repositories that already use Next.js.
Inspect package.json, lockfile, Next.js configuration, TypeScript/lint/test configuration, router structure, and applicable AGENTS.md first.
Working rules
- Follow the repository's existing App Router / Pages Router conventions rather than migrating routers opportunistically.
- Preserve server/client component boundaries and keep secrets/server-only data out of client bundles.
- Treat caching, revalidation, redirects, error/loading states, hydration, and route behavior as part of correctness when affected.
- Avoid assuming a specific hosting provider or deployment architecture.
- Use semantic, accessible markup and established styling/component conventions.
Validation
Use repository-declared scripts and its selected package manager. Validate type/static checks, tests, build, and existing browser/E2E coverage as required.
For user-visible changes, run ui-validation against the real application.
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.