concurrency
Goroutine ownership, errgroup patterns, worker pools, and graceful shutdown. Use when writing concurrent code or parallel request handling.
Goroutine ownership, errgroup patterns, worker pools, and graceful shutdown. Use when writing concurrent code or parallel request handling.
Analyze existing PHPStan error logs without running analysis. Use when: - User says "fix the phpstan errors" (after manually running PHPStan) - User says "what phpstan errors do I have?" - User points to specific log file - PHPStan was run outside Claude's context Delegates to fixer agent (sonnet) to find logs, parse errors, and implement fixes. Does NOT execute PHPStan - use phpstan-runner for that.
系统化调试方法,使用四阶段调试流程解决前端和后端问题。遇到 bug、错误或异常行为时使用。
Dataclass patterns including frozen dataclasses, slots, immutability, and value objects. Activated when designing data classes or value types.
Use when a plan is abandoned, obsolete, or superseded and should be archived
Skill untuk mengembangkan PayU Digital Banking Platform - mencakup microservices architecture (Spring Boot, Quarkus, FastAPI), event-driven patterns, PostgreSQL databases, dan integrasi dengan Red Hat OpenShift ecosystem.
Best practices for code structure, error handling, and reducing duplication.
Port-In 인터페이스 설계, UseCase/Service 구현, CQRS Command/Query 분리. CommandService와 QueryService 템플릿 제공. @Transactional은 Facade/Manager 책임.
Expert in modern code design standards including SOLID principles, Clean Code patterns (KISS, YAGNI, DRY, TDA), design patterns, and pragmatic software design. **ALWAYS use when designing ANY classes/modules, implementing features, fixing bugs, refactoring code, or writing functions. ** Use proactively to ensure proper design, separation of concerns, simplicity, and maintainability. Triggers - "create class", "design module", "implement feature", "refactor code", "fix bug", "is this too complex", "apply SOLID", "keep it simple", "avoid over-engineering", writing any code.
Use when working with .cs files, .NET projects, implementing C# features, advising on C#/.NET architecture and patterns, or answering questions about C#/.NET development. Covers async patterns, dependency injection, LINQ, and testing conventions.
Phase 3 of feature development - Create domain events, external events, value objects, and aggregate changes for the Burraco system. Use after feature-design to implement the domain model.
Core development principles and standards for consistent, high-quality code. Automatically applies DRY, KISS, YAGNI, SOLID, TDD, and micro-commit methodologies.
EARS (Easy Approach to Requirements Syntax) format for clear requirements
Implements Pub-Sub patterns using System.Reactive and Channels for event-based communication in .NET. Use when building reactive applications or decoupled event-driven architectures.
Systematic approaches to writing high-quality code with contract-first discipline and validation gates
Implementing formal agreements between data producers and consumers to ensure data reliability and stability.
Comprehensive guide to conducting blameless postmortems and learning from incidents to improve system reliability
Description of feature 2 and when to use it
Error-handling conventions (error mapping/presentation, what to throw vs return, user-facing output). Use when adding errors or changing failure behavior.
Design token systems and component architecture for web and React Native. Use when: implementing design-system, building UI components, defining tokens, creating themed interfaces. Do not use for: UX decisions (use ux-design), business logic, data fetching. Workflow: ux-design (what/why) → this skill (tokens, components) → nextjs/expo-react-native (integration).
Guide for implementing Domain Events following DDD principles. Use when adding events to aggregates or creating event listeners.
Graceful degradation through cascading fallback strategies - ensures system always completes while maintaining acceptable functionality
Génère des mappers bidirectionnels entre Domain Entities et Prisma Models pour l'isolation de la couche persistence. À utiliser lors de la création de mappers, repositories, ou quand l'utilisateur mentionne "mapper", "Prisma", "persistence", "toPrisma", "toDomain", "repository implementation".
CLAUDE Framework coding standards for code quality, naming conventions, error handling, security, testing, database, and logging