API Docs Writer

I ship a lot of packages, and every one needs API docs. For a while I did what everyone does: point a tool at the OpenAPI spec, generate a reference, call it done. It isn't. An importer writes the Reference section and stops — no response example bodies, no error resolutions, and none of the tutorial, how-to, or explanation a developer reaches for when they're stuck. That's one of the four Diataxis quadrants, shipped as if it were four. api-docs-writer picks up where the importer quits. It imports the reference, enriches the examples and error tables it dropped, writes the three missing quadrants in calm technical prose, and gates the whole set with five deterministic scripts that return PASS or FAIL, not vibes. On a real client API it caught a missing servers block that would have aimed every code sample at api.example.com. Delivery runs through the SpiderPublish docs theme — a three-column reference with a pinned tabbed code panel, published and deployed. Guidance-only. Composes @spideriq/publish-skills (delivery hands), copy-engine (prose + 7 languages), and voice-builder (the technical voice). Free in beta.