api-simulation
Use when you add or change code that calls other services and need to run it, test it, prove a fix or reproduce an upstream failure (timeouts, 5xx, 409, 429) end to end, locally or in CI, without the real services because they're unreachable, need credentials, cost money, have side effects or don't exist yet. Also use it to answer what happens to a request, or to the data it writes, when a service it calls goes down, is slow or returns errors ("what happens to a booking if the email service is down?"). Runs services, frontends, tests or demos against stand-ins for their HTTP dependencies, served as one environment locally or at a deployed URL. Applies even when nobody says mock or simulation; a postman/simulations/ directory is itself a reason to load it. To give a frontend or another team a stand-in for an API, use api-mocking. Covers postman simulation.
Pinned to revision 6936c4e3b882, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/api-simulation/SKILL.md
- skills/api-simulation/reference/context_file.md
- skills/api-simulation/reference/sim_yaml_schema.md
Every link opens the file at its source, pinned to the revision this page describes.