Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.
Custom repository pattern and DataContext implementation for JSON-based storage with computed columns.
Entity Framework Core best practices for configuration, queries, concurrency, and multi-tenancy.
Improving internal code structure without changing external behavior.
Design production-grade software systems with expert knowledge of architecture patterns, distributed systems, cloud platforms, and operational excellence. Use this skill when architecting complex systems, evaluating technology choices, designing scalable infrastructure, or making critical architectural decisions requiring trade-off analysis.
Principal Software Architect for Rainze. Use when implementing features, writing code, or creating modules. Expert in Python + Rust hybrid architecture with 9 coding commandments.
Validate Clean Architecture implementation in iOS. Checks layer separation (Presentation/Domain/Data), MVVM patterns, dependency injection with Swinject, and UseCase/Repository patterns. Use when reviewing architecture, checking layer boundaries, or validating DI.
Clear escalation procedures and paths for incident response
Simulate and coordinate Ëtrid’s Consensus Day process, aggregating proposals, electorate role weights, quorum rules, and final decision outcomes.
Error handling patterns for try-catch, error boundaries, structured logging, and exception strategies. Trigger: When implementing error handling, when building error boundaries, when setting up logging, when designing error responses, when handling async errors, when creating custom error classes.
Use BEFORE implementing any new domain/feature to ensure proper layered architecture with dependency injection. Prevents mixed concerns and tight coupling.
Enterprise context and session management with token budget optimization and state persistence
Python coding style - pragmatic, readable, fast development over heavy abstraction
Expert API architecture including REST, GraphQL, gRPC design, versioning, and documentation
Generates business logic layer components (use cases, repository interfaces, business models, validators) for go-kratos microservices following Clean Architecture. Use when implementing domain logic, creating entity CRUD operations, adding validation rules, or orchestrating data access in kratos services.
Comprehensive Spring Boot 3.x best practices for building scalable, maintainable enterprise applications with Jakarta EE. Use this skill when creating Spring Boot applications, designing REST APIs, implementing security, writing tests, or architecting Spring Boot projects. Covers Controller-Service-Repository patterns, validation, error handling, testing strategies, performance optimization, and production-ready configurations.
Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.
Review and fix Swift concurrency issues (async/await, actors, Sendable, isolation). Use when the user needs concurrency correctness or performance remediation in Swift.
Apply functional and compositional architecture patterns when designing systems, modules, and components. Use when creating architecture definitions, designing system boundaries, defining interfaces, or building modular systems.
Backend entity patterns - services with DI, Drizzle schemas (3-file pattern), ORPC routers, TypeIDs, neverthrow. Use when creating services, schemas, routers, or new entities.
Standardized patterns for creating and reading ZIO configuration using zio-config with magnolia derivation. Use when creating new configuration classes, reading configuration values, or refactoring existing config code to follow project standards.
Design and architect microservices following Chris Richardson's Microservices Patterns. Use when designing services, APIs, data flows, or evaluating architecture decisions. Guides full workflow from feature intake to production-ready design with observability, async patterns, security, testing, and deployment strategies.
Standardized error responses for all failure scenarios. Always transparent, always provide next steps.
Use when designing system architecture, creating design documents, planning technical architecture, or making high-level design decisions. Apply when user mentions system design, architecture, technical design, design docs, or asks to architect a solution. Use proactively when a feature requires architectural planning before implementation.
