Stateless conversation management with database-backed history, message persistence, and scalable architecture. Use when handling chat state, loading history, or building stateless APIs.
Skill for structuring requirements based on Domain-Driven Design (DDD) principles. Used for (1) defining bounded contexts and aggregates, (2) establishing ubiquitous language, and (3) clarifying domain responsibilities for ADRs, System Contexts, or Design Docs.
Generate service objects for complex business logic. Use when controller/model is too fat, multiple models interaction, external API calls, or says "extract logic", "create service", "business logic", "refactor controller", "complex operation".
Python Protocol-based storage abstraction pattern enabling dependency injection and testable file operations. Use this skill when implementing storage backends, adding file operations to services, or writing tests that need to avoid filesystem side effects. The pattern uses Python's typing.Protocol for structural subtyping, allowing any class with matching methods to satisfy the interface without explicit inheritance.
确保GOAL粒度合理，不过粗或过细。当GOAL创建完成后使用，确保GOAL符合单一职责原则。
Formalize architecture planning into a single, iterative workflow and produce one canonical architecture document (no doc sprawl). Use for architectural changes, refactors, or new system design.
Buenas prácticas y patrones de desarrollo Python para el proyecto MCP. Incluye estándares de código, patrones arquitectónicos, y convenciones.
Java 21 LTS 개발 전문가로서 Spring Boot 3.3, Virtual Threads, Pattern Matching 및 엔터프라이즈 패턴을 다룬다. 엔터프라이즈 애플리케이션, 마이크로서비스, Spring 프로젝트 구축 시 사용
Cascading error recovery for multi-agent workflows following 2024-2025 patterns. Use when: - Agent task fails and needs retry strategy - Tool call returns error - Build or test failures need diagnosis - Rate limiting encountered - Context window overflow - Subagent produces invalid output - Need graceful degradation strategy Do NOT use for: - User-facing error messages (use standard error handling) - Expected validation failures - Intentional test failures (TDD red phase)
Explain the codebase architecture, project structure, how components work together, API endpoints, data flow. Use when explaining code, understanding structure, or learning about the project.
Apply Clean Architecture layering and dependency rules (Domain, Application, Infrastructure, Presentation layers). Use when structuring applications or ensuring dependencies point inward.
Single-responsibility components with clear boundaries. Orchestration separate from execution. Build maintainable systems through component isolation.
This skill should be used when making architectural decisions, refactoring code, or evaluating design trade-offs. It provides guidance on core software design principles including KISS, DRY, Boy Scout Rule, avoiding over-engineering, and shipping stable code.
System architecture reviewer focused on simplicity, scalability, and productization readiness. Use when planning new features, reviewing architecture decisions, evaluating abstraction opportunities, or preparing for scale.
Sagebaseのエラーハンドリング規約とベストプラクティス。例外階層の使い分け、エラーの伝播ルール、再試行可能なエラーの区別をカバー。エラーハンドリングを実装・修正する時にアクティベートします。
You are a migration expert tracking The Composable Architecture removal from Leavn.
C# best practices with .NET 8, ASP.NET Core, Entity Framework, and modern async programming for 2025
Decision framework for choosing between 3D-printed home organization systems (Gridfinity, OpenGrid, Neogrid, French Cleat, Underware, Deskware). Provides interpretive guidance on system selection based on item size, mounting surface, and use case. Use when users ask which organization system to recommend or need help choosing between modular storage options.
This skill should be used when the user asks to "implement a feature in Elixir", "refactor this module", "should I use a GenServer here?", "how should I structure this?", "use the pipe operator", "add error handling", "make this concurrent", or mentions protocols, behaviours, pattern matching, with statements, comprehensions, structs, or coming from an OOP background. Contains paradigm-shifting insights.
Apply 37signals/DHH Rails conventions when writing Ruby on Rails code. Use when building Rails applications, reviewing Rails code, or making architectural decisions. Covers various aspects of Rails application architecture, design and dependencies.
