super-nodejs
Skill0 starsChanged 18 days agoMITView on GitHub
Use for any Node.js backend work: package.json, Express, Fastify, middleware, REST or GraphQL APIs, authentication, database integration, error handling, async patterns, Node security and testing. One skill with two specialities: decide (framework, runtime, architecture, anti-patterns) and build (production-ready service patterns with worked examples). It detects the job and loads only the guide it needs.
In this repository57 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/comments.mdcCursor rule
- .cursor/rules/commit-messages.mdcCursor rule
- .cursor/rules/git-workflow.mdcCursor rule
- .cursor/rules/manage-stack.mdcCursor rule
- .cursor/rules/no-worktrees.mdcCursor rule
- manage-stackSkill
- convert-as-skillSkill
- create-agentSkill
- create-agents-mdSkill
- create-commandSkill
- create-hookSkill
- create-ruleSkill
- create-skillSkill
- retrospectiveSkill
- super-architectureSkill
- super-cachingSkill
- super-elixirSkill
- super-protobufSkill
- super-tech-blueprintSkill
- atomic-semantic-commitSkill
- code-reviewSkill
- create-bruno-collectionSkill
- create-documentationSkill
- create-ticketsSkill
- ready-specSkill
- write-adrSkill
- write-changelogSkill
- write-mr-descriptionSkill
- write-planSkill
- write-postmortemSkill
- write-runbookSkill
- noslopSkill
- output-saversSkill
- safe-refactorSkill
- tddSkill
- verifySkill
- get-movingSkill
- later-listSkill
- standupSkill
- challenge-meSkill
- codebase-learnerSkill
- researchSkill
- second-opinionSkill
- traceSkill
- color-kitSkill
- design-system-kitSkill
- diagramSkill
- infographicSkill
- product-polish-workflowSkill
- prototype-wireframeSkill
- ui-ux-kitSkill
- evidenceSkill
- find-skillsSkill
- handoffSkill
- rumblingSkill
- use-levistackSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 38
Do this first and do not announce it.
- Very specific: line 54
Gate: Run what package.json defines (lint, type check, test).
≈ “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
Super Node.js
One skill, two specialities. Call it once. It picks the speciality from the job and loads only that guide.
The guides are kept whole. Each is a full, separate skill that was merged in.
Step 0: detect the job
Do this first and do not announce it. Read package.json (dependencies, type, scripts) and the server entry point if the project exists; the facts decide framework-specific advice.
| If the user is doing this | Speciality | Load |
| Choosing a framework or runtime, "how should I structure this", reviewing a design, naming an anti-pattern, a decision checklist | best-practices | best-practices |
| Writing the service: Express or Fastify setup, middleware, auth, database integration, validation, error handling, API design, tests | backend-patterns | backend-patterns |
| A new service from scratch | both, in order | best-practices, then backend-patterns |
| Reviewing existing Node code | best-practices for the principles, backend-patterns for the target shape | both, as needed |
Order of precedence: a security finding, then the user's explicit words, then the detected job. A security issue or data-loss risk is always stated in full sentences.
Build pipeline: one service, in order
- Decide. best-practices: framework, runtime, layering, what to avoid. Write the decisions down in two or three lines before coding.
- Build. backend-patterns: the structure, middleware, auth, data access and error handling that the decisions call for. Open its
references/only for the topic at hand. - Test. The testing section of each guide. Run the project's own test command, not a guessed one.
- Gate. Run what
package.jsondefines (lint, type check, test). Report any gate you could not run.
Rules that hold across both guides
- Follow the project first. Match the framework, module system and conventions already in
package.jsonand the code; the guides are defaults, not a rewrite order. - One place for each concern. Validation, authentication and error mapping each live in one layer, not scattered through handlers.
- Fail loudly at startup, safely at runtime. Missing config stops boot; request errors return a controlled response and are logged once.
- Never block the event loop. Anything CPU-heavy or synchronous on a request path is moved off it.
Related skills
super-architecture: pick or review the service structure.super-caching: add or tune a cache layer.super-protobuf: the service exposes gRPC or Connect.tdd: build or fix a handler test-first.noslop: filter generated handlers and errors for slop.create-bruno-collection: document and run the API as a Bruno collection.
Done when
- The guide that matches the job was opened, and only that one (plus the second when the job needs it).
- Advice matches the project's actual framework and module system.
- The project's own gates ran, or the ones that did not are named.
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.