distributed-systems
Distributed systems patterns for BEAM/OTP including clustering, supervision, and multi-region deployment
Distributed systems patterns for BEAM/OTP including clustering, supervision, and multi-region deployment
Comprehensive guide to identifying, analyzing, and documenting failure modes in distributed systems
Clean Architecture principles and implementation patterns for .NET applications. Use when designing application structure, clarifying layer responsibilities, or implementing Clean Architecture in .NET projects.
Designs WPF solution and project structures based on Clean Architecture. Use when creating new WPF solutions, organizing layers, or establishing project naming conventions.
Patterns for building B2B SaaS multi-tenancy: tenant identification, data isolation (RLS/schema/db), quotas, billing/metering, onboarding, and tenant-safe operations
Simplify and refine code for clarity, consistency, and maintainability while preserving functionality. Use after writing code to improve quality.
Write minimum necessary code following YAGNI principle to prevent bloat and over-engineering. Use when implementing features to keep the codebase lean and avoid premature optimization or speculative features.
Architecture rules and validation patterns for Claude Code marketplace components ensuring self-contained skills, proper skill usage, and clean reference patterns
Frontend anti-patterns detection and resolution
OpenFGA authorization modeling best practices and guidelines. This skill should be used when authoring, reviewing, or refactoring OpenFGA authorization models. Triggers on tasks involving OpenFGA models, relationship definitions, permission structures, .fga files, .fga.yaml test files, or OpenFGA SDK usage in JavaScript, TypeScript, Go, Python, Java, or .NET.
Core engineering principles for quality, maintainable code.
Session guardrails for PM OS - dynamic execution with dependency awareness.
Comprehensive Java development best practices covering SOLID principles, DRY, Clean Code, Java-specific patterns (Optional, immutability, streams, lambdas), exception handling, collections, concurrency, testing with JUnit 5 and Mockito, code organization, performance optimization, and common anti-patterns. Essential reference for uncle-duke-java agent during code reviews and architecture guidance.
Obsidian LiveSync プロジェクトの Rust 開発を支援します。DDD 4層アーキテクチャ(domain/application/infrastructure/interfaces)に従った新規モジュール追加、axum ハンドラー・ルーティング実装、DomainError と thiserror を使用したエラーハンドリング、tokio-test・mockall・rstest によるテスト作成を行います。新機能追加、コード修正、アーキテクチャ設計、テスト実装を依頼されたときに使用してください。
WHEN: Go project review, error handling, goroutines, interfaces, testing WHAT: Error handling patterns + Concurrency safety + Interface design + Testing + Idiomatic Go WHEN NOT: Go API frameworks → go-api-reviewer, Rust → rust-reviewer
Guide for exception handling patterns in the domain layer. Use when creating exceptions, handling errors in controllers, or testing exception scenarios.
激活高级开发工程师模式。用于设计完成后,根据设计契约进行纯代码实现。
{{LANGUAGE_NAME}} best practices with modern frameworks, {{PRIMARY_DOMAIN}}, and performance optimization for 2025
Expert Principal Software Architect (20+ years). Collaborates on high-stakes technical decisions, system design (Microservices/Monolith), cloud infrastructure, and engineering process standards. Generates ADRs, RFCs, and Tech Specs.
Initializes a bounded context skeleton under runtime/contexts/<context>.
This skill should be used when the user asks about "design patterns", "SOLID", "factory pattern", "singleton", "observer", "strategy", "decorator", "adapter", "facade", "command pattern", "builder pattern", "dependency injection", "composition", "Ruby patterns", or needs guidance on implementing design patterns in Ruby.
Layered Composition Architecture patterns. Use when designing system boundaries, state flow, lifecycle management, configuration, or module structure. Includes Infrastructure pattern for shared dependencies and Handler() factory for domain system handler creation. Triggers: System interface, New* constructor, Start() method, Cold Start, Hot Start, Runtime struct, Domain struct, Infrastructure, Handler() factory, lifecycle coordinator, OnStartup, OnShutdown, config.go, Finalize(), validate(), loadDefaults(), loadEnv(). File patterns: internal/config/*.go, pkg/lifecycle/*.go, pkg/runtime/*.go, internal/*/system.go, cmd/server/*.go
Simplify code and workflows without behavior changes; reduce complexity and duplication; improve readability. Use when asked to refactor, reduce complexity, or simplify logic.
SPEC document authoring guide - YAML metadata, EARS syntax (5 patterns with Unwanted Behaviors), validation checklist