skills.rest
wesleyegberto
wesleyegbertoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

architecture-designer

Design system architectures and document ADRs with trade-offs.

3|2|Updated Mar 23, 2026
Search Tags:#architecture#scalability#adr#reliability#design-patterns#system-design
One-click install
npx skills add https://github.com/wesleyegberto/software-engineering-skills --skill architecture-designer-wesleyegberto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-designer
Source: https://github.com/wesleyegberto/software-engineering-skills/tree/main/plugins/architecture/skills/architecture-designer
Command: npx skills add https://github.com/wesleyegberto/software-engineering-skills --skill architecture-designer-wesleyegberto

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Use to design new system architectures, review existing designs, and drive architectural decisions with ADRs, patterns, and scalability planning.

Core Features & Use Cases

  • Guidance on selecting architectural patterns aligned with requirements (monolith, microservices, event-driven, CQRS, etc.)
  • Documentation of Architecture Decisions and ADRs with rationale.
  • Framework for evaluating non-functional requirements and planning for scalability, reliability, and operations.

Quick Start

Provide a system design brief to begin drafting ADRs and a high-level architecture outline.

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 trade-offs for a new system design?▼

You can review existing system designs by evaluating architecture patterns against non-functional requirements, identifying trade-offs in scalability and reliability, and generating ADRs to document necessary architectural changes.

What is the best way to choose architecture patterns for scalability and reliability?▼

To plan system design for scalability and reliability, you evaluate non-functional requirements against architecture patterns like monolith, microservices, or CQRS, and document the resulting trade-offs in ADRs to guide infrastructure decisions.

Can I use this to review an existing system design and make architectural decisions?▼

Yes, you can review existing system designs by evaluating architecture patterns against non-functional requirements, identifying trade-offs in scalability and reliability, and generating ADRs to document necessary architectural changes.

How do I plan system design for scalability and reliability operations?▼

To plan system design for scalability and reliability, you evaluate non-functional requirements against architecture patterns like monolith, microservices, or CQRS, and document the resulting trade-offs in ADRs to guide infrastructure decisions.

Related Skills

Explore More Software Engineering Skills→
proyecto26proyecto26
42

requirements-scoping

Structure ambiguous system design prompts into functional requirements, non-functional constraints, and out-of-scope boundaries.

Official
Intermediate
duynhneduynhne

devops-expert

Optimize and secure CI/CD pipelines, containers, Kubernetes, and infrastructure as code.

Community
Advanced
datamaker-krdatamaker-kr
1

spec-workflow

Orchestrate specification-driven development from feature idea to implemented code.

Official
Advanced
crytligcrytlig

azure-quotas

Analyze Azure resource quotas and usage to validate deployment capacity.

Community
Intermediate