architecture-patterns
System and API design guidance covering component boundaries, data flow, integration patterns, and scalability considerations.
Source facts
- Repository
- a5c-ai/babysitter
- Last source activity
- June 1, 2026 at 07:46
- Detected SKILL.md language
- English
- Stars
- 1,813
- Forks
- 111
Install options
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Review the source files
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
File Explorer
2 filesShowing SKILL.md
SKILL.md
Source instructions · Read-only preview- name
- architecture-patterns
- description
- System and API design guidance covering component boundaries, data flow, integration patterns, and scalability considerations.
- allowed-tools
- Read, Write, Edit, Bash, Grep, Glob, WebSearch
- graph
- {"domains":["domain:software-engineering"],"skillAreas":["skill-area:agentic-loops","skill-area:orchestration-loop"],"workflows":["workflow:feature-development"],"topics":["topic:developer-experience"],"roles":["role:tech-lead","role:backend-engineer"]}
- 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)
View on GitHub