Claude Cursor Skill

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 architectu

LLM Mart · 0 points · 14 views 0 listing impressions 0 install-command copies
Download wshobson-agents-plugins_javascript-typescript_skills_nodejs-backend-patterns-46891e7.zip · 8 KB

Install

skills CLI npx skills add https://github.com/wshobson/agents/tree/main/plugins/javascript-typescript/skills/nodejs-backend-patterns
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install wshobson-agents@llmmart
Git git clone https://github.com/wshobson/agents.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole wshobson/agents collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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

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

Testing Patterns

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

Files (agents)
  • references
    • advanced-patterns.md 9.2 KB
      Loading…
    • details.md 14.6 KB
      Loading…
  • SKILL.md 1.9 KB
    ---
    name: nodejs-backend-patterns
    description: 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.
    ---
    
    # 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
    
    1. **Use TypeScript**: Type safety prevents runtime errors
    2. **Implement proper error handling**: Use custom error classes
    3. **Validate input**: Use libraries like Zod or Joi
    4. **Use environment variables**: Never hardcode secrets
    5. **Implement logging**: Use structured logging (Pino, Winston)
    6. **Add rate limiting**: Prevent abuse
    7. **Use HTTPS**: Always in production
    8. **Implement CORS properly**: Don't use `*` in production
    9. **Use dependency injection**: Easier testing and maintenance
    10. **Write tests**: Unit, integration, and E2E tests
    11. **Handle graceful shutdown**: Clean up resources
    12. **Use connection pooling**: For databases
    13. **Implement health checks**: For monitoring
    14. **Use compression**: Reduce response size
    15. **Monitor performance**: Use APM tools
    
    ## Testing Patterns
    
    See `javascript-testing-patterns` skill for comprehensive testing guidance.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.