skills.rest
CoreStack-Engg
CoreStack-EnggOFFICIAL
Explore all skills by this author →
GitHub

architecture

Compare system architecture options and document decisions with ADRs.

Updated Mar 13, 2026
Search Tags:#architecture#scalability#microservices#adr#api-design#system-design#c4-model
One-click install
npx skills add https://github.com/CoreStack-Engg/claude-plugins --skill architecture-corestack-engg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/CoreStack-Engg/claude-plugins/tree/main/plugins/architecture/skills/architecture
Command: npx skills add https://github.com/CoreStack-Engg/claude-plugins --skill architecture-corestack-engg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

System architects struggle to choose and justify design options for scalable, resilient distributed systems; this skill helps evaluate trade-offs, capture decisions, and communicate architecture clearly.

Core Features & Use Cases

  • Catalog of architectural styles (Microservices, Event-Driven, CQRS, Hexagonal) with pros/cons and trade-offs
  • ADR templates and documentation practices for decisions that need future governance
  • Guidance on API design principles, quality attributes (scalability, reliability, security), and C4 model usage

Quick Start

Document the architecture for a new service using ADRs and C4 diagrams to capture decisions.

Frequently Asked Questions about architecture

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

FAQPage Schema
How do I choose between a monolith and microservices for my system architecture?▼

To choose between a monolith and microservices, evaluate architectural trade-offs using this skill to compare scalability, resilience, and operational complexity. It catalogs architectural styles with specific pros and cons to help justify your distributed system design decisions.

What is the best way to document architecture decisions for future governance?▼

The best way to document architecture decisions is by using Architecture Decision Records (ADRs). This skill provides ADR templates and documentation practices to capture trade-offs and design choices, ensuring decisions are traceable for future governance.

How do I model and communicate a new service architecture clearly?▼

To model and communicate a new service architecture, apply the C4 model. This skill guides you on C4 model usage to visually describe system context, containers, and components, making complex distributed architectures easier to understand.

When should I use event-driven or CQRS patterns in my system design?▼

You should use event-driven or CQRS patterns when building scalable distributed systems that require high throughput or segregated read/write workloads. This skill catalogs these architectural patterns with their specific trade-offs and quality attributes.

How do I define API design principles for a microservices architecture?▼

To define API design principles for a microservices architecture, use this skill to access guidance on API contracts and quality attributes like reliability and security. It helps establish clear communication boundaries between distributed services.

Related Skills

Explore More Software Engineering Skills→
EnigmaWUEnigmaWU
1

define-architectural-drivers

Translate raw product requirements into architectural drivers for system design.

Community
Advanced
shakhovskiya-createshakhovskiya-create

architecture

Generate C4 architecture designs and ADRs from an approved PRD.

Community
Advanced
imMamdouhaboammarimMamdouhaboammar

agency-devops-automator

Automate infrastructure provisioning and CI/CD pipeline development.

Community
Advanced
alessioroberto82alessioroberto82

arch

Design system architecture and document decisions with ADRs.

Community
Advanced