scalability-expert
Expert scalability design including horizontal scaling, load balancing, database scaling, and capacity planning
Expert scalability design including horizontal scaling, load balancing, database scaling, and capacity planning
Analyze and refactor backend code to follow entity/service separation patterns. Use when asked to "refactor X to entity pattern", "analyze architecture for X", "extract business rules for X", "separate concerns for X", "create entity for X", or "clean up X service". Triggers on domain concepts like deals, leads, applications, locations, franchisees, etc.
This skill should be used when the user asks about Service Abstractions library, infrastructure service management, or database/cache/file system configurations in Kotlin
Event-driven architecture patterns for RabbitMQ-based service coordination
Mรฉthodologie TDD/BDD pour refactoring sรปr et systรฉmatique. MANDATORY pour code improvement. ร utiliser lors de refactoring, amรฉlioration de code, ou quand l'utilisateur mentionne "refactor", "amรฉliorer", "nettoyer le code", "simplifier".
ๅๅฉ่จญ่จๅ้็ผ Claude Code Skills๏ผๆไพ skill ่จญ่จ็ๆ่้่ผฏๅๆไฝณๅฏฆ่ธ
Constructor-based MapStruct mapping for compile-time safety in Jakarta EE. Use when implementing DTO mapping or using @Default annotations.
Stateless conversation management with database-backed history, message persistence, and scalable architecture. Use when handling chat state, loading history, or building stateless APIs.
Language-agnostic backend patterns: API design, authentication, security, databases. Use when: designing APIs, implementing auth, securing endpoints, modeling data. Triggers: "api design", "rest api", "graphql", "authentication", "jwt", "oauth", "security", "owasp", "database schema", "migrations", "sql".
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.