java-concurrency
Master Java concurrency - threads, executors, locks, CompletableFuture, virtual threads
Master Java concurrency - threads, executors, locks, CompletableFuture, virtual threads
Make and document architecture decisions using structured frameworks
Limita acciones posibles para prevenir errores. Use cuando diseñe formularios, flujos críticos, o sistemas donde los errores son costosos.
Exception classes, failure classes, Either type, and error handling strategies
SEMO 세션 간 컨텍스트 영속화 (공통 Skill). Use when (1) 아키텍처 결정 사항 저장, (2) 팀 선호도 기록, (3) 자주 참조하는 파일 캐싱, (4) 세션 간 맥락 유지.
Use when needing synchronous actor access in tests, legacy delegate callbacks, or performance-critical code. Covers MainActor.assumeIsolated, @preconcurrency protocol conformances, crash behavior, Task vs assumeIsolated.
Rustでのエラー設計を、境界ごとに thiserror / anyhow を使い分けて実装する。ドメイン/ライブラリは型付きエラー(thiserror)、アプリ境界のみ anyow。context付与、unwrap禁止、HTTP/CLI変換の指針を含む。
Advanced security patterns including zero-trust architecture, secret management, CSP, and compliance frameworks
Master Entity Framework Core patterns for ABP Framework including entity configuration, DbContext, migrations, relationships, and performance optimization. Use when: (1) configuring entities with Fluent API, (2) creating migrations, (3) designing relationships, (4) implementing repository patterns.
Designs scalable, resilient architectures using the 7 Omega principles. Use when building systems that need to scale to millions of users or designing platform-level infrastructure.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Complex analysis using Cipher MCP (10-30s) for library research via context7, design pattern memory search, and multi-tool integration for LoRAIro strategic planning
Analyzes a user story specification and breaks it down into atomic implementation phases. Creates a strategic phases plan without detailed implementation steps. Use when the user mentions "plan story phases", "break down story into phases", "story planning", "create phases plan", "decompose story", or needs to structure a story into implementable phases. Works with any software project and tech stack.
Implement common Django design patterns including managers, querysets, mixins, services, and architectural patterns. Use when refactoring code or implementing standard Django patterns.
Enforces TypeORM implementation patterns for this NestJS backend project. This skill should be used when creating or modifying TypeORM entities, repositories, database configuration, migrations, or any database-related code. It covers configuration patterns (TypeOrmModule.forRootAsync, replication, naming strategy), entity patterns (base entity, comments, indexes), and observability (X-Ray logging).
Create a utility service for cross-cutting concerns. Use when creating services for authentication, authorization, email, notifications, or other shared functionality that doesn't directly map to a domain entity.
Apply graph theory to decompose large UIs into optimal rendering subgraphs.
Toda aplicación tiene complejidad irreducible que debe ir al sistema o al usuario. Use cuando simplifique flujos, automatice tareas, o decida dónde poner la complejidad.
Elixir error handling refactoring using the Triage library. Use when working with Elixir code and users mention "triage" library or the `Triage` model. Useful for refactoring or evaluating code using `triage`. This skill provides correct API usage, refactoring patterns, and helps avoid common mistakes when transforming traditional Elixir error handling (with statements, case statements, try/rescue) into Triage's pipeline-based approach.
Design APIs that developers love. RESTful principles, GraphQL patterns, versioning strategies, and the art of creating interfaces that are intuitive, consistent, and future-proof.
Software architecture patterns and best practices
Execute context preservation protocols for session continuity.