Loading...
Loading...
Found 32 Skills
System architecture and technical design specialist. 🚨 TIER 2 SKILL - ON-DEMAND ACTIVATION 🚨 Use when user requests involve: - System architecture design and planning - Technical specifications and ADRs - Technology evaluation and selection - Scalability and performance planning - Integration architecture and API design - English: "design system", "architecture", "ADR", "tech stack", "scalability" - Swedish: "arkitektur", "systemdesign", "teknikval", "skalbarhet" Architecture Specialist (British female voice) provides: - System design and architecture patterns - Architecture Decision Records (ADRs) - Technology evaluation and trade-off analysis - Cloud and microservices architecture - Integration patterns and API design User confirmation optional but recommended for major architectural decisions.
Expert in designing high-level enterprise solutions. Specializes in TOGAF adaptation, trade-off analysis, and aligning technology with business strategy.
Use when designing new system architecture, reviewing existing designs, or making architectural decisions. Invoke for system design, architecture review, design patterns, ADRs, scalability planning.
Design software architectures with appropriate patterns for scale, maintainability, and team structure. Covers layered, hexagonal, event-driven, CQRS, and modular monolith architectures. Produces architecture decision records, component diagrams, and dependency maps. Prevents over-engineering, premature distribution, and architectural drift.
Research best practices via MCP Ref/Context7/WebSearch and create documentation (guide/manual/ADR/research). Single research, multiple output types.
Systematically evaluate architecture decisions, document trade-offs, and select appropriate patterns. This skill should be used when the user asks about 'architecture decision', 'ADR', 'design pattern selection', 'technology choice', or needs to evaluate architectural trade-offs. Keywords: architecture, ADR, patterns, trade-offs, technical debt, quality attributes, decision record.
Use when designing system architecture, making high-level technical decisions, or planning major system changes. Focuses on structure, patterns, and long-term strategy.
Design, evaluate, and document software architecture patterns
Design scalable, reliable software systems. Use when planning new systems, major features, or architecture changes. Covers C4 diagrams, trade-off analysis, and system decomposition.
Extract architectural decisions from conversations. Identifies problem-solution pairs, trade-off discussions, and explicit choices. Use when analyzing session transcripts for ADR generation.
Guides senior system and solution architecture—cross-service boundaries, integration patterns, non-functional requirements (scale, reliability, security, cost), ADRs, C4-style modeling, architecture review, build-vs-buy, and phased migration (strangler, dual-write). Use when designing multi-service systems, evaluating platform or vendor choices, writing or reviewing architecture decision records, defining standards and principles, or assessing technical risk across domains—not for single-service RFCs and module design (senior-software-engineer), data platform or mesh decisions (data-architect), cloud landing zone, Well-Architected, and migration architecture (cloud-architect), cloud/IaC implementation (infrastructure-engineer, cloud-engineer), internal developer platform product (platform-engineer), or program tracking (technical-program-manager). For business strategy and cases, use business-consultant; for applied AI (RAG, agents, copilots), use applied-ai-architect-commercial-enterprise.
Guardião da arquitetura de software no SynkOS. Use esta skill quando o usuário pedir para propor ou revisar a arquitetura de um sistema, avaliar tradeoffs entre tecnologias ou abordagens, criar um ADR (Architecture Decision Record), desenhar um modelo de dados ou contrato de API, ou fazer perguntas como "qual stack usar para X?", "como estruturar esse serviço?", "quais são os tradeoffs de Y vs Z?", "documente as decisões técnicas", "revise essa arquitetura". Ative também para discovery brownfield (entender o que já existe antes de propor mudanças), para cross-cutting concerns como segurança e performance, e para revisar designs propostos pelas equipes de implementação.