About nodejs-backend-patterns
A pattern guide for Node.js backend developers building APIs, microservices, and scalable applications. It combines architecture guidance with practices for validation, error handling, databases, and testing.
Key features
- 01REST API and GraphQL patterns
- 02Microservices and architecture design
- 03Authentication, authorization, and middleware
- 04Database integration and background jobs
- 05Logging, monitoring, and health checks
Use cases
- 01Designing a Node.js microservice architecture
- 02Adding authentication and error handling to an API
- 03Integrating SQL or NoSQL databases
- 04Planning background jobs or real-time applications
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ wshobson/ agents --skill nodejs-backend-patternsAfter installing, type/nodejs-backend-patternsin Claude Code to confirm it loaded.
Bundled filesreferences/advanced-patterns.mdreferences/details.md
Details
From the project READMENode.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.