/architecture

Generate structured architecture documentation with HLD, LLD, C4 diagrams, and cloud blueprints.

49|12|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/DavidROliverBA/ArchitectKB --skill architecture-davidroliverba
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: /architecture
Source: https://github.com/DavidROliverBA/ArchitectKB/tree/main/.claude/skills/architecture
Command: npx skills add https://github.com/DavidROliverBA/ArchitectKB --skill architecture-davidroliverba

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps Solutions Architects and Technical Architects create structured documentation for various architecture designs, ensuring consistency and completeness.

Core Features & Use Cases

  • Architecture Documentation: Generates notes for High-Level Designs (HLD), Low-Level Designs (LLD), C4 diagrams, and cloud architectures.
  • Scope Definition: Clearly defines the project or enterprise-wide scope of the architecture.
  • System and Component Mapping: Identifies and links involved systems and design patterns.
  • Non-Functional Requirements: Captures critical NFRs like availability, latency, and security.
  • Decision Rationale: Documents key design decisions and considered alternatives.
  • Use Case: When designing a new data integration pipeline, use this Skill to create a comprehensive HLD, including involved systems like SAP and DataPlatform, design patterns like event-driven, and NFRs for latency and throughput.

Quick Start

Use the /architecture skill to create a new High-Level Design note for the 'Customer Data Platform' project.

Frequently Asked Questions about /architecture

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

FAQPage Schema
How do I generate structured high-level and low-level design documentation for a new software architecture?

Generate structured high-level and low-level design documentation by defining the project scope, mapping involved systems, applying design patterns, and capturing non-functional requirements like latency and security. This ensures comprehensive architecture blueprints for enterprise solutions.

What is the best way to document C4 diagrams and cloud infrastructure blueprints for a data integration pipeline?

Document C4 diagrams and cloud infrastructure blueprints by capturing the architecture scope, linking involved systems like SAP and DataPlatform, and detailing event-driven design patterns alongside throughput non-functional requirements for comprehensive knowledge management.

How do I capture non-functional requirements and key design decisions when creating architecture documentation?

Capture non-functional requirements and design decisions by documenting critical constraints such as availability and latency, recording the design rationale, and linking to related ADRs to maintain comprehensive architectural knowledge.

Does this architecture documentation approach work for both project-specific solutions and enterprise-wide scope?

Yes, the architecture documentation approach supports both enterprise-wide and project-specific scopes, allowing you to map involved systems, apply design patterns, and capture non-functional requirements for diverse architectural solutions.

Can I link ADRs to my high-level design notes for better architecture knowledge management?

Yes, you can link related ADRs and projects directly to your high-level design notes to ensure comprehensive knowledge management and traceability of key architectural decisions and considered alternatives.