docs-architect

Generates comprehensive technical documentation and architecture guides from existing codebases.

2|Updated Jun 16, 2026
One-click install
npx skills add https://github.com/monang404/lunawave --skill docs-architect-monang404
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: docs-architect
Source: https://github.com/monang404/lunawave/tree/main/.agent/skills/docs-architect
Command: npx skills add https://github.com/monang404/lunawave --skill docs-architect-monang404

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing long-form technical documentation for a complex codebase is time-consuming and often skipped, leaving teams without architecture references, onboarding material, or design rationale. This Skill analyzes an existing codebase and produces structured, in-depth technical manuals that capture both the what and the why of the system. ## Core Features & Use Cases - Codebase Analysis: Examines code structure, dependencies, design patterns, data flows, and integration points to ground documentation in the actual implementation. - Structured Long-Form Output: Produces multi-chapter documents covering executive summaries, architecture overviews, design decisions, core components, data models, security, and deployment. - Diagram and Visual Planning: Describes architectural diagrams, sequence diagrams, and flowcharts to communicate system behavior. - Use Case: Point the Skill at a backend service repository and receive a complete architecture guide with component deep-dives, API documentation, and onboarding reading paths for new engineers. ## Quick Start Analyze this repository and generate a comprehensive technical architecture document covering its components, data flow, and design decisions.

Frequently Asked Questions about docs-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate technical documentation from an existing codebase?▼

Provide the codebase and ask for an architecture document. The Skill analyzes code structure, dependencies, and design patterns, then produces a structured manual covering components, data models, integration points, and design rationale.

What sections should a software architecture document include?▼

A complete architecture document includes an executive summary, architecture overview, design decisions, core component deep-dives, data models, integration points, deployment architecture, performance characteristics, security model, and appendices with glossary and references.

Can this Skill document design decisions and rationale?▼

Yes, documenting the why behind design decisions is a core practice. The Skill extracts architectural choices from the codebase and explains their rationale, including evolutionary history and common pitfalls.

What output format does the documentation use?▼

Documentation is generated in Markdown with clear heading hierarchy, syntax-highlighted code blocks, tables, and file references in file_path:line_number format. Diagrams and flowcharts are described in detail within the text.

When should I not use automated codebase documentation?▼

Avoid it when the codebase is too small to warrant long-form documentation, or when you need API reference docs generated from type signatures, which dedicated tools like Javadoc or Sphinx handle more precisely.