Docgen
SkillDocs & knowledge[UDS] Generate usage documentation (cheatsheets, references, guides) from project sources. Use when: producing a cheatsheet or feature reference from CLI and skill definitions, regenerating docs after commands change, checking generated docs are current. Not for: deciding what documentation a projec
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Docgen skill
What this skill tells your AI
The instructions your AI receives, as published by asiaostrich/universal-dev-standards in skills/docs-generator/SKILL.md and read by ahel’s review.
Generate complete documentation from inspected source with explicit coverage tracking. Use standalone or as the analysis engine for Flow documentation work.
Workflow
- Load the documentation strategy and component template below.
- Execute the manifest-driven coverage workflow against the exact source scope.
- Cross-reference the documented components and synthesize the requested consumer-facing document.
Guardrails
Read every in-scope file. Do not infer behavior from names, skip small files, or claim completeness while manifest entries remain unresolved.
Output
Return the completed/total manifest count, module overview, scaled per-component documentation, verified cross-references, usage examples, and a dependency map when the scope contains multiple components.
Validation
Confirm every manifest item is covered and every documentation claim comes from freshly inspected source.
Example
For a four-file module, report [4/4 files documented], describe each public
interface, and show the verified dependency direction between components.
References
- Docgen strategy — coverage workflow and progress rules.
- Component template — generated document structure.
Signals
- GitHub stars
- 73
- Forks
- 13
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
docgen- Source
- github.com/asiaostrich/universal-dev-standards