architecture-patterns

Document software architecture patterns for scalable systems.

3|3|Updated Jan 4, 2026

Search Tags:#architecture #scalability #microservices #migration #patterns #orchestration #software-design

Ready to run

npx skills add https://github.com/adaptive-enforcement-lab/claude-skills --skill architecture-patterns-adaptive-enforcement-lab

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-patterns
Source: https://github.com/adaptive-enforcement-lab/claude-skills/tree/main/plugins/patterns/skills/architecture-patterns
Command: npx skills add https://github.com/adaptive-enforcement-lab/claude-skills --skill architecture-patterns-adaptive-enforcement-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design teams struggle with maintaining scalable architectures as systems grow. This set of fundamental patterns provides proven principles to structure software for readability, resilience, and evolvability.

Core Features & Use Cases

Separation of Concerns: Single-responsibility components with clear boundaries.
Hub and Spoke: Central orchestration with distributed execution.
Strangler Fig: Incremental migration from legacy systems.
Three-Stage Design: Separate discovery, execution, and reporting.
Matrix Distribution: Parallel processing and scalability.

Quick Start

Review the architecture patterns guide to begin structuring a new system with separation, orchestration, and incremental migration.

Frequently Asked Questions about architecture-patterns

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

FAQPage Schema

What are proven software design patterns for building scalable microservices?▼

Separation of Concerns establishes single-responsibility components with clear boundaries, while Hub and Spoke provides central orchestration with distributed execution. These patterns structure distributed systems for readability, resilience, and evolvability.

How do I incrementally migrate from a legacy system without downtime?▼

To incrementally migrate from a legacy system, apply the Strangler Fig pattern. This proven approach allows incremental migration by gradually replacing legacy functionality with new services, ensuring safe transitions without disrupting the entire system.

What is the best way to orchestrate distributed execution in large-scale applications?▼

The best way to orchestrate distributed execution in large-scale applications is the Hub and Spoke pattern. It provides central orchestration for coordinating distributed execution across microservices, ensuring clear boundaries and reliable system operations.

How do I structure a system for parallel processing and scalability?▼

Use the Matrix Distribution pattern to structure a system for parallel processing and scalability. This architecture pattern enables parallel processing across distributed systems, allowing large-scale applications to handle increased workloads effectively.

When should I separate discovery, execution, and reporting in software architecture?▼

You should separate discovery, execution, and reporting when applying the Three-Stage Design pattern. This architecture pattern isolates these core operations, addressing design concerns for clear boundaries and observability in distributed systems.

nkseth

legacy-modernizer

Document legacy system architecture and define an incremental migration strategy.

Community

Advanced

chicanoandres702

llm-application-dev-langchain-agent

Implement LangChain 0.1+ and LangGraph agent workflows with async patterns, error handling, observability, security, and deployment readiness across plan-and-execute, React, and multi-agent orchestration architectures.

Community

Advanced