mockstar-mock

The key words MUST, MUST NOT, SHOULD, SHOULD NOT and MAY in this skill are to be interpreted as described in BCP 14 (RFC 2119, RFC 8174) when, and only when, they appear in all capitals.

Converts any combination of API specs and docs into a runnable mockstar mock project. It accepts OpenAPI 3.x (JSON/YAML), Postman collections, HAR captures, curl command files, GraphQL SDL/introspection, and prose documentation (Markdown, PDF, DOCX, or a URL) — one or several at once — and produces a fully configured mockstar project with realistic scenarios, dynamic handlers, and webhooks, verified by booting the server and smoke-testing every route.

The defining rule: no fabricated endpoints. Every mock traces back to a fetched or provided source. Behavior that is reasoned from context rather than explicitly documented is tagged confidence: "inferred" in the Endpoint Inventory and flagged in the coverage report. Speculation is visible and reviewable; it is never silently promoted to ground truth.

When to use