husu/loom

Loom lets a developer describe an API in conversational style — vibe coding, in the repo's own framing — and have an agent produce structured interface documentation, complete with a built-in doc viewer and a mock server that mirrors the spec. The mock server is what separates this from a thin wrapper over a docs-generation prompt: frontend teams can hit real mock endpoints while the backend is still in flux, which collapses the usual coordination overhead. The documentation artifact and the runnable mock stay in sync because they come from the same source. Reservation: the repo is in early shape — Chinese-language README, limited test coverage, and no obvious path to importing an existing OpenAPI spec. If the codebase is already documented elsewhere, migration friction is real. But as a greenfield doc-and-mock workflow for a small team starting a new service, the concept is tight. -> Best for: SaaS team of 2-5 building new backend services who want docs and mocks generated together.