skills.rest
Design-System-ET
Design-System-ETOFFICIAL
Explore all skills by this author →
GitHub

architecture-designer

Design scalable distributed systems and document architecture decisions with ADRs.

Updated Jun 16, 2026
Search Tags:#architecture#scalability#system design#microservices#adr#technical design
One-click install
npx skills add https://github.com/Design-System-ET/genexus-dev-opencode --skill architecture-designer-design-system-et
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-designer
Source: https://github.com/Design-System-ET/genexus-dev-opencode/tree/main/skills/architecture-designer
Command: npx skills add https://github.com/Design-System-ET/genexus-dev-opencode --skill architecture-designer-design-system-et

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the complexity of designing scalable, maintainable software systems by providing a structured framework for decision-making, trade-off analysis, and technical documentation.

Core Features & Use Cases

  • Architecture Decision Records (ADRs): Standardizes the documentation of critical technical choices to ensure long-term project clarity.
  • Pattern Selection: Provides expert guidance on choosing between monoliths, microservices, event-driven architectures, and more based on specific project constraints.
  • System Design: Facilitates the creation of high-level diagrams and non-functional requirement checklists to ensure systems are built for performance and reliability.

Quick Start

Invoke the architecture-designer skill to create an ADR for the proposed migration from a monolithic database to a microservices-based storage strategy.

Frequently Asked Questions about architecture-designer

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

FAQPage Schema
How do I document architectural decisions for a microservices migration?▼

Documenting architectural decisions for microservices requires creating Architecture Decision Records (ADRs) to standardize critical technical choices, ensuring long-term project clarity and structured trade-off analysis. This skill provides the framework to formalize these records.

What is the best way to evaluate technology trade-offs for distributed systems?▼

Evaluating technology trade-offs for distributed systems involves analyzing non-functional requirements and comparing infrastructure patterns like monoliths versus microservices. This skill facilitates rigorous technical design reviews to guide pattern selection based on specific constraints.

How do I design scalable distributed systems for high reliability?▼

Designing scalable distributed systems involves creating high-level diagrams and non-functional requirement checklists to ensure performance and reliability. This skill provides expert-level guidance to structure your system design and infrastructure pattern selection.

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

Architecture Decision Records (ADRs) are needed when you want to standardize the documentation of critical technical choices during system design. They ensure long-term project clarity by providing a structured framework for decision-making and trade-off analysis.

Does this skill support event-driven architecture pattern selection?▼

Yes, pattern selection is supported, providing expert guidance on choosing between monoliths, microservices, event-driven architectures, and other patterns. It evaluates these options based on your specific project constraints and non-functional requirements.

Can I use this for non-functional requirement planning and system architecture reviews?▼

Yes, this skill applies directly to system architecture reviews and non-functional requirement planning. It facilitates the creation of high-level diagrams and checklists to ensure systems are built for performance and reliability.

Related Skills

Explore More Software Engineering Skills→
ldk-hubldk-hub

bmad-agent-architect

Translate product requirements and UX into technical architecture decisions with trade-offs.

Community
Advanced
Blake-JohnBlake-John

architecture-designer

Design and evaluate system architectures while capturing architectural decisions.

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
jungmini0601jungmini0601

planning

Plan technical implementations and design system architectures with roadmaps.

Community
Advanced