skills.rest
preedep
preedepCOMMUNITY
Explore all skills by this author →
GitHub

architecture-designer

Design scalable system architectures and document decisions with ADRs.

Updated Apr 15, 2026
Search Tags:#architecture#scalability#microservices#adr#trade-offs#diagrams#system-design
One-click install
npx skills add https://github.com/preedep/kham --skill architecture-designer-preedep
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-designer
Source: https://github.com/preedep/kham/tree/main/.claude/skills/architecture-designer
Command: npx skills add https://github.com/preedep/kham --skill architecture-designer-preedep

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Architects and teams face the challenge of designing scalable system architectures and documenting key decisions. This skill provides a structured approach to create architecture diagrams, write Architecture Decision Records (ADRs), evaluate technology trade-offs, and plan for scalable infrastructure.

Core Features & Use Cases

  • Create architecture diagrams (Mermaid) and visualize component interactions.
  • Author Architecture Decision Records (ADRs) to capture rationale and trade-offs.
  • Evaluate technology options and patterns for scalability, reliability, and maintainability.
  • Review architecture with stakeholders and plan for microservices boundaries and infrastructure patterns.

Quick Start

Generate a high-level architecture diagram and an ADR outline for a scalable system design, including candidate components and technology 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 design scalable system architectures and document the decisions?▼

Author Architecture Decision Records (ADRs) to document trade-offs and rationale, and generate Mermaid architecture diagrams to visualize scalable system designs and component interactions for stakeholder reviews.

How do I write an Architecture Decision Record for microservices planning?▼

Use ADR templates to capture rationale and technology trade-offs during microservices planning, ensuring your architecture decisions for scalability and maintainability are properly documented.

What is the best way to visualize system design and component interactions?▼

Generate Mermaid architecture diagrams to visualize component interactions and candidate components, providing a clear system design overview for stakeholder reviews and microservices boundary planning.

Can I evaluate technology trade-offs for scalability and maintainability during an architecture review?▼

Evaluate technology options and patterns to analyze trade-offs affecting scalability, reliability, and maintainability, directly guiding your design decisions during stakeholder architecture reviews.

When do I need Architecture Decision Records for system design?▼

You need Architecture Decision Records when designing scalable systems to document technology trade-offs and rationale, providing a structured approach for architecture reviews and infrastructure planning.

Related Skills

Explore More Software Engineering Skills→
nahisahonahisaho
69

system-architect

Generate Mermaid C4 diagrams and ADRs for system architecture design.

Community
Advanced
Vivekmano27Vivekmano27

system-architect

Design system architectures with Mermaid diagrams and ADR documentation.

Community
Advanced
dieu-donneedieu-donnee

architecture-designer

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

Community
Advanced
softsparksoftspark
161

architecture-decision

Document architecture decisions with structured templates for context, consequences, and trade-offs.

Community
Advanced