skills.rest
vasilyu1983
vasilyu1983COMMUNITY
Explore all skills by this author →
Website𝕏@vasilyuGitHub

software-architecture-design

Design system-level software architectures including patterns, scalability, resilience, and ADR-driven decisions.

73|16|Updated Nov 14, 2025
Search Tags:#scalability#system design#microservices#resilience#ADR#event-driven#architecture patterns
One-click install
npx skills add https://github.com/vasilyu1983/AI-Agents-public --skill software-architecture-design
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: software-architecture-design
Source: https://github.com/vasilyu1983/AI-Agents-public/tree/main/frameworks/claude-code-kit/initial-setup/skills/software-architecture-design
Command: npx skills add https://github.com/vasilyu1983/AI-Agents-public --skill software-architecture-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Designing robust, scalable, and maintainable software systems is complex, requiring careful consideration of architecture patterns, data consistency, and reliability. This Skill provides execution-ready patterns for system-level design decisions.

Core Features & Use Cases

  • Architecture Pattern Selection: Choose between monolith, modular monolith, microservices, event-driven, and serverless architectures based on project needs.
  • Scalability & Resilience: Design for high traffic with load balancing, caching, sharding, and implement resilience patterns like circuit breakers and retries.
  • Decision Documentation: Use Architecture Decision Records (ADRs) to document key design choices, tradeoff analysis, and technology selection for clarity and future reference.

Quick Start

Use the software-architecture-design skill to design a microservices architecture for an e-commerce platform, focusing on service boundaries and data consistency.

Frequently Asked Questions about software-architecture-design

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

FAQPage Schema
How do I choose between microservices, monolith, and event-driven architectures?▼

Architecture pattern selection depends on team size, scalability needs, and operational complexity. Monoliths suit smaller teams; microservices enable independent scaling; event-driven architectures decouple services for resilience. This Skill covers tradeoffs for each pattern so you can match your project constraints.

What's the best way to document architecture decisions for a production system?▼

Architecture Decision Records (ADRs) document design choices, tradeoffs, and technology rationale in a structured format. ADRs create a clear audit trail for future maintainers and help teams avoid repeating solved problems. This Skill provides ADR templates and decision-making frameworks.

How do I design for scalability and resilience in distributed systems?▼

Scalability patterns include load balancing, caching, and data sharding; resilience patterns include circuit breakers, retries, and graceful degradation. This Skill covers service boundary design, data consistency models, and how to combine these patterns for production-grade systems.

Can I apply microservices architecture to an existing monolith?▼

Yes. Microservices work for greenfield projects and major refactors of existing systems. This Skill guides service boundary definition, data consistency strategies, and observability modeling to execute refactors safely while maintaining system stability.

What should I consider when designing API contracts between services?▼

API contracts define interfaces between services and prevent breaking changes. This Skill covers service boundary modeling, API contract definition, and observability patterns so teams can evolve services independently without cascading failures.

Do I need to handle data consistency differently in microservices versus monoliths?▼

Yes. Monoliths use transactions; microservices require eventual consistency, sagas, or event-driven patterns. This Skill examines data consistency models for each architecture style so you can choose the right approach for your reliability and latency requirements.

Related Skills

Explore More Software Engineering Skills→
nguyenphpnguyenphp
41

architecture

Facilitate architectural decision-making with requirements analysis, trade-off evaluation, and ADR documentation.

Community
Advanced
mislam-devmislam-dev
1

microservices-architecture

Design microservices architectures with service boundaries and communication patterns.

Community
Advanced
theandyalvarez7-rubytheandyalvarez7-ruby

senior-backend

Design scalable Node.js/Express/Fastify backend architectures and API designs.

Community
Advanced
thapaliyabikendrathapaliyabikendra
24

system-design-patterns

Provide system design patterns for scalable distributed systems.

Community
Intermediate