express-domain-delivery

What problem does it solve?

Express route pipelines often become inconsistent and fragile, causing middleware order mistakes, unclear error handling, unsafe validation/auth placement, and blurry transaction ownership that leads to hard-to-debug production failures.

Core Features & Use Cases

• Deliberate middleware pipeline ordering: Ensures security, parsing, context/logging, auth/rate limiting, routers, not-found, and one canonical error handler run in the correct sequence.
• Clear Express boundaries: Keeps controllers thin (HTTP mapping only) while services own business logic and transaction boundaries.
• Production-ready delivery with evidence: Forces source-of-truth reading, scoped verification, confidence gating, and explicit rollback planning before claiming completion.
• Use case: Add or modify an Express endpoint that mixes validation, authorization, async work, persistence, and response mapping without breaking existing middleware behavior.

Quick Start

Ask the AI to deliver a safe Express middleware and routing change by running the skill in implementation phase: /supervibe express-domain-delivery for your specific route family.