reviewing-type-safety
TypeScript type safety patterns and best practices for maximum type coverage. Triggers: TypeScript, type safety, any, 型安全, 型カバレッジ, strict mode.
TypeScript type safety patterns and best practices for maximum type coverage. Triggers: TypeScript, type safety, any, 型安全, 型カバレッジ, strict mode.
Analyze gaps between implementation plans and actual codebase implementation for the Rust self-learning memory project
Handle production incidents effectively. Use when responding to outages, conducting post-mortems, or improving reliability. Covers incident response and blameless culture.
Example Skill packaged as a standalone Maven artifact
Apply layered security architecture. Use when designing security controls, hardening systems, or reviewing security posture. Covers multiple security layers.
Clean architecture patterns for JUCE plugins including separation of concerns, APVTS patterns, state management, preset systems, MIDI handling, and modulation routing. Use when designing plugin architecture, refactoring code structure, implementing parameter systems, building preset managers, or scaling complex audio plugins.
Spec-First Development with OpenSpec for Spring Boot. Align on specifications before implementation begins.
Systematic process for analyzing and modernizing legacy applications to comply with the 12-Factor App methodology. Covers code analysis, configuration externalization, dependency management, and container/Kubernetes best practices.
Design and implement DDD patterns (entities, value objects, aggregates, CQRS). Use when creating new domain objects, implementing bounded contexts, designing repository interfaces, or learning proper layer separation. For fixing existing Deptrac violations, use the deptrac-fixer skill instead.
PolicyEngine variable patterns - variable creation, no hard-coding principle, federal/state separation, metadata standards
Go concurrency patterns - goroutines, channels, sync primitives
Design scalable, reliable software systems. Use when planning new systems, major features, or architecture changes. Covers C4 diagrams, trade-off analysis, and system decomposition.
Enterprise architecture patterns following TOGAF ADM methodology. Implements capability-driven design, federated architecture, and technology-agnostic specifications. Activates for enterprise-scale architecture decisions.
Senior Kotlin developer using http4k and functional patterns. Use when writing Kotlin code, implementing features, or working with Gradle projects. Used as a part of the XP skill.
Define services, provide layers, compose dependencies, and switch live/test. Use for DI boundaries and app composition.
Code readability review based on "The Art of Readable Code" and Miller's Law (7±2). Triggers: 可読性, 理解しやすい, わかりやすい, 明確, 命名, 変数名, 関数名, ネスト, 深いネスト, 関数設計, コメント, 複雑, 難しい, 難読, Miller's Law, ミラーの法則, 認知負荷, AI-generated, 過剰設計.
Sage 项目整体架构设计指南,基于 Claude Code、Crush 最佳实践的融合方案
Improve code structure, readability, and maintainability without changing external behavior through systematic refactoring
Design and build internal developer platforms for self-service infrastructure