Habilidades nodejs-best-practices
📦

nodejs-best-practices

Seguro

Apply Node.js Best Practices

Get guidance on Node.js architecture decisions, framework selection, async patterns, and security principles. This skill teaches decision-making frameworks rather than copy-paste code.

Soporta: Claude Codex Code(CC)
🥉 74 Bronce
1

Descargar el ZIP de la skill

2

Subir en Claude

Ve a Configuración → Capacidades → Skills → Subir skill

3

Activa y empieza a usar

Pruébalo

Usando "nodejs-best-practices". I need to build a high-performance API that will handle 10,000 requests per second. What should I use?

Resultado esperado:

For high-performance APIs handling significant load, Fastify is recommended. It offers 2-3x better performance than Express due to its schema-based serialization and lower overhead. Consider: 1) Use Fastify with async/await for routes, 2) Implement rate limiting to protect from abuse, 3) Add validation early using Zod or similar, 4) Consider worker threads for CPU-intensive operations.

Usando "nodejs-best-practices". What anti-patterns should I avoid in Node.js?

Resultado esperado:

Key anti-patterns to avoid: 1) Using Express for edge/serverless projects (use Hono instead), 2) Using synchronous file operations in production, 3) Putting business logic in controllers, 4) Skipping input validation, 5) Hardcoding secrets, 6) Blocking the event loop with CPU-intensive work.

Auditoría de seguridad

Seguro
v1 • 2/24/2026

All 34 static findings are FALSE POSITIVES. This is pure documentation content (SKILL.md) containing educational material about Node.js best practices. The scanner misidentified ASCII tree diagrams (using backticks) as shell commands, security advice as vulnerabilities, and HTTP status code references as system reconnaissance. No executable code, network operations, or file operations are present.

1
Archivos escaneados
340
Líneas analizadas
0
hallazgos
1
Auditorías totales
No se encontraron problemas de seguridad
Auditado por: claude

Puntuación de calidad

38
Arquitectura
100
Mantenibilidad
87
Contenido
50
Comunidad
100
Seguridad
91
Cumplimiento de la especificación

Lo que puedes crear

New Project Architecture

Getting framework and architecture recommendations when starting a new Node.js project based on deployment target and requirements.

Code Review Guidance

Using the decision checklist and anti-patterns section to review existing Node.js code for common issues.

Security Implementation

Applying the security checklist and validation principles when building secure Node.js applications.

Prueba estos prompts

Framework Selection Help 
I am building a [type of application] with these requirements: [list requirements]. What framework should I use and why?
Architecture Review 
Help me structure my Node.js application. It has [describe features]. Should I use a layered architecture?
Async Pattern Selection 
I need to fetch data from [number] external APIs and then process the results. Which async pattern should I use?
Security Checklist 
What security measures should I implement for a Node.js API that handles user authentication and payments?

Mejores prácticas

  • Ask users about their specific context before recommending solutions - do not assume one framework fits all needs
  • Consider the deployment target early in the decision process (Edge, Serverless, Container, VM)
  • Validate all inputs at API boundaries and treat all external data as untrusted
  • Use layered architecture for projects expected to grow beyond simple scripts

Evitar

  • Defaulting to Express for every project without considering alternatives
  • Using synchronous file operations (fs.readFileSync) in production code
  • Skipping input validation and trusting client data
  • Putting business logic directly in route handlers instead of service layer

Preguntas frecuentes

Which Node.js framework should I use in 2025?
It depends on your context. Use Hono for edge/serverless (fastest cold starts), Fastify for high-performance APIs (2-3x faster than Express), NestJS for enterprise teams needing structure, and Express for legacy projects or learning.
Should I use TypeScript with Node.js?
Yes, TypeScript is recommended for Node.js projects. Node.js 22+ supports running .ts files directly with --experimental-strip-types. TypeScript provides better IDE support, catches errors at compile time, and improves maintainability.
How do I handle errors in Node.js?
Use centralized error handling: create custom error classes, throw from any layer, catch at the top level (middleware), and format consistent responses. Clients get user-friendly messages with appropriate HTTP status codes while logs get full details.
When should I use Promise.all vs Promise.allSettled?
Use Promise.all when all promises MUST succeed (fail fast). Use Promise.allSettled when you want all results regardless of individual failures. Use Promise.race for timeouts or first-response-wins scenarios.
How do I secure my Node.js application?
Follow the security checklist: validate all inputs, use parameterized queries, hash passwords with bcrypt/argon2, verify JWTs, implement rate limiting, use security headers (Helmet), enforce HTTPS, and audit dependencies regularly.
Can I use sync file operations in Node.js?
Never use synchronous file operations (fs.readFileSync, etc.) in production code. They block the event loop and degrade performance. Use async alternatives or offload to worker threads for CPU-intensive file processing.

Detalles del desarrollador

Autor

sickn33

Licencia

MIT

Repositorio

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/nodejs-best-practices

Ref.

main

Estructura de archivos

📄 SKILL.md