architecture-designer

Design high-level system architectures and ADRs with Mermaid diagrams.

1|Updated Aug 12, 2023
One-click install
npx skills add https://github.com/nktfh100/nixos-config --skill architecture-designer-nktfh100
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-designer
Source: https://github.com/nktfh100/nixos-config/tree/main/claude/skills/architecture-designer
Command: npx skills add https://github.com/nktfh100/nixos-config --skill architecture-designer-nktfh100

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Architects and engineers often struggle to align on high-level architectural decisions and ensure scalable designs across complex systems. This skill provides a framework to create architecture diagrams, capture rationale with ADRs, and evaluate technology trade-offs before implementation.

Core Features & Use Cases

  • Architecture Design & ADRs: Create architecture diagrams, capture decisions with ADRs, and compare trade-offs across candidate patterns.
  • Pattern & Infrastructure Planning: Evaluate monolith vs microservices, data strategies, and deployment architectures for scalability.
  • Collaboration & Documentation: Produce concise design docs that stakeholders can review and sign off on.

Quick Start

Draft a high-level architecture design for a new microservice platform and generate an ADR outlining the main trade-offs.

Frequently Asked Questions about architecture-designer

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

FAQPage Schema
How do I document system design trade-offs for a microservices architecture?▼

Architecture diagrams visualize system design components and data flows using Mermaid syntax, enabling engineers to map out microservices, infrastructure planning, and scalability analysis before implementation begins.

When do I need to write an ADR for infrastructure planning?▼

You need to write an ADR for infrastructure planning when evaluating technology trade-offs across deployment architectures, ensuring that architectural decisions regarding scalability and data strategies are documented for stakeholder review and sign-off.

What's the best way to compare monolith vs microservices for a new platform?▼

The best way to compare monolith vs microservices is to perform a trade-off analysis that evaluates deployment architectures, data strategies, and scalability requirements, producing a concise design doc with ADRs to guide the final architectural decision.

Can I generate architecture diagrams automatically from my system design decisions?▼

Yes, you can generate architecture diagrams using Mermaid syntax directly from your system design decisions, producing visual representations of microservices and infrastructure patterns alongside the corresponding ADRs and trade-off analyses.

Does this approach support pattern selection for scalability analysis?▼

Yes, this approach supports pattern selection for scalability analysis by evaluating candidate patterns and deployment architectures, producing trade-off analyses that determine which infrastructure planning choices best meet your scalability requirements.