skills.rest
Danhvb
DanhvbCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

System Design

Design scalable software architectures with pattern selection and design artifacts.

Updated Feb 9, 2026
Search Tags:#design#architecture#security#scalability#microservices#event-driven#system-design
One-click install
npx skills add https://github.com/Danhvb/my-ba-skills --skill system-design-danhvb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: System Design
Source: https://github.com/Danhvb/my-ba-skills/tree/main/multi-agent-ba/.agent/skills/solution-architect/system-design
Command: npx skills add https://github.com/Danhvb/my-ba-skills --skill system-design-danhvb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design and document scalable, reliable software architectures to align technical decisions with business goals, reducing drift and rework.

Core Features & Use Cases

  • Pattern selection: Choose between Monolithic, Microservices, Event-Driven, and Serverless architectures based on needs.
  • Quality attributes: Address scalability, availability, reliability, maintainability, and security.
  • Deliverables: Produce High-Level Design (HLD), Low-Level Design (LLD), Architectural Decisions Records (ADRs), API strategy, and data model considerations.
  • Use Case: A growing platform transitions from a monolith to microservices while preserving data consistency and observability.

Quick Start

Refine a system design by selecting a pattern (e.g., Microservices or Event-Driven) and outlining core components and interfaces for the next milestone.

Frequently Asked Questions about System Design

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

FAQPage Schema
How do I design scalable software architectures for business requirements?▼

Design scalable software architectures by selecting patterns like Microservices or Event-Driven, addressing cross-cutting concerns like security, and producing HLD, LLD, and ADR artifacts to align technical decisions with business goals.

When should I transition from a monolithic to a microservices architecture?▼

Transition from a monolithic to a microservices architecture when a growing platform requires improved scalability and maintainability, using high-level and low-level designs to preserve data consistency and observability.

How do I choose between Monolithic, Microservices, Event-Driven, and Serverless patterns?▼

Choose between Monolithic, Microservices, Event-Driven, and Serverless patterns by evaluating business requirements against quality attributes like scalability, availability, reliability, and security to guide architectural decisions.

What deliverables are needed for high-level and low-level system design?▼

High-level and low-level system design deliverables include Architectural Decision Records, API strategy, data model considerations, and core component interfaces outlined for the next project milestone.

Does system design address security and maintainability for event-driven architectures?▼

System design addresses security and maintainability for event-driven architectures by applying cross-cutting concerns to the selected pattern, ensuring the software architecture remains reliable and scalable.

Can I use this to document architectural decisions and technology stack guidance?▼

Document architectural decisions and technology stack guidance by generating ADRs and mapping core components, ensuring software architecture choices satisfy business requirements and reduce rework.

Related Skills

Explore More Software Engineering Skills→
HechaoYannetHechaoYannet

create-architecture

Generate a master architecture document from GDDs, ADRs, and governance constraints.

Community
Advanced
Prathmesh2000Prathmesh2000
1

lld-writer

Generates Low-Level Design documents outlining class structures, data flows, and API contracts.

Community
Advanced
mzniumzniu
7

tech_evaluation

Assess technology readiness, scalability, security, and architectural risks in a structured report.

Community
Advanced
oalansilvaoalansilva

domain-modeling

Identify and define domains and bounded contexts for complex software systems.

Community
Advanced