architecture
ใฟในใฏใฎๆ่กใขใผใญใใฏใใฃใ่ฉณ็ดฐ่จญ่จใใๅฎ่ฃ ๅฏ่ฝใชใฌใใซใพใงๅ ทไฝๅใใใ
ใฟในใฏใฎๆ่กใขใผใญใใฏใใฃใ่ฉณ็ดฐ่จญ่จใใๅฎ่ฃ ๅฏ่ฝใชใฌใใซใพใงๅ ทไฝๅใใใ
Implement robust error handling with user-friendly messages, specific exception types (ISP), centralized error boundaries (SRP), fail-fast validation (KISS), graceful degradation, retry strategies, and proper resource cleanup. Use this skill when adding try-catch blocks, throwing or catching exceptions, creating error classes, implementing error boundaries or middleware, displaying error messages to users, or handling async errors and promise rejections. Use when working with error handling in any language (.ts, .js, .py, .java, .go) across backend services, API endpoints, frontend components, or data processing pipelines. Use when implementing exponential backoff for external service calls or ensuring resources are cleaned up in finally blocks.
Level 4 patterns - multi-language orchestration, root + subproject structure
Kalahari architecture patterns and key classes. Use for code analysis and design.
WHEN: Kotlin Multiplatform (KMP) project review, expect/actual patterns, shared module structure, iOS interop WHAT: Module structure analysis + expect/actual validation + platform separation + iOS/Android interop + dependency management WHEN NOT: Android UI โ kotlin-android-reviewer, Server โ kotlin-spring-reviewer
Refactors code to improve readability, maintainability, performance, and adherence to best practices while preserving functionality
Design React components following Tetris architecture guidelines. Use when creating new components, refactoring components, optimizing performance, or improving component structure. Auto-triggers on phrases like "create a component", "refactor this component", "optimize rendering", or "improve component design". Emphasizes component consolidation, unified patterns, and efficient hook usage.
Domain-Driven Design ๊ธฐํ ๋ฐ ์ค๊ณ ์ ๋ฌธ skill. ํ๋ก์ ํธ ๋๋ฉ์ธ ๋ถ์, Bounded Context ์ ์, Aggregate ์ค๊ณ, Context Mapping, Event Storming, Ubiquitous Language ์ ์ ๋ฑ DDD ์ ์ฒด ํ๋ก์ธ์ค๋ฅผ ์ง์ํฉ๋๋ค. ์ฌ์ฉ ์๊ธฐ: (1) DDD ๊ธฐํ/์ค๊ณ๋ฅผ ์์ฒญํ ๋ (2) ๋๋ฉ์ธ ๋ชจ๋ธ๋ง์ ์์ฒญํ ๋ (3) Bounded Context, Aggregate, Domain Event ์ค๊ณ ์ (4) ํ๋ฉด์ ์์/DB์ ์์์์ ๋๋ฉ์ธ ์ถ์ถ ์ (5) Context Map ์์ฑ ์ (6) Kotlin DDD ์ฝ๋ ์์ฑ ์
Comprehensive Ruby development skill covering language fundamentals, object-oriented design patterns, error handling strategies, performance optimization, modern Ruby 3.x features (pattern matching, ractors, typed Ruby), testing patterns, metaprogramming, concurrency, and Rails-specific best practices. Use when writing Ruby code, refactoring, implementing design patterns, handling exceptions, optimizing performance, writing tests, or applying Ruby idioms and conventions.
REST API design and implementation patterns for FastAPI endpoints including CRUD operations, pagination, filtering, error handling, and request/response models. Use when building FastAPI endpoints, creating REST APIs, implementing CRUD operations, adding pagination, designing API routes, handling API errors, or when user mentions FastAPI patterns, REST API design, endpoint structure, API best practices, or HTTP endpoints.
Implements event-driven architecture with Watermill pub/sub (RabbitMQ/AMQP/message queue) for go-kratos microservices. Creates publisher/subscriber wrappers, event handlers, worker services with context propagation (request_id, correlation_id), and RabbitMQ/AMQP integration. Use when implementing pub/sub patterns, creating message queues, adding event handlers, building worker services for async processing, or setting up background jobs.
Laravel framework patterns for PHP applications including Eloquent ORM, migrations, routing, queues, and Blade templates. Use when building Laravel applications or working with Laravel projects.
Use this when reasoning about API surfaces, packages, protobuf schema, versioning, compatibility adapters or domain action handlers.
Chat ์๋น์ค์ ์์ํ ๋ ์ด์ด ๊ฐ์ด๋. Checkpointer(๋ฉํฐํด ์ปจํ ์คํธ), Message Persistence(PostgreSQL), Redis Streams Consumer ์ํคํ ์ฒ ๋ฐ ํธ๋ฌ๋ธ์ํ . Use when: (1) chat.messages ํ ์ด๋ธ์ด ๋น์ด์์ ๋, (2) checkpointer ๊ด๋ จ ์๋ฌ ๋ฐ์ ์, (3) ๋ฉํฐํด ๋ํ ์ปจํ ์คํธ๊ฐ ์ ์ง๋์ง ์์ ๋, (4) Redis Streams consumer group ์ค์ ์.
Rust async/await with Tokio and async patterns
PRDใจๆฉ่ฝ่จญ่จๆธใซๅบใฅใใฆใขใผใญใใฏใใฃ่จญ่จๆธใไฝๆใใในใญใซใdocs/prd.md ใจ docs/functional-design.md ใๅญๅจใใๅ ดๅใซใใใฏใใญใธใผในใฟใใฏใใฌใคใคใผใใขใผใญใใฏใใฃใใใผใฟๆฐธ็ถๅๆฆ็ฅใใใใฉใผใใณใน่ฆไปถใใปใญใฅใชใใฃ่จญ่จ็ญใๅซใใขใผใญใใฏใใฃ่จญ่จๆธใไฝๆใใพใใใใขใผใญใใฏใใฃ่จญ่จๆธใไฝๆใใฆใใๆ่กไปๆงๆธใๆธใใฆใใarchitecture design ใไฝใฃใฆใ็ญใฎใชใฏใจในใใงไฝฟ็จใใฆใใ ใใใ
Multi-module ๊ตฌ์กฐ ์ค๊ณ, Gradle ์ค์ , Version Catalog, ์์กด์ฑ ๊ด๋ฆฌ. ํฅ์ฌ๊ณ ๋ ์ํคํ ์ฒ ๋ชจ๋ ๋ถ๋ฆฌ. Domain ์ธ๋ถ ์์กด์ฑ ๊ธ์ง, ์ํ ์์กด์ฑ ๊ธ์ง. QA ๋๊ตฌ (Checkstyle, SpotBugs, PMD, JaCoCo) ์ค์ .
Framework for designing safeguards in autonomous systems including kill switches, resource limits, anomaly detection, and human-in-the-loop patterns.
Minimal reference skill used to validate parsing and loading.
Reference and maintain the project's technology stack including frameworks, languages, databases, testing tools, and third-party services to ensure consistency across the codebase. Use this skill when making technology decisions, adding new dependencies, choosing appropriate tools or libraries, configuring build systems, setting up testing frameworks, or documenting the tech stack. Apply this skill when selecting which framework, library, or tool to use for a given task, when ensuring code follows the conventions of the chosen stack (React patterns, Python idioms, Rails conventions), when integrating third-party services, or when documenting technology choices in README or architecture documentation. This skill ensures all team members use consistent technologies, new additions align with existing stack decisions, technology choices are documented with rationale, and the project maintains coherent patterns rather than mixing conflicting approaches or frameworks.
Core software design principles from 'A Philosophy of Software Design'. Use when asking about decomposition, deep modules, information hiding, complexity management, or John Ousterhout's design principles.