docs-architect

Run this Skill against the repository so it analyzes structure, entry points, dependencies, and data models, then writes a structured manual. The output includes an architecture overview, component deep-dives, and linked code references in Markdown.

This Skill produces an executive summary, architecture overview, design decisions (ADRs), core component deep-dives, data models, integration points, and a security model. Each section follows a progressive disclosure hierarchy from general to specific.

No. The Skill explicitly excludes basic automated API reference generation without design rationale. It focuses on explaining the what and why behind architecture, not endpoint-by-endpoint schema output.

Avoid it for user manuals, marketing content, or copywriting, which are out of scope. Also treat the output as a draft requiring environment-specific validation and expert review rather than a final authoritative document.

Documentation is generated in Markdown with nested headings, syntax-highlighted code blocks, tables for schemas and configurations, and relative links to source files in the format [filename](file:///path/to/file#lines).