global-error-handling
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.
justfile-polyglot-patterns
Level 4 patterns - multi-language orchestration, root + subproject structure
architecture-patterns
Kalahari architecture patterns and key classes. Use for code analysis and design.
kotlin-multiplatform-reviewer
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
refactor-code
Refactors code to improve readability, maintainability, performance, and adherence to best practices while preserving functionality
react-component-design
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.
ddd-planning
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 코드 생성 시
ruby
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.
fastapi-api-patterns
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.
kratos-events
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.
developing-with-laravel
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.
api-design
Use this when reasoning about API surfaces, packages, protobuf schema, versioning, compatibility adapters or domain action handlers.
chat-agent-persistence
Chat 서비스의 영속화 레이어 가이드. Checkpointer(멀티턴 컨텍스트), Message Persistence(PostgreSQL), Redis Streams Consumer 아키텍처 및 트러블슈팅. Use when: (1) chat.messages 테이블이 비어있을 때, (2) checkpointer 관련 에러 발생 시, (3) 멀티턴 대화 컨텍스트가 유지되지 않을 때, (4) Redis Streams consumer group 설정 시.
maverick-rust-async
Rust async/await with Tokio and async patterns
architecture-design-creator
PRDと機能設計書に基づいてアーキテクチャ設計書を作成するスキル。docs/prd.md と docs/functional-design.md が存在する場合に、テクノロジースタック、レイヤードアーキテクチャ、データ永続化戦略、パフォーマンス要件、セキュリティ設計等を含むアーキテクチャ設計書を作成します。「アーキテクチャ設計書を作成して」「技術仕様書を書いて」「architecture design を作って」等のリクエストで使用してください。
project-setup-expert
Multi-module 구조 설계, Gradle 설정, Version Catalog, 의존성 관리. 헥사고날 아키텍처 모듈 분리. Domain 외부 의존성 금지, 순환 의존성 금지. QA 도구 (Checkstyle, SpotBugs, PMD, JaCoCo) 설정.
safety-architecture
Framework for designing safeguards in autonomous systems including kill switches, resource limits, anomaly detection, and human-in-the-loop patterns.
fpf-skillhello-world
Minimal reference skill used to validate parsing and loading.
global-tech-stack
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.
principles
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.
