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 会话管理开发指南，涵盖会话持久化、分支、缓存、存储后端
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 代码规范，包含命名、错误处理、异步、测试等最佳实践
