Skipper: generate a backend (and optionally its UI + e2e tests)

Skipper turns a plain-English description into a running reactive backend service (REST API + OpenAPI spec). You drive the Skipper CLI to produce the service, then — for a website/app — you build the frontend against the service's generated openapi.json. That seam is the whole point of this skill: let Skipper own the backend, you own the UI.

Two job shapes

• "Build me a website / app" → generate the service with Skipper, run it locally, scaffold a frontend that calls it, then cover the flows with Playwright end-to-end tests.
• "Build me an API / backend / service" → generate the service with Skipper, smoke-test it, report the endpoints. Stop there.

Pick the shape from the user's request. When unsure, ask.

Hard rules (read before doing anything)