How does this skill help with architectural decision-making?

The skill provides specific, opinionated recommendations based on your current constraints (like team size and user count) rather than giving generic 'it depends' answers.

Is this skill useful for small teams or startups?

Yes, it specifically highlights when to avoid complex patterns like microservices or Event Sourcing to maintain development speed during early stages.

Does it support Clean Architecture and Hexagonal patterns?

Absolutely. It provides rules for dependency direction and layer organization to help you build systems where business logic is decoupled from frameworks and databases.

Can it help me choose between a monolith and microservices?

Yes, it includes a clear decision flowchart that uses developer count and product-market fit to determine the most efficient architecture for your specific situation.

Architecture Patterns & System Design

Name: Architecture Patterns & System Design
Author: criptogus

bycriptogus

•

API Development

Provides objective architectural recommendations and implementation patterns for building scalable, maintainable software systems.

This skill empowers developers to make decisive architectural choices by providing clear, opinionated guidance on system design. Instead of offering vague trade-offs, it utilizes specific criteria—such as team size, user load, and business maturity—to recommend the best path forward between monoliths, modular monoliths, and microservices. It features detailed blueprints for Clean Architecture, CQRS, and Event Sourcing, helping architects and leads establish robust foundations or refactor legacy systems with confidence and technical clarity.

Key Features

01Structural blueprints for Clean Architecture and Hexagonal design patterns.

02Implementation guides for CQRS to separate read and write responsibilities.

03Objective decision-making frameworks for Monolith vs. Microservices based on team constraints.

045 GitHub stars

05Event Sourcing patterns for comprehensive audit logs and system state reconstruction.

06Guidance on synchronous vs. asynchronous communication for service interoperability.

Use Cases

01Evaluating whether to migrate to microservices based on team growth and infrastructure readiness.

02Optimizing high-traffic platforms by implementing CQRS read models for better query performance.

03Designing a new backend service using Clean Architecture to ensure long-term framework independence.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add criptogus/liquid-ai architecture-patterns

For use in Claude.ai and ChatGPT

Download Skill