architecture-patterns

Guide software architecture pattern selection across monolith, microservices, and API designs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/seqis/OpenClaw-Skills-Converted-From-Claude-Code --skill architecture-patterns-seqis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-patterns
Source: https://github.com/seqis/OpenClaw-Skills-Converted-From-Claude-Code/tree/main/skills_tree/architecture-patterns
Command: npx skills add https://github.com/seqis/OpenClaw-Skills-Converted-From-Claude-Code --skill architecture-patterns-seqis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides guidance on selecting and implementing appropriate software architecture patterns, helping developers make informed decisions for scalable and maintainable systems.

Core Features & Use Cases

  • Pattern Selection: Offers a decision framework based on scale, complexity, and constraints.
  • Pattern Deep Dive: Details various architectural styles like Monolith, Modular Monolith, and Microservices.
  • API & Data Patterns: Explains REST, GraphQL, gRPC, Repository, CQRS, and Event Sourcing.
  • Use Case: A startup is deciding how to structure their new application. They can use this Skill to understand the trade-offs between a monolith and microservices based on their current team size and expected growth.

Quick Start

Use the architecture-patterns skill to help decide between a modular monolith and microservices for a growing application.

Frequently Asked Questions about architecture-patterns

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

FAQPage Schema
How do I choose between monolith and microservices architecture for my application?

Choosing between monolith and microservices architecture depends on your scale, complexity, and constraints. This skill provides a decision framework evaluating team size, expected growth, and trade-offs to guide your architectural pattern selection.

What are the differences between REST, GraphQL, and gRPC for API design?

REST, GraphQL, and gRPC are API design patterns with distinct data access characteristics. This skill explains these approaches to help you select the appropriate API architecture based on your system requirements.

When should I use CQRS and Event Sourcing in my data access layer?

CQRS and Event Sourcing are data access patterns suited for complex, scalable systems. This skill details these patterns alongside the Repository pattern to facilitate informed architectural decision-making for your data layer.

How do I implement Clean Architecture in a modular monolith?

Implementing Clean Architecture in a modular monolith involves structuring your application into distinct layers. This skill guides you through layered architectures and modular structuring to build maintainable and scalable systems.

What are common software architecture anti-patterns to avoid?

Software architecture anti-patterns are flawed design choices that reduce maintainability. This skill covers design principles and anti-patterns, helping you identify and avoid architectural decisions that negatively impact system scalability.

Does this architecture guide help startups deciding on their initial application structure?

Yes, this architecture guide helps startups decide on application structure by comparing a monolith and microservices. It offers a decision framework based on current team size and expected growth to support informed architectural decision-making.