architecture

Generate structured architecture documentation with SYSTEM_OVERVIEW, API_DESIGN, DATA_MODEL, SECURITY, and ADRs.

1|1|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/orbtyapp/orbty-eazy --skill architecture-orbtyapp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/orbtyapp/orbty-eazy/tree/main/skills/architecture
Command: npx skills add https://github.com/orbtyapp/orbty-eazy --skill architecture-orbtyapp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams produce standardized architecture documentation that defines system structure, APIs, data models, and security decisions upfront, reducing ambiguity and rework.

Core Features & Use Cases

  • SYSTEM_OVERVIEW.md: High-level system overview with diagrams to communicate architecture to stakeholders.
  • API_DESIGN.md: API structure, contracts, and endpoint definitions for developers.
  • DATA_MODEL.md: Data model and entity relationships to guide data storage.
  • SECURITY.md: Security architecture and risk mitigations for compliance.
  • adr/ADR-*.md: Architecture Decision Records capturing decisions and rationale.
  • Use Case: When starting a new product to maintain a living documentation corpus that evolves with the codebase.

Quick Start

Invoke the architecture skill to generate SYSTEM_OVERVIEW.md, API_DESIGN.md, DATA_MODEL.md, SECURITY.md, and ADRs from the current codebase and decisions.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I generate system architecture documentation from an existing codebase?

Architecture documentation standardizes system structure by generating files like SYSTEM_OVERVIEW.md, API_DESIGN.md, DATA_MODEL.md, SECURITY.md, and ADRs. This codifies decisions, defines APIs upfront, and reduces ambiguity and rework for stakeholders.

What is the best way to document architecture decisions and rationale for a new project?

Architecture Decision Records (ADRs) document architecture decisions and rationale. This skill captures them in the adr/ directory using the ADR-NNN_*.md naming convention, maintaining a living documentation corpus that evolves with your codebase.

Can I include mermaid diagrams for context and container views in my system overview?

Yes, mermaid diagrams are included. The skill generates SYSTEM_OVERVIEW.md with mermaid diagrams specifically for context and container views, visually communicating high-level architecture to stakeholders and aligning with TECH_RADAR inputs.

How do I codify API structure and data models upfront for developers?

You codify API structure and data models by generating API_DESIGN.md for endpoint definitions and contracts, alongside DATA_MODEL.md for entity relationships, guiding data storage and development implementation.

Do I need TECH_RADAR and MVP_DEFINITION inputs to draft system design documents?

Yes, TECH_RADAR and MVP_DEFINITION inputs are required. The generated architecture documentation, including system overviews and ADRs, is explicitly aligned to these project inputs to guide implementation and ensure consistent technology choices.