Loading...
Loading...
Found 25 Skills
Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
Use when designing system architecture, choosing between monolith/microservices/serverless, planning scalability, or making technology decisions. Covers microservices, event-driven, CQRS, modular monoliths, distributed systems, and reliability patterns for production-grade software.
Design scalable, reliable software systems. Use when planning new systems, major features, or architecture changes. Covers C4 diagrams, trade-off analysis, and system decomposition.
Design, evaluate, and document software architecture patterns
Activates the Technical Writer to generate, update, or refactor internal project documentation. Use when creating READMEs, ADRs, or technical guides.
Principal Solution Architect with 15+ years designing scalable distributed systems. Use when making technology choices, designing system architecture, selecting patterns (Saga, CQRS, Event Sourcing), creating ADRs, planning integrations, or addressing scalability concerns.
Collaborative design phase for feature lifecycle: explore requirements, discuss trade-offs, produce design document. Use when starting a new feature that needs design before implementation. Use for "design feature", "let's think through", "explore approaches", or "/feature-design". Do NOT use for simple bug fixes or tasks that don't need design discussion.
Design optimal cloud architecture based on your platform engineering requirements. Use when planning new services, migrations, or infrastructure changes that must align with organizational standards.
System Architect Specialist. Use this to design system architecture, creating C4 models and ADRs (Decision Records).
Design system architecture and high-level technical strategy
Dimensional modeling and schema design for data products. Star schema patterns, slowly changing dimensions, denormalization decisions, and architecture decision records. Use when designing data models, reviewing schema designs, choosing between normalization strategies, or when someone asks "how should I model this data?" or "should I denormalize?" For OMOP CDM patterns specifically, see healthcare-data-domain.
Designs system architecture and selects technology stack based on vision analysis. Use after vision analysis for technical decisions. Triggers on: design architecture, select tech stack, choose framework.