architecture-doc-writer

To generate architecture documentation from a codebase, you need a tool that analyzes source files and outputs structured markdown. This Skill produces a complete architecture document with an ASCII diagram, module tree, and tech stack table to support onboarding.

Creating an ASCII architecture diagram for onboarding involves mapping software components into 3-6 layered boxes. This Skill enforces ASCII-only diagrams around 120 columns, ensuring they render correctly in markdown and terminal environments.

Building a tech stack table for documentation involves categorizing the technologies used in your project. This Skill generates a two-column tech stack table listing categories and technologies, alongside the architecture diagram and module tree.

Yes, you can generate a module tree view for software projects of various sizes. The Skill produces a tree-style file organization view that helps stakeholders and new team members understand the repository structure.

Yes, the generated architecture document outputs directly to docs/ARCHITECTURE.md in your repository. This standard placement ensures the documentation is easily accessible for reviews and onboarding.

The limitation of ASCII diagrams for architecture documentation is the 120-column width constraint and 3-6 layer limit. This ensures terminal compatibility but may require structural simplification for highly complex, deeply nested project architectures.