What problem does it solve? Writing accurate API reference documentation for a library's public surface is tedious and error-prone, especially when entries are copied from each other or written without reading the source. This Skill generates reference docs entry-by-entry directly from source code, with a manifest to track coverage and staleness. ## Core Features & Use Cases - Manifest-driven tracking: Scans the source tree, builds a manifest.yaml listing every public entry (component, function, endpoint, command) with status (pending/draft/current/outdated/skipped). - Single and batch generation modes: Produce one entry at a time for review, or batch-generate dozens of entries after confirming 2-3 sample docs with the user. - Incremental updates: Detects outdated entries after code changes and refreshes only what changed, keeping docs synchronized with the source. - Use Case: After shipping a Vue component library, run this Skill to scan src/components, generate a manifest of all public components, and produce one accurate reference doc per component with props, defaults, and events extracted from the actual code. ## Quick Start Ask the AI to generate API reference documentation for all public components in the library, starting with a manifest of entries.
