skills.rest
Ethansuttor
EthansuttorCOMMUNITY
Explore all skills by this author →
GitHub

agent-arch-system-design

Design scalable system architectures and document ADRs with C4/UML diagrams.

Updated Apr 1, 2026
Search Tags:#architecture#scalability#adr#patterns#diagrams#system-design
One-click install
npx skills add https://github.com/Ethansuttor/QUANTIFIED --skill agent-arch-system-design
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-arch-system-design
Source: https://github.com/Ethansuttor/QUANTIFIED/tree/main/.gemini/skills/ruflo/.agents/skills/agent-arch-system-design
Command: npx skills add https://github.com/Ethansuttor/QUANTIFIED --skill agent-arch-system-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams design scalable, well-documented system architectures and capture architectural decisions to guide implementation and collaboration.

Core Features & Use Cases

  • High-level system design: Create architecture overviews (C4/UML), define components, interfaces, and data flows.
  • ADR documentation: Produce Architecture Decision Records to justify patterns and trade-offs.
  • Guided decision support: Evaluate technology choices, identify risks, and propose mitigations for major decisions.
  • Use Case: Audit a monolithic application and draft a microservices-oriented architecture with clear boundaries and non-functional requirements.

Quick Start

Provide a high-level system architecture for a given project, including major components, interactions, and trade-offs.

Frequently Asked Questions about agent-arch-system-design

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

FAQPage Schema
How do I design scalable system architectures for complex enterprise projects?▼

Architecture Decision Records (ADRs) document architectural decisions to justify patterns and trade-offs. They capture the rationale behind technology choices, evaluate risks, and propose mitigations to guide implementation and team collaboration.

What is the best way to document architectural decisions and trade-offs?▼

Architecture Decision Records (ADRs) document architectural decisions to justify patterns and trade-offs. They capture the rationale behind technology choices, evaluate risks, and propose mitigations to guide implementation and team collaboration.

Can I use C4 and UML diagrams to define components and data flows?▼

Yes, you can create architecture overviews using C4 and UML diagrams to define components, interfaces, and data flows. This visual modeling helps establish clear boundaries and non-functional requirements for your system.

How do I audit a monolithic application and draft a microservices architecture?▼

Audit a monolithic application to draft a microservices-oriented architecture by evaluating trade-offs and identifying risks. The skill proposes mitigations and establishes clear boundaries with non-functional requirements for major decisions.

Does this system design process require human approval for major technical decisions?▼

Yes, the system design process requires human approval for major technical decisions. It provides guided decision support by evaluating technology choices and identifying risks, ensuring teams validate architecture patterns before implementation.

Related Skills

Explore More Software Engineering Skills→
pingmepipingmepi

pm-stage-01-brief

Generate a structured 7-section product brief from a business statement.

Community
Advanced
VSF-QC-TTSVSF-QC-TTS

common-architecture-diagramming

Standardize architecture diagrams using C4 and UML models with Mermaid syntax.

Official
Intermediate
andisabandisab

gitlab-ci

Generate secure GitLab CI/CD pipelines for Terraform and Kubernetes deployments.

Community
Advanced
TwuanMinnTwuanMinn

architecture

Document architecture decisions using ADRs and structured trade-off analyses.

Community
Advanced