effect-layers-services
Define services, provide layers, compose dependencies, and switch live/test. Use for DI boundaries and app composition.
reviewing-readability
Code readability review based on "The Art of Readable Code" and Miller's Law (7ยฑ2). Triggers: ๅฏ่ชญๆง, ็่งฃใใใใ, ใใใใใใ, ๆ็ขบ, ๅฝๅ, ๅคๆฐๅ, ้ขๆฐๅ, ใในใ, ๆทฑใใในใ, ้ขๆฐ่จญ่จ, ใณใกใณใ, ่ค้, ้ฃใใ, ้ฃ่ชญ, Miller's Law, ใใฉใผใฎๆณๅ, ่ช็ฅ่ฒ ่ท, AI-generated, ้ๅฐ่จญ่จ.
sage-architecture
Sage ้กน็ฎๆดไฝๆถๆ่ฎพ่ฎกๆๅ๏ผๅบไบ Claude CodeใCrush ๆไฝณๅฎ่ทต็่ๅๆนๆก
code-refactoring
Improve code structure, readability, and maintainability without changing external behavior through systematic refactoring
internal-platform-builder
Design and build internal developer platforms for self-service infrastructure
applying-fsd-architecture
Feature-Sliced Design(FSD) ์ํคํ ์ฒ๋ฅผ ์ ์ฉํ ํ๋ก ํธ์๋ ํ๋ก์ ํธ ๊ฐ๋ฐ ์ง์. FSD ๋ ์ด์ด, ์ฌ๋ผ์ด์ค, ์ธ๊ทธ๋จผํธ ๊ตฌ์กฐ ์ค๊ณ, ์์กด์ฑ ๊ท์น ์ ์ฉ, ๋ง์ด๊ทธ๋ ์ด์ ์ ์ฌ์ฉ.
storage-sync
Synchronize memories between Turso (durable) and redb (cache) storage layers. Use when cache appears stale, after failures, or during periodic maintenance.
infrastructure-software-upgrades
Generic guidelines on how to perform infrastructure component upgrades in a reliable way
optimization-patterns
Apply caching strategies, database optimization, and algorithmic improvements to enhance application performance
brokle-error-handling
Use this skill when implementing, reviewing, or debugging error handling in the Brokle codebase. This includes repository error mapping, service layer AppError constructors, handler response mapping, domain alias imports, or understanding the industrial error handling flow.
separation-of-concerns
Separation of Concerns principle for TypeScript code review and refactoring. Use when detecting mixed responsibilities, business logic in UI components, infrastructure code in domain layer, or tightly coupled modules. Helps improve modularity and maintainability. Related to Clean Architecture layers.
finding-code-patterns
Finds similar implementations, usage examples, and existing patterns in the codebase - shows concrete code examples for modeling new work. Pattern librarian documenting what exists without judgment.
unity-csharp-fundamentals
Unity C# fundamental patterns including TryGetComponent, SerializeField, RequireComponent, and safe coding practices. Essential patterns for robust Unity development. Use PROACTIVELY for any Unity C# code to ensure best practices.
csharp-async-patterns
Modern C# asynchronous programming patterns using async/await, proper CancellationToken usage, and error handling in async code. Use when guidance needed on async/await best practices, Task composition and coordination, ConfigureAwait usage, ValueTask optimization, or async operation cancellation patterns. Pure .NET framework patterns applicable to any C# application.
scalable-thinking
Design for scale while keeping implementation simple (KISS).
feature-planning
Break down features into implementable tasks and choose architecture approach. Use when starting a new feature or receiving requirements that need technical decomposition.
distributed-workers
Use when working on worker implementation, ServiceOrchestrator patterns, WorkerAPIBase, operation dispatch, progress tracking, cancellation, backend-to-worker communication, or adding new worker types.
software-engineering
The foundation of engineering mindset. Focuses on architecture, system patterns, and universal code navigation.
domain-driven-design
Apply Domain-Driven Design patterns. Use when modeling complex business domains, defining bounded contexts, or designing aggregates. Covers entities, value objects, and repositories.
refactoring-code
Improve code structure while preserving behavior with test verification. Use when cleaning up code, reducing duplication, simplifying complexity, or reorganizing modules.
functional-programming
Use when writing functional code - covers FP best practices (Lea differs from traditional FP languages)
effect-errors-retries
Error modeling and recovery with TaggedError, catchTag(s), mapError, and retry schedules. Use when defining errors or adding resilience.
policyengine-code-organization
Code organization patterns for PolicyEngine - variable naming conventions, folder structure, file organization
