redis-expert
Redis 전문가. Lettuce(캐싱) + Redisson(분산락) 듀얼 전략. CacheAdapter(Cache-Aside, TTL 필수, KEYS 금지→SCAN 사용), LockAdapter(Pub/Sub, Watchdog, try-finally). Key Naming: {namespace}:{entity}:{id}. @Component...
发现 devops architecture patterns 相关 Skills,比较来源仓库和用途,查看适合你工作流的技能说明。
Redis 전문가. Lettuce(캐싱) + Redisson(분산락) 듀얼 전략. CacheAdapter(Cache-Aside, TTL 필수, KEYS 금지→SCAN 사용), LockAdapter(Pub/Sub, Watchdog, try-finally). Key Naming: {namespace}:{entity}:{id}. @Component...
Factory & Assembler 변환 전문가. CommandFactory Command→Domain 변환, QueryFactory Query→Criteria 변환, Assembler Domain→Response 변환. PersistBundle 영속화 묶음, QueryBundle 조회 결과 묶음. 단방향 변환 원칙: Fa...
JPA Entity Long FK 전략, BaseAuditEntity/SoftDeletableEntity 상속, EntityMapper Domain⇄Entity 변환. JPA 관계 어노테이션(@ManyToOne, @OneToMany) 금지. Lombok 금지, Setter 금지. Entity는 of() static factory metho...
Multi-module 구조 설계, Gradle 설정, Version Catalog, 의존성 관리. 헥사고날 아키텍처 모듈 분리. Domain 외부 의존성 금지, 순환 의존성 금지. QA 도구 (Checkstyle, SpotBugs, PMD, JaCoCo) 설정.
Repository 전문가. JpaRepository(Command: save/delete), QueryDslRepository(Query: 4개 메서드), AdminQueryDslRepository(Join 허용, DTO Projection), LockRepository(Pessimistic Lock). Entity 직접 반환 금지, N+1은...
REST Controller 전문가. Thin Controller 패턴, CQRS Command/Query Controller 분리, ResponseEntity 래핑, @Valid 검증 필수. DELETE 금지(PATCH 사용). TestRestTemplate 필수 (MockMvc 금지). UseCase 의존. Mapper DI.
Port-In 인터페이스 설계, UseCase/Service 구현, CQRS Command/Query 분리. CommandService와 QueryService 템플릿 제공. @Transactional은 Facade/Manager 책임.
Create comprehensive technical documentation for code systems including data flow diagrams, architecture overviews, algorithm documentation, cheat sheets, and multi-file documentation sets. Use when documenting...
Guidelines for working with Option (nullable values) and Result (error handling) types in odu_core.
Guidelines for creating and maintaining service providers, which handle dependency injection in Flutter/Riverpod.
Create and modify domain entities following DDD principles with proper encapsulation, validation, and identity management. - Creating new domain entities - Modifying existing entities - Adding business methods...
Convex development guidelines and best practices. Use when writing Convex functions, queries, mutations, schemas, or reviewing Convex code. Triggers on tasks involving Convex backend development, real-time data...
タスクの技術アーキテクチャを詳細設計し、実装可能なレベルまで具体化する。
Architect persona for system and infrastructure design. ACTIVATE when messages contain architecture, design, system, infrastructure, diagram, flow, structure, architect, blueprint, plan, framework, pattern, or...
Specialized agent for determining the optimal placement of components and logic in a Next.js project based on the "Scope Scope Rule". It prevents tech debt by strictly enforcing modularity: local by default, sh...
Use this skill when users mention "component usage", "where is this component used", "deprecate component", "migration impact", "component analytics", or want to track and analyze component usage across the cod...
Apply object-oriented design principles (SOLID/GRASP) when writing or reviewing code in this TypeScript + Next.js codebase. Use when designing/refactoring services, libraries, domain models, and module boundari...
Validate atomic specs meet atomicity criteria
Decompose high-level specs into atomic specs
Expert in Lighthouse Journey Timeline frontend architecture, React patterns, TypeScript, TanStack Query, Zustand, and component development with strong type safety. Use when building UI components, implementing...
Expert in Lighthouse Journey Timeline backend architecture, service patterns, testing, and API development using Express.js, TypeScript, and Drizzle ORM. Use when implementing backend services, APIs, controller...
Discovers and finds connection details for Model Context Protocol (MCP) servers through research and documentation
This skill provides guidance for creating feature specifications in the Spec-Driven Development process.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库,同一仓库的多个技能可能共享相同数值;它反映仓库关注度,不代表单个技能的安装量或质量评分。