Loading...
Loading...
Found 66 Skills
Consult this skill when designing client-server systems or API architectures. Use when traditional web/mobile applications with centralized services, clear separation between client and server responsibilities needed. Do not use when selecting from multiple paradigms - use architecture-paradigms first. DO NOT use when: peer-to-peer dominates - consider dedicated P2P patterns.
Agent skill for arch-system-design - invoke with $agent-arch-system-design
Produce a high-level technical design with architecture diagram, component responsibilities, data flow, and test scenario map. Use after the product intent specification is approved.
Explain a piece of code, a subsystem, or an architectural concept in the codebase, grounded in real files. Use when user says 'explain this', 'walk me through X', 'how does Y work', 'what does this module do', 'help me understand the Z flow', or 'onboard me on this component'. Do NOT use for writing permanent docs (use write-doc or arc42) or for code review (use review-diff).
System Architect Specialist. Use this to design system architecture, creating C4 models and ADRs (Decision Records).
Cloud design patterns for distributed systems architecture covering 42 industry-standard patterns across reliability, performance, messaging, security, and deployment categories. Use when designing, reviewing, or implementing distributed system architectures.