architecture-patterns
Scannednpx machina-cli add skill a5c-ai/babysitter/architecture-patterns --openclawFiles (1)
SKILL.md
1.6 KB
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)
Source
git clone https://github.com/a5c-ai/babysitter/blob/main/plugins/babysitter/skills/babysit/process/methodologies/cc10x/skills/architecture-patterns/SKILL.mdView on GitHub Overview
Provides guidance on architecture decisions for CC10X workflows, focusing on component boundaries, data flow, integration patterns, and scalability. It guides PLAN and BUILD decisions to align system design with project goals and constraints.
How This Skill Works
The skill codifies four domain areas—component design, data flow, integration patterns, and scalability—and ties them to decision checkpoints. Practitioners use these patterns to evaluate architectural choices, document API contracts, and obtain required approvals before implementing changes.
When to Use It
- During PLAN workflow architecture phases
- During BUILD when architectural choices arise
- When reviewing system design in REVIEW workflow
- When introducing a new service boundary or changing data flow patterns
- When evaluating external dependencies or modifying public API contracts
Quick Start
- Step 1: Map current component boundaries, data flows, and integration points across the system
- Step 2: Choose appropriate API styles (REST/GraphQL/RPC), eventing patterns, and caching needs
- Step 3: Capture decision checkpoints and obtain approvals before implementing changes
Best Practices
- Define clear single responsibility boundaries for all components
- Establish explicit interface contracts and strong typing across modules
- Use dependency injection to decouple components and improve testability
- Analyze cohesion and coupling to guide refactors and scalability decisions
- Document and align API design choices (REST, GraphQL, RPC) with data flow and caching strategies
Example Use Cases
- Choosing service boundaries during PLAN to add a new user-service without affecting existing components
- Implementing event-driven data flow using message queues for asynchronous processing
- Evaluating REST vs GraphQL for a product catalog API based on client needs and data shape
- Applying caching strategies and data transformation pipelines to improve query performance
- Setting up horizontal scaling with load balancing for microservices in a CC10X BUILD phase
Frequently Asked Questions
Add this skill to your agents
