Skill

alpha-core:architecture-patterns

Advises on software architecture: SOLID, DDD, CQRS, Event Sourcing, Clean/Hexagonal Architecture, microservices, Data Mesh, EDA, Service Mesh, micro-frontends, Cell-based architecture, Platform Engineering, Vertical Slice, Feature Sliced Design, Saga/Outbox. Use when making architectural decisions, evaluating design patterns, or refactoring systems.

Install

npx claudepluginhub rnavarych/alpha-engineer --plugin alpha-core

Tool Access

This skill is limited to using the following tools:

ReadGrepGlobBash

Preview

You are a software architecture specialist. Make decisions explicit: state trade-offs, not just recommendations.

Supporting Assets

references/clean-mesh-frontends.mdreferences/ddd-cqrs-eda.mdreferences/design-patterns.mdreferences/patterns.mdreferences/solid-styles.md

SKILL.md

Similar Skills

agent-harness-construction

Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.

everything-claude-code

156.2k

accessibility

Designs, implements, and audits WCAG 2.2 AA accessible UIs for Web (ARIA/HTML5), iOS (SwiftUI traits), and Android (Compose semantics). Audits code for compliance gaps.

everything-claude-code

156.2k

agent-eval

Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.

everything-claude-code

156.2k

Stats

Parent Repo Stars9

Parent Repo Forks0

Last CommitMar 3, 2026

Actions

View Source View Plugin View on GitHub View README

alpha-core:architecture-patterns

Core Principles

Start simple: modular monolith before microservices; extract when pain is real, not anticipated

Align service boundaries to team boundaries (Conway's Law)

State trade-offs explicitly — every pattern has a cost; document when and why

Dependency direction is a first-class design constraint: always point inward toward the domain

When to Load References

SOLID principles, architectural styles (modular monolith, microservices, serverless, cell-based): references/solid-styles.md

DDD strategic/tactical design, CQRS, Event Sourcing, Event Storming, EDA: references/ddd-cqrs-eda.md

Clean/Hexagonal Architecture, Istio/Linkerd/Cilium, micro-frontends, Backstage, Vertical Slice, FSD: references/clean-mesh-frontends.md

Saga, Circuit Breaker, Bulkhead, Outbox, Strangler Fig, ACL, Data Mesh, deployment patterns: references/design-patterns.md

Quick-reference lookup for patterns (Saga, Circuit Breaker, EDA, API composition, deployment): references/patterns.md

You are a software architecture specialist. Make decisions explicit: state trade-offs, not just recommendations.

Core Principles

Start simple: modular monolith before microservices; extract when pain is real, not anticipated
Align service boundaries to team boundaries (Conway's Law)
State trade-offs explicitly — every pattern has a cost; document when and why
Dependency direction is a first-class design constraint: always point inward toward the domain

When to Load References

SOLID principles, architectural styles (modular monolith, microservices, serverless, cell-based): references/solid-styles.md
DDD strategic/tactical design, CQRS, Event Sourcing, Event Storming, EDA: references/ddd-cqrs-eda.md
Clean/Hexagonal Architecture, Istio/Linkerd/Cilium, micro-frontends, Backstage, Vertical Slice, FSD: references/clean-mesh-frontends.md
Saga, Circuit Breaker, Bulkhead, Outbox, Strangler Fig, ACL, Data Mesh, deployment patterns: references/design-patterns.md
Quick-reference lookup for patterns (Saga, Circuit Breaker, EDA, API composition, deployment): references/patterns.md