Vtex Io Http Routes

When you're building callback endpoints, partner integrations, or webhook receivers in VTEX IO, this skill keeps your route handlers honest. It pushes you to make HTTP contracts explicit at the handler boundary, validate params and bodies right where the request lands, and pull shared concerns like auth checks into middleware instead of copying them everywhere. The hard constraints are opinionated but practical: no hiding validation deep in service layers, no long-running work that should be async, and middleware for anything repeated. If you're wiring service.json routes to node handlers and want cleaner boundaries between HTTP surface and domain logic, this will keep you from drifting into implicit contracts that break partner integrations.