saranskumar Goal
Design Node.js services that separate runtime concerns from business logic and integration code.
When to Use
- A Node.js backend process needs design.
- The system is service-oriented or integration-heavy.
- The project is not purely frontend despite sharing a JS/TS stack.
Instructions
- Define service purpose, consumers, and runtime behavior.
- Separate startup code, handlers, domain logic, adapters, and config.
- Plan errors, retries, shutdown, and operational visibility.
- Note environment and dependency assumptions.
Constraints
- Do not equate Node.js with Express only.
- Avoid hiding system behavior inside framework middleware chains.
- Keep runtime lifecycle explicit.
Output Format
- service overview
- module and runtime structure
- operational notes
- risks
Examples
- "Design a Node service for provider sync."
- "How should this Node daemon be structured?"