architecture-docs

Generate ADRs, system overviews, and Mermaid diagrams for architecture documentation.

28|3|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/girijashankarj/cursor-handbook --skill architecture-docs-girijashankarj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-docs
Source: https://github.com/girijashankarj/cursor-handbook/tree/main/.cursor/skills/documentation/architecture-docs
Command: npx skills add https://github.com/girijashankarj/cursor-handbook --skill architecture-docs-girijashankarj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematizes the creation and maintenance of architecture records (ADR history, component inventories, and data-flow diagrams) to improve traceability and onboarding.

Core Features & Use Cases

  • ADR creation and tracking: generate, store, and reference Architecture Decision Records.
  • System overview generation: assemble high-level diagrams and component lists from code, designs, or docs.
  • Diagram-driven documentation: produce Mermaid or diagram-assisted documentation to visualize data flows and interactions.
  • Use Case: quickly document a new service by adding ADRs, a system overview, and a Mermaid diagram to docs/architecture.

Quick Start

Create a starter architecture document in docs/architecture with an overview, ADR examples, and a basic Mermaid diagram.

Frequently Asked Questions about architecture-docs

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

FAQPage Schema
How do I create Architecture Decision Records for a new software service?

Create Architecture Decision Records by generating standardized ADR files that capture architectural choices, context, and consequences to ensure consistent engineering standards and traceability across your codebase.

What is the best way to generate system overview diagrams from existing code?

Generate system overview diagrams by assembling high-level component lists and data-flow visualizations from existing code or design documents to improve onboarding and architectural traceability.

How does diagram-driven documentation work for visualizing data flows?

Diagram-driven documentation works by producing Mermaid diagrams that map component interactions and data flows, allowing teams to maintain visual architecture references directly within their documentation.

Can I use Mermaid diagrams for system design documentation across multiple teams?

Yes, you can use Mermaid diagrams for system design documentation to establish consistent visual conventions, enabling multiple teams and lifecycles to reference the same architectural standards.

When do I need ADRs and component inventories for my engineering project?

You need ADRs and component inventories when your codebase or design requires systematized architecture records, high-level overviews, and traceability to improve team onboarding and maintain engineering standards.

How do I start documenting architecture with ADRs and Mermaid diagrams?

Start documenting architecture by creating a starter document in your docs/architecture directory containing a system overview, ADR examples, and a basic Mermaid diagram to establish baseline conventions.