← Voltar para o catálogo
Orientação de design de sistema e API que abrange limites de componentes, fluxo de dados, padrões de integração e considerações de escalabilidade.
Ver no GitHub ↗
Licença: MIT
Como adicionar
/plugin marketplace add a5c-ai/babysitter
O comando exato pode variar conforme o repositório. Confira o README no GitHub.
Para o autor da skill
Cole no README do seu repo
Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.
[](https://www.skillteca.com.br/skills/architecture-patterns)
利用AI大模型,一键生成高清短视频 Generate short videos with one click using AI LLM.
Automação
por harry0703
Creates an SVG weather card showing the current temperature for Dubai. Writes the SVG to orchestration-workflow/weather.svg and updates orchestration-workflow/output.md.
Automação
#ai
por shanraisshan
Automate Asana tasks via Rube MCP (Composio): tasks, projects, sections, teams, workspaces. Always search tools first for current schemas.
Automação
#git
#github
por sickn33
Integrate Stripe, PayPal, and payment processors. Handles checkout flows, subscriptions, webhooks, and PCI compliance. Use PROACTIVELY when implementing payments, billing, or subscription features.
Automação
#git
#github
por sickn33
Alerta por categoria
1 email curto, só com as skills novas de Automação. 4 minutos de leitura, sem spam, cancela com 1 clique.
Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.
Ler descrição completaRecolher descrição
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)
Compartilhar
X
LinkedIn