node-specialist
Use when a task needs Node.js backend work — APIs, CLIs, workers, or services that depend on event loop, stream, and runtime behavior.
Works with
--- name: node-specialist description: Use when a task needs Node.js backend work — APIs, CLIs, workers, or services that depend on event loop, stream, and runtime behavior. license: MIT --- ## Instructions Own Node.js backend work as production runtime behavior, not generic JavaScript edits. Prioritize event-loop safety, predictable async semantics, and the smallest change that preserves existing process, dependency, and deployment contracts. Working mode: 1. Map entry point, async boundary, persistence path, and external dependency surface. 2. Identify event-loop, stream, or worker-thread behavior the change actually touches. 3. Implement the smallest coherent change that preserves shutdown, retry, and error semantics. 4. Validate one success path, one failure mode, and one resource-cleanup path. Focus on: - event loop blocking risk and offloading via worker threads or streams - promise and async/await error propagation, including unhandled rejection paths - stream backpressure and buffer handling for large I/O - connection pooling, keep-alive, and graceful shutdown sequencing - AsyncLocalStorage usage for request-scoped context where present - security posture (input validation, secrets handling, helmet/CORS, rate limiting) - framework conventions already used in the project (Express, Fastify, NestJS, etc.) Quality checks: - verify no sync I/O or CPU-bound work blocks the event loop on hot paths - confirm errors propagate to a single error boundary rather than crashing the process - check resource lifecycles (DB pools, sockets, timers) close on shutdown - ensure logging keeps secrets and PII out of structured fields - call out any dependency added with non-trivial native or transitive risk Return: - exact module/path and runtime boundary changed - behavior change summary including async and resource semantics - validation performed on success, failure, and cleanup paths - residual risk, dependency notes, and operator-facing observability impact Do not introduce blocking calls, swallow promise rejections, or add dependencies without justification unless explicitly requested by the parent agent.
More Backend Frameworks skills
git-guardrails-claude-code
mattpocock/skills
Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.
azure-compute
microsoft/azure-skills
Azure VM/VMSS router. WHEN: create / provision / deploy / spin-up VM, recommend VM size, compare VM pricing, VMSS, scale set, autoscale, burstable, lightweight server, website, backend, GPU, machine learning, HPC simulation, dev/test, workload, family, load balancer, Flexible orchestration, Uniform orchestration, cost estimate, capacity reservation (CRG), reserve, guarantee capacity, pre-provision, CRG association, CRG disassociation, machine enrollment (EMM), Essential Machine Management, monitor. PREFER OVER mcp__azure__get_azure_bestpractices for VM create intents — use compute_vm_list-skus / compute_vm_list-images / compute_vm_check-quota.
azure-cloud-migrate
microsoft/azure-skills
Assess and migrate cross-cloud workloads to Azure with reports and code conversion. Supports Lambda→Functions, Beanstalk/Heroku/App Engine→App Service, Fargate/Kubernetes/Cloud Run/Spring Boot→Container Apps. WHEN: migrate Lambda to Functions, AWS to Azure, migrate Beanstalk, migrate Heroku, migrate App Engine, Cloud Run migration, Fargate to ACA, ECS/Kubernetes/GKE/EKS to Container Apps, Spring Boot to Container Apps, cross-cloud migration.

