What problem does it solve? Manually writing REST Client .http files for every API controller is repetitive and error-prone; this Skill scaffolds a complete, convention-compliant .http test file for any endpoint in the ECommerceApp API. ## Core Features & Use Cases - Two ready templates: Template A for standard resource CRUD endpoints and Template B for custom-route endpoint groups, both in VS/VS Code REST Client format. - Built-in auth flow: Every generated file starts with a Login request against /api/Login so you can copy the JWT into the @token variable. - Convention enforcement: Variables (@baseUrl, @token, @contentType, @routePrefix), ### separators, Bearer headers on protected endpoints, and commented-out sub-resource routes. - Use Case: After adding a new Orders controller, ask for an HTTP scenario and receive an orders.http file with login, paginated GET, GET by ID, POST, PUT, and DELETE requests matching the controller's DTOs. ## Quick Start Ask the assistant to create an HTTP scenario for a given controller or bounded context name, and it will read the controller and generate the .http file under ECommerceApp.API/HttpScenarios.