What problem does it solve? Backend developers working in the Self Serve Express BFF need to communicate with other platform services over NATS without bypassing the protected nats.service.ts singleton, inventing unauthorized subjects, or mishandling timeouts and errors. ## Core Features & Use Cases - NATS Request/Reply Guidance: Enforces explicit timeouts, MicroserviceError propagation through next(error), and correct logger usage for subject tracing. - Subject Ownership Rules: Prevents inventing new NATS subjects from Self Serve by routing coordination to the owning service repositories. - Protected File Discipline: Directs all messaging through the existing nats.service.ts helper methods with code-owner review for new methods. - Use Case: When a backend endpoint must resolve a project ID via NATS request/reply, this Skill ensures the call uses the singleton connection, sets an explicit timeout, logs via the logger service, and surfaces failures as structured errors. ## Quick Start Ask the assistant to add a NATS request/reply call in the Express BFF that resolves a project by ID using nats.service.ts with proper timeout and error handling.
