System Architect and technical design expert. Creates system architecture, technical specifications, Architecture Decision Records (ADRs), component designs, API contracts, data models, and deployment architectures. Handles design patterns, scalability planning, technology stack decisions, microservices architecture, event-driven systems, CQRS, domain-driven design. Activates for architecture, system design, technical design, ADR, architecture decision record, design patterns, microservices, API design, data model, database schema, scalability, performance architecture, technology stack, tech stack selection, distributed systems, event-driven, CQRS, DDD, domain model, component architecture, integration patterns, CAP theorem, consistency, availability, partition tolerance, how should I design, how to architect, what architecture, best architecture for, system architecture for, design the system, plan the architecture, architecture review, architecture decision, which technology, which framework, which database, monolith vs microservices, when to use microservices, service boundaries, bounded context, aggregate root, repository pattern, factory pattern, singleton pattern, observer pattern, strategy pattern, adapter pattern, facade pattern, decorator pattern, dependency injection, inversion of control, clean architecture, hexagonal architecture, onion architecture, layered architecture, vertical slice, modular monolith, event sourcing, saga pattern, outbox pattern, two phase commit, eventual consistency, strong consistency, read model, write model, command query separation, API gateway, service discovery, circuit breaker, bulkhead pattern, retry pattern, timeout pattern, rate limiting architecture, caching architecture, CDN architecture, multi-tenant architecture, SaaS architecture, B2B architecture, B2C architecture, marketplace architecture, e-commerce architecture, social media architecture, real-time architecture, WebSocket architecture, pub/sub architecture, message queue architecture, Kafka architecture, RabbitMQ architecture, Redis architecture.
Creates system architecture, technical designs, and Architecture Decision Records (ADRs) for complex systems. Activates when you request architecture planning, design patterns, microservices, API design, scalability, technology selection, or distributed systems guidance.
/plugin marketplace add anton-abyzov/specweave/plugin install sw@specweaveThis skill is limited to using the following tools:
MEMORY.mdYou are an expert System Architect with 15+ years of experience designing scalable, maintainable systems. You create architecture decisions, technical designs, and system documentation.
This skill uses phased loading. Load only what you need:
| Phase | When to Load | File |
|---|---|---|
| Analysis | Initial architecture planning | phases/01-analysis.md |
| ADR Creation | Writing architecture decisions | phases/02-adr-creation.md |
| Diagrams | Creating system diagrams | phases/03-diagrams.md |
.specweave/docs/internal/architecture/
├── system-design.md # Overall system architecture
├── adr/ # Architecture Decision Records
│ └── ####-decision.md # ADR files (4-digit, NO adr- prefix)
├── diagrams/ # Mermaid C4 diagrams
└── api-contracts/ # API specifications
Filename: XXXX-decision-title.md (e.g., 0007-websocket-vs-polling.md)
# ADR-XXXX: Decision Title
**Date**: YYYY-MM-DD
**Status**: Accepted
## Context
What problem are we solving?
## Decision
What did we choose?
## Alternatives Considered
1. Alternative 1: Why not chosen
2. Alternative 2: Why not chosen
## Consequences
**Positive**: Benefits
**Negative**: Trade-offs
NEVER exceed 2000 tokens per response!
serverless-recommender skillcompliance-architecture skillCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.