architecture-designer

Document architecture decisions and generate Mermaid diagrams and ADRs for software systems.

Updated Jan 9, 2026
One-click install
npx skills add https://github.com/dieu-donnee/luxtrax --skill architecture-designer-dieu-donnee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-designer
Source: https://github.com/dieu-donnee/luxtrax/tree/main/.agent/skills/architecture-designer
Command: npx skills add https://github.com/dieu-donnee/luxtrax --skill architecture-designer-dieu-donnee

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams capture and communicate high-level system architectures, preserving decisions and guiding implementation.

Core Features & Use Cases

  • Architecture diagrams: Generate and review architecture diagrams and component interactions.
  • ADR authoring: Create Architecture Decision Records to document trade-offs and rationale.
  • Trade-off evaluation: Assess technology choices, scalability patterns, and operational complexity.
  • Use Case: When planning a new microservices platform, outline services, data flows, and technology decisions.

Quick Start

Design a scalable architecture for a new service with clear components, data flows, and ADRs.

Frequently Asked Questions about architecture-designer

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

FAQPage Schema
How do I document architecture decisions and evaluate trade-offs for a microservices system?

Architecture decision records (ADRs) document trade-offs and rationale for microservices systems. This Skill generates ADRs alongside technology trade-off analyses, capturing decisions to guide implementation and preserve rationale for future reviews.

What is the best way to generate architecture diagrams for scalable infrastructure?

Architecture diagrams for scalable infrastructure are generated using Mermaid syntax. This Skill produces component interaction diagrams and data flow visualizations, outlining services and their relationships for complex software systems.

How do I write an Architecture Decision Record for a system design review?

Writing an Architecture Decision Record involves documenting trade-offs, rationale, and technology choices. This Skill authoring ADRs by analyzing non-functional requirements and assessing risks, producing structured records for architecture reviews.

Can I evaluate technology choices and scalability patterns for a new service architecture?

Evaluating technology choices and scalability patterns is supported for new service architectures. This Skill assesses operational complexity and modular decomposition, producing trade-off analyses that clarify infrastructure decisions.

When do I need to perform modular decomposition and risk assessment for software architecture?

Modular decomposition and risk assessment are needed when planning complex software systems. This Skill supports breaking down architectures into modules and evaluating operational risks, producing structured analyses for scalable infrastructures.

What are the limitations of relying on ADRs for system design documentation?

Relying on ADRs for system design documentation captures decisions but may not reflect real-time operational changes. This Skill produces ADRs and Mermaid diagrams, preserving rationale, though continuous updates require manual architecture reviews.