skills.rest
Astrumon
AstrumonCOMMUNITY
Explore all skills by this author →
đť•Ź@Radix_UAGitHub

architecture-designer

Design system-level architectures and document decisions with ADRs and component diagrams.

Updated Mar 5, 2026
Search Tags:#architecture#scalability#system design#adr#component diagram#trade-offs#operational complexity
One-click install
npx skills add https://github.com/Astrumon/Spovishun --skill architecture-designer-astrumon
Or copy as Structured Prompt for Agentâ–Ľ
Please help me install this Agent Skill.
Skill: architecture-designer
Source: https://github.com/Astrumon/Spovishun/tree/main/.claude/skills/architecture-designer
Command: npx skills add https://github.com/Astrumon/Spovishun --skill architecture-designer-astrumon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams make clear, justified system-level architecture decisions by gathering requirements, evaluating alternatives, and documenting trade-offs so designs are maintainable, scalable, and operable.

Core Features & Use Cases

  • Requirements & Constraints: Elicit functional and non-functional requirements, deployment constraints, and operational expectations.
  • Pattern Matching & Trade-offs: Recommend architectural patterns (e.g., modular monolith, microservices, event-driven) and analyze pros/cons for latency, cost, and operational burden.
  • Design Artifacts & ADRs: Produce component diagrams, Architecture Decision Records (ADR) using the provided template, and explicit failure/degradation plans.
  • Validation & Deliverables: Create a requirements summary, component diagram, ADRs for key choices, technology rationale with alternatives, and risk mitigation strategies for stakeholder review.

Quick Start

Ask the architecture-designer to produce a component diagram, list the top three trade-offs between options, and draft an ADR for the chosen approach.

Frequently Asked Questions about architecture-designer

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

FAQPage Schema
How do I design a scalable system architecture and document the trade-offs?â–Ľ

To design a scalable system architecture, gather functional and non-functional requirements, evaluate patterns like microservices or event-driven systems, and document trade-offs using Architecture Decision Records for stakeholder review.

What is the best way to write an Architecture Decision Record for technology selection?â–Ľ

Writing an Architecture Decision Record involves documenting technology rationale, evaluating explicit alternatives, and validating non-functional constraints like latency and operational complexity to justify system-level architectural choices.

How does component diagram generation work for service decomposition?â–Ľ

Component diagram generation for service decomposition works by mapping cross-cutting multi-layer design tasks into visual design artifacts that illustrate service boundaries and validate system-level operational expectations.

When do I need failure-mode analysis for backend systems?â–Ľ

You need failure-mode analysis for backend systems when validating non-functional constraints and creating explicit failure or degradation plans to ensure your scalable architecture remains operable during disruptions.

Related Skills

Explore More Software Engineering Skills→
Dijjo10Dijjo10

analyst

Elicit and structure project requirements into a Product Definition Record.

Community
Intermediate
franroafranroa

Architecture Designer

Design scalable software architectures and document decisions with ADRs.

Community
Advanced
Elevaria-biaElevaria-bia

aiox-architect

Translate system requirements into secure, scalable multi-layer software architecture.

Community
Advanced
co-cddoco-cddo

System Architect

Design system architectures across monolith, modular monolith, microservices, or serverless patterns with technology selection and NFR mapping.

Official
Basic