Node.js Backend Patterns
Production Node.js API patterns: services, middleware, error handling, auth, observability
- What
- Production Node.js API patterns: services, middleware, error handling, auth, observability
- Cost
- Free
- Needs
- a Node.js project
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a Node.js backend patterns skill: production-ready API structure (controllers, services, repositories), middleware composition, centralized error handling, auth patterns, request validation, logging and observability hooks, and testing conventions — the skeleton for standing up a backend that doesn't fall over the first week. By @wshobson, listed here with credit to its creator. Honest caveats: patterns, not a framework — your agent still writes the code and you still review it; Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a Node.js project Install "Node.js Backend Patterns" for me. Give my agent the production Node.js API patterns — services, middleware, error handling, auth, observability Repository: https://github.com/wshobson/agents/blob/main/plugins/javascript-typescript/skills/nodejs-backend-patterns/SKILL.md 1. Fetch the SKILL.md file for the wshobson-nodejs-backend-patterns skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "wshobson-nodejs-backend-patterns". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself. GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.