Skill1.3k repo starsupdated today

architecture-patterns

Architecture Patterns provides guidance for system and API design decisions including component boundaries, data flow, integration approaches, and scalability strategies. Use this skill during the PLAN phase when defining system structure and component interactions, or during BUILD when architectural choices emerge that affect service boundaries, data flow patterns, external dependencies, or public API contracts.

View source Repository: babysitter

Install in Claude Code

Copy

git clone --depth 1 https://github.com/a5c-ai/babysitter /tmp/architecture-patterns && cp -r /tmp/architecture-patterns/library/methodologies/cc10x/skills/architecture-patterns ~/.claude/skills/architecture-patterns

Then start a new Claude Code session; the skill loads automatically.

Definition

SKILL.md

# Architecture Patterns

## Overview

Guidance for system architecture and API design decisions within CC10X workflows. Used during PLAN and BUILD workflows for architectural choices.

## Domain Areas

### Component Design
- Single responsibility boundaries
- Interface contracts and type safety
- Dependency injection patterns
- Module cohesion and coupling analysis

### Data Flow
- Request/response patterns
- Event-driven architecture
- State management strategies
- Data transformation pipelines

### Integration Patterns
- API design (REST, GraphQL, RPC)
- Message queuing and async processing
- Service boundaries and communication
- Error propagation across boundaries

### Scalability
- Horizontal vs vertical scaling considerations
- Caching strategies
- Database design and query optimization
- Load balancing and distribution

## Decision Checkpoints

Architectural decisions require user approval when:
- Introducing new service boundaries
- Changing data flow patterns
- Adding new external dependencies
- Modifying public API contracts

## When to Use

- During PLAN workflow architecture phases
- During BUILD when architectural choices arise
- When reviewing system design in REVIEW workflow

## Agents Used

- `planner` (architecture planning)
- `component-builder` (architecture implementation)
- `code-reviewer` (architecture review)