Nodejs backend patterns

Skill FridrichMethod/awesome-skills/skills/nodejs-backend-patterns

Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices. Use when creating Node.js servers, REST APIs, GraphQL backends, or microservices architectures.From its SKILL.md

Install

npx -y skills add FridrichMethod/awesome-skills --skill nodejs-backend-patterns

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
11 stars11 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.9 KB, 339 tokens by cl100k_base, as published. Nobody here has run it

Node.js Backend Patterns

Comprehensive guidance for building scalable, maintainable, and production-ready Node.js backend applications with modern frameworks, architectural patterns, and best practices.

When to Use This Skill

Building REST APIs or GraphQL servers
Creating microservices with Node.js
Implementing authentication and authorization
Designing scalable backend architectures
Setting up middleware and error handling
Integrating databases (SQL and NoSQL)
Building real-time applications with WebSockets
Implementing background job processing

Detailed patterns and worked examples

Detailed pattern documentation lives in references/details.md. Read that file when the navigation tier above is insufficient.

Best Practices

Use TypeScript: Type safety prevents runtime errors
Implement proper error handling: Use custom error classes
Validate input: Use libraries like Zod or Joi
Use environment variables: Never hardcode secrets
Implement logging: Use structured logging (Pino, Winston)
Add rate limiting: Prevent abuse
Use HTTPS: Always in production
Implement CORS properly: Don't use * in production
Use dependency injection: Easier testing and maintenance
Write tests: Unit, integration, and E2E tests
Handle graceful shutdown: Clean up resources
Use connection pooling: For databases
Implement health checks: For monitoring
Use compression: Reduce response size
Monitor performance: Use APM tools

Testing Patterns

See javascript-testing-patterns skill for comprehensive testing guidance.

What ships with it: 2 files

23.9 KB alongside SKILL.md

references/

advanced-patterns.md9.2 KB
details.md14.7 KB

Gives 2 of the 12 instructions most data backend skills give in 339 tokens

Counted across 229 of the 229 authors here whose files we hold, read 2026-08-07

Separate business logic into service layersin 22 of 229, across 15 files
Retry failures with exponential backoffin 21 of 229, across 14 files
Select only needed database columnsin 20 of 229, across 13 files
Abstract data access into repository classesin 19 of 229, across 12 files
Use centralized error handlersin 17 of 229, across 10 files
Use AsNoTracking for read-only queriesin 16 of 229, across 4 files
Use async/await for all I/O operationsin 16 of 229, across 5 files
Implement structured logginghere, and in 15 of 229, across 4 files
Use dependency injection for all servicesin 14 of 229, across 2 files
Use resource-based URLs for REST APIsin 13 of 229, across 7 files
Invalidate cache after data changesin 13 of 229, across 9 files
Use a dependency injection containerhere, and in 12 of 229, across 4 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.