architecture-patterns
System and API design guidance covering component boundaries, data flow, integration patterns, and scalability considerations.
Best use case
architecture-patterns is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
System and API design guidance covering component boundaries, data flow, integration patterns, and scalability considerations.
Teams using architecture-patterns should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/architecture-patterns/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How architecture-patterns Compares
| Feature / Agent | architecture-patterns | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
System and API design guidance covering component boundaries, data flow, integration patterns, and scalability considerations.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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)
Related Skills
parallel-patterns
GPU parallel algorithm design patterns and implementations. Implement parallel reduction, scan/prefix sum, histogram, parallel sort algorithms, stream compaction, and work-efficient patterns optimized for specific GPU architectures.
architecture-analyzer
Analyze and visualize software architecture patterns, dependencies, and module boundaries for migration planning
planning-patterns
Structured planning methodology with research, brainstorming, phased plan creation, risk assessment, and plan-to-build continuity.
debugging-patterns
Root cause analysis frameworks including log-first investigation, git bisect correlation, and pattern-based diagnosis with confidence scoring.
code-review-patterns
Multi-dimensional code assessment across security, quality, performance, and maintainability with confidence-gated reporting (>=80%) and Router Contract generation.
Architecture Design
Design comprehensive system architecture with technology selection and ADRs.
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
yolo
Run Babysitter autonomously with minimal manual interruption.
user-install
Install the user-level Babysitter Codex setup.
team-install
Install the team-pinned Babysitter Codex workspace setup.
retrospect
Summarize or retrospect on a completed Babysitter run.