Loading...
Loading...
Found 2 Skills
Generate reference documentation entry by entry for the public surface of libraries (components, functions, commands, etc.), with manifest tracking, supporting both single-entry and batch modes. Fundamental differences from guidedoc: guidedoc teaches you how to use things, while libdoc tells you what each part looks like; guidedoc's information sources are solution docs + user knowledge, while libdoc's information source is the source code itself. Trigger scenarios: When users say "write API documentation", "component documentation", "libdoc", "write documentation for each component", or when new public library interfaces are found after feature-acceptance.
Writes one component's documentation entry from its code, stories and real call sites, in a Geist-style page order. Use for "document the button", "write docs for Select", "what states does Toast have", usage rules for a component, or a new or changed component. Skip foundations, overview pages and multi-component patterns. Docs for a whole design system go to design-system-boss.