Choose and implement iOS architecture patterns (MVVM, TCA, Clean Architecture) based on feature complexity. Use when designing architecture for new features or refactoring existing code.
Use when invalid data causes failures deep in execution, requiring validation at multiple system layers - validates at every layer data passes through to make bugs structurally impossible
Maintain Structurizr C4 architecture diagrams in sync with code changes. Use when adding components, modifying relationships, changing architectural boundaries, or implementing new patterns. Ensures workspace.dsl accurately reflects the current system architecture.
Reviews technical proposals and architectural decisions against 30 complexity dimensions. Use when user proposes technical solutions, designs systems, or evaluates architectural choices. Questions necessity of scale, consistency, resilience, and other complexity drivers. Pushes for simplest viable approach. Use when: - User proposes specific technologies (Kafka, microservices, event sourcing, etc.) - Designing new systems or features - Evaluating architectural trade-offs - Someone says "we need" followed by complex infrastructure Do NOT use when: - Simple feature implementation (use hamburger-method or story-splitting instead) - Work is already planned and simple - User asks "how to" implement something specific (use micro-steps-coach instead)
PolicyEngine parameter patterns - YAML structure, naming conventions, metadata requirements, federal/state separation
Core Go programming concepts - syntax, types, interfaces, error handling
Design and implement service layer classes for Frappe Framework v15 with proper business logic separation. Triggers: "create service", "add service layer", "frappe service", "business logic", "/frappe-service". Generates service classes with validation, orchestration, and integration patterns.
Expert guidance on Swift Concurrency best practices, patterns, and implementation. Use when developers mention: (1) Swift Concurrency, async/await, actors, or tasks, (2) "use Swift Concurrency" or "modern concurrency patterns", (3) migrating to Swift 6, (4) data races or thread safety issues, (5) refactoring closures to async/await, (6) @MainActor, Sendable, or actor isolation, (7) concurrent code architecture or performance optimization, (8) concurrency-related linter warnings (SwiftLint or similar; e.g. async_without_await, Sendable/actor isolation/MainActor lint).
Structured ADR creation in MADR format. Use when creating architecture decision records, documenting technology choices, or when user mentions ADR, Architecture Decision, ๆฑบๅฎ่จ้ฒ, ๆ่ก้ธๅฎ, ใขใผใญใใฏใใฃๆฑบๅฎ, deprecation, ้ๆจๅฅจๅ.
Resource safety with acquireRelease, Effect.scoped, and finalizers. Use when opening files, sockets, servers, or external handles.
Structured ADR creation in MADR format. Triggers: ADR, Architecture Decision, ๆฑบๅฎ่จ้ฒ, ๆ่ก้ธๅฎ, ใขใผใญใใฏใใฃๆฑบๅฎ, design decision, ๆ่ก็ๆฑบๅฎ, ่จญ่จๅคๆญ, deprecation, ้ๆจๅฅจๅ, process change, ใใญใปในๅคๆด
Complete HUMMBL Base120 mental models framework with all 120 models across 6 transformations (Perspective, Inversion, Composition, Decomposition, Recursion, Meta-Systems). Includes model selection guidance, application methodology, and validation checklist. Version 1.0-beta definitive reference.
Sage ็ฌๆ็ๆฃๆฅ็น็ณป็ป่ฎพ่ฎก๏ผๅ ๅซ็ถๆๅฟซ็ งใๆไปถ่ฟฝ่ธชใๅๆปๆขๅคๆบๅถ
Sage ไผ่ฏ็ฎก็ๅผๅๆๅ๏ผๆถต็ไผ่ฏๆไน ๅใๅๆฏใ็ผๅญใๅญๅจๅ็ซฏ
Sage MCP ๅ่ฎฎๅผๅๆๅ๏ผๆถต็ๅฎขๆท็ซฏใไผ ่พๅฑใๆๅกๅ็ฐใ้็ฅๅค็
Apply cloud-native architecture patterns. Use when designing for scalability, resilience, or cloud deployment. Covers microservices, containers, and distributed systems.
๋ฐฑ๊ทธ๋ผ์ด๋์์ ์ฌ๋ฌ ์์ด์ ํธ๊ฐ ๋ณ๋ ฌ๋ก ๊ตฌํ ์์ ์ ์ํํฉ๋๋ค. ๊ธฐํ ๋ฌธ์๋ฅผ ๊ธฐ๋ฐ์ผ๋ก ๋ ๋ฆฝ์ ์ธ ์์ ์ ๋ถ๋ฆฌํ๊ณ , ๊ฐ ์์ด์ ํธ๊ฐ ์ง์ ์ฝ๋๋ฅผ ์์ฑํฉ๋๋ค. ์ปจํ ์คํธ ์ ํ์๋ ์์ ํฉ๋๋ค. "๋ฐฑ๊ทธ๋ผ์ด๋ ๊ตฌํ", "bg impl", "๋ณ๋ ฌ ๊ตฌํ" ์์ฒญ ์ ํ์ฑํ๋ฉ๋๋ค.
Apply Gang of Four and architectural patterns appropriately to solve common software design problems
Design disaster recovery strategies including backup, failover, RTO/RPO planning, and multi-region deployment for business continuity.
Senior Ruby developer using functional programming techniques. Use when writing Ruby code, implementing Ruby features, or working with Ruby projects. Follows TDD methodology via development skill. Used as a part of the XP skill.
Use this to create or modify architecture decision records (ADRs)
Queue and PubSub patterns, background fibers, and graceful shutdown. Use for decoupling producers/consumers.
Systematic approach to implementing new features in the Rust memory system following project conventions. Use when adding new functionality with proper testing and documentation.
Sage ้กน็ฎ Rust ไปฃ็ ่ง่๏ผๅ ๅซๅฝๅใ้่ฏฏๅค็ใๅผๆญฅใๆต่ฏ็ญๆไฝณๅฎ่ทต
