verification-rules
4-layer verification system for task completion. Use when verifying that a task has been fully completed before marking it done.
choosing-pattern
Use when deciding which pgdbm pattern to use (standalone, dual-mode library, or shared pool) - provides decision tree based on deployment context without requiring doc exploration
error-handling
Strategy for handling errors gracefully and logging them.
go-error-handling
Go error handling patterns including wrapping, custom error types, errors.Is/As, and error conventions. Use when handling, creating, or checking errors in Go.
feature-module-architect
Scaffolds feature modules following feature-based architecture with colocation principle and 500 LOC file limit. Use when creating new features or refactoring large files into modular structure.
websocket-engineer
Real-time communication specialist implementing scalable WebSocket architectures. Masters bidirectional protocols, event-driven systems, and low-latency messaging for interactive applications.
status-tracker
**AUTO-TRIGGER when user says:** "update progress", "track status", "what's our progress", "generate progress report", "update next steps", "update Notion memory", "create session page" Manages TogetherOS progress tracking, Notion memory updates, and status reporting. Updates module progress, manages next steps, syncs to Notion, and maintains session memory. Use proactively without asking permission when task matches skill purpose.
moai-lang-c
C programming language patterns, memory management, and systems programming
kafka-event-driven
Event-driven architecture patterns with Apache Kafka. Covers event schemas, producer/consumer patterns, partitioning strategies, dead letter queues, and retry mechanisms. Works with Dapr Pub/Sub abstraction.
mega
Maximally Endowed Graph Architecture — λ-calculus over bounded n-SuperHyperGraphs with grounded uncertainty, conditional self-duality, and autopoietic refinement. Use when (1) simple graphs insufficient (η<2), (2) multi-scale reasoning required, (3) uncertainty is structured not stochastic, (4) knowledge must self-refactor. Pareto-governed: complexity added only when simpler structures fail validation.
senior-architect
Software architecture guidance for designing scalable systems. Covers architecture patterns, tech stack decisions, system design trade-offs, and integration patterns.
python-result-pattern
Implement the Result[T] = Union[Success[T], Failure] pattern for explicit, type-safe error handling in Python. Use this skill when writing service methods that can fail, adding new error codes, refactoring try/except blocks, or implementing Railway-Oriented Programming patterns. This pattern replaces exceptions for control flow, making errors explicit in function signatures.
moai-core-todowrite-pattern
TodoWrite pattern for incremental implementation and placeholder management
supabase-rls
Supabase RLS パフォーマンス最適化。セキュリティ境界と最適化フィルタの区別、および堅牢な関数定義を規定。
design-review
Review production system designs for architecture, scaling, security, and operational concerns. Use when reviewing system architecture, technical designs, or complex technical approaches.
erlang-message-sync
Erlang-style message passing via /tmp file system. Use when simulating actor model with actual message synchronization between processes. Provides send/receive primitives with blocking and pattern matching.
rust-engineer
Senior Rust engineer for systems programming. Use for ownership, async Rust, and zero-cost abstractions.
spring-boot-engineer
Expert in Spring Boot 3+, Microservices, and Cloud-Native Java. Specializes in Virtual Threads, Spring Cloud, and Reactive Stack.
auto-generated-circuit-breaker-pattern
Opossum circuit breaker patterns for resilience. Singleton pattern per service, timeout from env, event listeners. Triggers on "circuit breaker", "resilience", "external api", "failure handling", "opossum".
python-async-patterns
Best practices for async Python code, avoiding common pitfalls like await precedence bugs and sync-in-async anti-patterns.
java-ddd-hexagonal
Guide Claude to create domain modules following DDD principles and hexagonal architecture for Java + Spring Boot projects. Use when user requests: (1) "Create a new module" / "새 모듈 만들어줘" / "도메인 모듈 생성" (2) "Add {feature} module" (e.g., "Add order module", "Add product module") (3) "Build {domain} bounded context" / "{domain} 바운디드 컨텍스트 구현" (4) Any request to create a new domain module for Java + Spring Boot projects with DDD and hexagonal architecture. Applies Kent Beck's TDD workflow (Red → Green → Refactor). Adapts to any Java/Spring Boot project by reading CLAUDE.md at project root. Uses Java 17+ features including records, sealed classes, and pattern matching.
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
