backend-nodejs

Guides specification, implementation, and review of Node.js backend endpoints and services.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/jcg-admin/IACT-ui --skill backend-nodejs-jcg-admin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: backend-nodejs
Source: https://github.com/jcg-admin/IACT-ui/tree/main/.claude/skills/backend-nodejs
Command: npx skills add https://github.com/jcg-admin/IACT-ui --skill backend-nodejs-jcg-admin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Backend features in Node.js projects often lack consistent structure across diagnosis, API specification, implementation, and quality review, leading to unvalidated inputs, leaked secrets, and untested endpoints. This Skill provides a phase-by-phase checklist so every Node.js feature follows the same disciplined workflow. ## Core Features & Use Cases - Diagnosis Guidance: Maps affected endpoints, layers (controller, service, repository), external dependencies, and error cases before any code is written. - API Contract Specification: Defines input/output contracts, validation rules, and side effects for each endpoint during the design phase. - Implementation Conventions: Enforces a layered order—schema validation first, thin controllers, pure business-logic services, and data-only repositories. - Quality Review Checklist: Verifies input validation, environment-based secrets, bounded queries, safe error logging, and integration test coverage. - Use Case: When adding a new REST endpoint to the thyrox project, invoke this Skill to specify the contract, implement the handler/service/repository layers in order, and audit security before closing the task. ## Quick Start Ask the AI to apply the backend-nodejs skill to design and implement a new validated REST endpoint with layered architecture and integration tests.

Frequently Asked Questions about backend-nodejs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a Node.js REST endpoint with clean architecture?▼

Implement layers in this order: schema validation with zod or joi first, then a controller that only orchestrates, a service holding pure testable business logic, and a repository handling data access. Finish with integration tests for the endpoint.

What should an API specification include for Node.js endpoints?▼

Each endpoint specification should define the HTTP method, route, required headers, JSON body schema, possible status codes, response bodies per case, input validation rules, and side effects such as database writes or emitted events.

How do I validate request input in Node.js APIs?▼

Validate all external inputs with a schema library like zod or joi before any business logic runs. Never trust client-supplied data, and enforce required fields, types, and ranges at the boundary of the handler.

What security checks should a Node.js code review cover?▼

Verify that no secrets are hardcoded and configuration comes from process.env, all queries use LIMIT to bound results, error logs never expose stack traces to clients, and every new endpoint has at least one integration test.

When should I document Node.js endpoints with OpenAPI or Swagger?▼

Document endpoints in OpenAPI or Swagger after implementation and integration testing, but only if the project already uses that tooling. The specification phase should still capture contracts independently in the requirements document.