create-lib-docs
Creating library documentation
Good library docs answer four different questions, and the best projects keep them on separate
pages instead of mixing them: teach me (tutorial), help me do X (how-to guide), explain why
(concepts), tell me exactly (reference). FastAPI, Pydantic, DuckDB and Effect all follow that split,
each with its own strengths. This skill reproduces it for any library, adds what AI agents need
(stable anchors, exact schemas, llms.txt), and refuses to publish anything unverified: a
plausible-looking snippet that doesn't run is worse than no snippet.
references/patterns.md lists what to borrow from each reference project, and references/templates.md
has the page skeletons. Read both before planning the docs.
Options
Read the invocation text for these, in any order: