rc-postman

# Postman Collection Keep a Postman collection synchronized with the API's real routes and request contracts. Build requests from what the code accepts, not from guesses. This skill is standalone and stack-agnostic; it detects how the project defines HTTP endpoints. ## Required Inputs - None. Operates on the current repository. - Optional: the collection output directory (default `.techdocs/docs/postman/`), the collection name (default derived from the project name), and which environments to emit (default `Local`). ## Workflow 1. Locate the collection. Search for an existing `*.postman_collection.json` (`.techdocs/docs/postman/`, `.techdocs/docs/`, `docs/`). If found, read it to preserve its structure and reuse its directory; otherwise default the output to `.techdocs/docs/postman/`, creating the directory if needed. 2. Discover HTTP endpoints from source. Detect the routing mechanism and enumerate every HTTP endpoint with its method, full path, and handler reference. Routing lives in different places per stack: - Framework routers (Express, Fastify, NestJS, Gin, Echo, Spring controllers, FastAPI/Flask, Rails routes, ASP.NET controllers). - Infrastructure manifests (`serverless.yml`, API Gateway / OpenAPI definitions, k8s ingress) — use `http` events; ignore non-HTTP triggers (queue, schedule, stream). - Exclude non-HTTP entry points (queue consumers, cron jobs, background workers). 3. Extract the request contract for each endpoint from its handler/validation...