system-design-patterns
Common system design patterns and architectures
What this skill does
# System Design Patterns Skill
Common patterns for designing scalable systems.
## Architectural Patterns
### Layered Architecture
```
┌─────────────────────────────┐
│ Presentation Layer │ UI, API endpoints
├─────────────────────────────┤
│ Application Layer │ Business logic, use cases
├─────────────────────────────┤
│ Domain Layer │ Entities, business rules
├─────────────────────────────┤
│ Infrastructure Layer │ Database, external services
└─────────────────────────────┘
```
```typescript
// Presentation Layer
@Controller('users')
class UserController {
constructor(private userService: UserService) {}
@Get(':id')
getUser(@Param('id') id: string) {
return this.userService.findById(id)
}
}
// Application Layer
class UserService {
constructor(private userRepository: UserRepository) {}
async findById(id: string): Promise<User> {
return this.userRepository.findById(id)
}
}
// Domain Layer
class User {
constructor(
public id: string,
public email: string,
public name: string
) {}
updateEmail(newEmail: string) {
// Business validation
if (!this.isValidEmail(newEmail)) {
throw new ValidationError('Invalid email')
}
this.email = newEmail
}
}
// Infrastructure Layer
class TypeOrmUserRepository implements UserRepository {
async findById(id: string): Promise<User | null> {
return this.repository.findOne({ where: { id } })
}
}
```
### Microservices
```
┌─────────────┐
│ API Gateway │
└──────┬──────┘
┌───────────────┼───────────────┐
▼ ▼ ▼
┌────────────┐ ┌────────────┐ ┌────────────┐
│ User │ │ Order │ │ Payment │
│ Service │ │ Service │ │ Service │
└────────────┘ └────────────┘ └────────────┘
│ │ │
▼ ▼ ▼
┌────────────┐ ┌────────────┐ ┌────────────┐
│ User DB │ │ Order DB │ │ Payment DB │
└────────────┘ └────────────┘ └────────────┘
```
### Event-Driven Architecture
```typescript
// Event definition
interface OrderCreatedEvent {
orderId: string
userId: string
items: OrderItem[]
total: number
createdAt: Date
}
// Publisher
class OrderService {
async createOrder(data: CreateOrderDTO): Promise<Order> {
const order = await this.repository.save(data)
await this.eventBus.publish('order.created', {
orderId: order.id,
userId: order.userId,
items: order.items,
total: order.total,
createdAt: order.createdAt
})
return order
}
}
// Subscribers
class InventoryService {
@OnEvent('order.created')
async reserveInventory(event: OrderCreatedEvent) {
for (const item of event.items) {
await this.inventory.reserve(item.productId, item.quantity)
}
}
}
class NotificationService {
@OnEvent('order.created')
async sendConfirmation(event: OrderCreatedEvent) {
const user = await this.userService.findById(event.userId)
await this.email.send(user.email, 'Order Confirmation', { order: event })
}
}
```
## Data Patterns
### CQRS (Command Query Responsibility Segregation)
```typescript
// Commands (Write side)
class CreateUserCommand {
constructor(public email: string, public name: string) {}
}
class CreateUserHandler {
async execute(command: CreateUserCommand) {
const user = new User(uuid(), command.email, command.name)
await this.writeRepository.save(user)
await this.eventBus.publish(new UserCreatedEvent(user))
}
}
// Queries (Read side)
class GetUserQuery {
constructor(public userId: string) {}
}
class GetUserHandler {
async execute(query: GetUserQuery) {
return this.readRepository.findById(query.userId)
}
}
// Read model updated by events
class UserProjection {
@OnEvent('user.created')
async onUserCreated(event: UserCreatedEvent) {
await this.readModel.insert({
id: event.userId,
email: event.email,
name: event.name,
createdAt: event.createdAt
})
}
}
```
### Event Sourcing
```typescript
// Events are the source of truth
interface Event {
id: string
aggregateId: string
type: string
data: any
timestamp: Date
version: number
}
// Account aggregate
class Account {
private balance: number = 0
private events: Event[] = []
deposit(amount: number) {
this.apply(new MoneyDepositedEvent(this.id, amount))
}
withdraw(amount: number) {
if (this.balance < amount) {
throw new InsufficientFundsError()
}
this.apply(new MoneyWithdrawnEvent(this.id, amount))
}
// Rebuild state from events
static fromEvents(events: Event[]): Account {
const account = new Account()
for (const event of events) {
account.applyEvent(event)
}
return account
}
private applyEvent(event: Event) {
switch (event.type) {
case 'MoneyDeposited':
this.balance += event.data.amount
break
case 'MoneyWithdrawn':
this.balance -= event.data.amount
break
}
}
}
```
## Integration Patterns
### API Gateway
```typescript
// Route requests to appropriate services
const routes = {
'/api/users/*': 'http://user-service:3001',
'/api/orders/*': 'http://order-service:3002',
'/api/products/*': 'http://product-service:3003'
}
// Gateway middleware
app.use('/api/*', async (req, res) => {
const service = matchRoute(req.path, routes)
// Authentication
const user = await authenticate(req.headers.authorization)
// Rate limiting
await rateLimiter.check(user.id)
// Proxy request
const response = await proxy(service, {
...req,
headers: {
...req.headers,
'x-user-id': user.id
}
})
res.status(response.status).json(response.data)
})
```
### Circuit Breaker
```typescript
class CircuitBreaker {
private failures = 0
private lastFailure: Date | null = null
private state: 'closed' | 'open' | 'half-open' = 'closed'
async call<T>(fn: () => Promise<T>): Promise<T> {
if (this.state === 'open') {
if (this.shouldReset()) {
this.state = 'half-open'
} else {
throw new CircuitOpenError()
}
}
try {
const result = await fn()
this.onSuccess()
return result
} catch (error) {
this.onFailure()
throw error
}
}
private onSuccess() {
this.failures = 0
this.state = 'closed'
}
private onFailure() {
this.failures++
this.lastFailure = new Date()
if (this.failures >= this.threshold) {
this.state = 'open'
}
}
private shouldReset(): boolean {
return Date.now() - this.lastFailure!.getTime() > this.timeout
}
}
```
### Saga Pattern
```typescript
// Distributed transaction coordination
class OrderSaga {
async execute(orderData: CreateOrderDTO) {
const steps = [
{ action: () => this.reserveInventory(orderData), compensate: () => this.releaseInventory(orderData) },
{ action: () => this.processPayment(orderData), compensate: () => this.refundPayment(orderData) },
{ action: () => this.createOrder(orderData), compensate: () => this.cancelOrder(orderData) },
{ action: () => this.sendConfirmation(orderData), compensate: () => {} }
]
const completed: typeof steps = []
try {
for (const step of steps) {
await step.action()
completed.push(step)
}
} catch (error) {
// Compensate in reverse order
for (const step of completed.reverse()) {
await step.compensate()
}
throw error
}
}
}
```
## Scalability Patterns
### Horizontal Scaling
```yaml
# Kubernetes deployment
apiVersion: apps/v1
kind: Deployment
metadata:
name: api-service
spec:
replicas: 3
selector:
matchLabels:
app: api-service
template:
spec:
containers:
- name: api
image: api-service:latest
resources:
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.