architecture-patterns
5
tasks-feature-implementation
Use when implementing new features or enhancements requiring multi-layer changes (Domain, Application, Persistence, API, Frontend).
CongDon1207
development
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
architecture-patterns
5
slo-implementation
エラーバジェットとアラートを用いたサービスレベルインジケーター（SLI）とサービスレベル目標（SLO）を定義・実装します。信頼性ターゲットの確立、SREプラクティスの実装、サービスパフォーマンスの測定時に使用します。
amurata
development
architecture-patterns
5
websocket-real-time
WebSocket real-time updates, SSE broadcasting, event buffering
ikeniborn
development
architecture-patterns
5
ruby-patterns
Modern Ruby idioms, design patterns, metaprogramming techniques, and best practices. Use when writing Ruby code or refactoring for clarity.
geoffjay
development
architecture-patterns
4
thinking-framework
Use this when complex problem-solving, root cause analysis, strategic decision-making, or systematic thinking is needed. Applies 15 thinking methods with multi-agent orchestration and Clear-Thought MCP integration for enhanced analysis quality.
Tempuss
development
architecture-patterns
4
gap-analyzer
Identifies missing components and architectural gaps in project structure based on detected patterns
fractary
development
architecture-patterns
4
parallel-decompose
Decompose PRDs and Tech Specs into parallel-executable tasks with contracts, prompts, and dependency graphs. Use when breaking down a PRD for multi-agent execution.
jpoutrin
development
architecture-patterns
4
architecture-patterns
This skill should be used for system design, design patterns, architectural decisions, SOLID principles, clean code structure, code organization, refactoring strategy, software architecture
Zate
development
architecture-patterns
4
workflow-designer
Designs and generates workflow components following Manager-as-Agent pattern with architectural compliance
fractary
development
architecture-patterns
4
architecture
System architecture and technical design specialist. 🚨 TIER 2 SKILL - ON-DEMAND ACTIVATION 🚨 Use when user requests involve: - System architecture design and planning - Technical specifications and ADRs - Technology evaluation and selection - Scalability and performance planning - Integration architecture and API design - English: "design system", "architecture", "ADR", "tech stack", "scalability" - Swedish: "arkitektur", "systemdesign", "teknikval", "skalbarhet" Architecture Specialist (British female voice) provides: - System design and architecture patterns - Architecture Decision Records (ADRs) - Technology evaluation and trade-off analysis - Cloud and microservices architecture - Integration patterns and API design User confirmation optional but recommended for major architectural decisions.
carlheath
development
architecture-patterns
4
domain-modeling
Domain modeling skill for creating accurate representations of business domains through entities, value objects, aggregates, and domain services. Guides systematic analysis of business requirements and translation into robust domain models. Anchors: • Domain-Driven Design (Eric Evans) / 適用: Entity and Value Object identification / 目的: Clear domain boundaries • Implementing Domain-Driven Design (Vaughn Vernon) / 適用: Aggregate design and modeling patterns / 目的: Consistent aggregate boundaries • Domain Modeling Made Functional (Scott Wlaschin) / 適用: Type-driven design / 目的: Compile-time domain validation Trigger: Use when designing domain models, identifying entities and value objects, defining aggregate boundaries, modeling business invariants, creating ubiquitous language, or translating business requirements into domain structures. Keywords: domain model, entity, value object, aggregate, domain service, invariant, ubiquitous language, business logic
daishiman
development
architecture-patterns
4
caching
Comprehensive caching strategies and patterns for performance optimization. Use when implementing cache layers, cache invalidation, TTL policies, or distributed caching with Redis/Memcached. Triggers: cache, caching, Redis, Memcached, TTL, invalidation, cache-aside, write-through, cache stampede, distributed cache.
cosmix
development
architecture-patterns
4
api-versioning
APIバージョニング戦略と後方互換性管理を専門とするスキル。破壊的変更の管理、段階的廃止プロセス、バージョン間の移行ガイド作成を支援します。 **Anchors（参考資料）:** • 『RESTful Web APIs』（Leonard Richardson）/ 適用: API設計とバージョニング戦略 / 目的: RESTfulなバージョニング方式の理解と実装 **Triggers（自動発動条件）:** - API バージョニング戦略を決定する時 - 破壊的変更を導入する時 - エンドポイントを非推奨化する時 - バージョン間の移行ガイドを作成する時 - APIバージョン管理を設計する時 - 後方互換性を検証する時
daishiman
development
architecture-patterns
4
event-driven
Event-driven architecture patterns including message queues, pub/sub, event sourcing, CQRS, and sagas. Use when implementing async messaging, distributed transactions, event stores, command query separation, RabbitMQ, Kafka, SQS, or NATS integration.
cosmix
development
architecture-patterns
4
check-concurrency
Find concurrency issues including race conditions, deadlocks, unsafe shared state, and improper synchronization
pwittchen
development
architecture-patterns
4
defense-in-depth
Use when invalid data causes failures deep in execution, requiring validation at multiple system layers - validates at every layer data passes through to make bugs structurally impossible
alexsandrocruz
development
architecture-patterns
4
kiss-principle
Apply the K.I.S.S principle (Keep It Simple, Stupid) to reduce complexity, improve maintainability, and solve problems elegantly. Use when designing systems, writing code, planning solutions, creating documentation, architecting features, or making decisions where simplicity drives quality and efficiency.
markpitt
development
architecture-patterns
4
domain-event-patterns
ドメインイベントパターンを使用して、ビジネスドメイン内で発生した重要な出来事をモデル化・永続化・伝播するスキル。 イベントソーシング、CQRS、イベント駆動アーキテクチャの実装をサポートする。 Anchors: • Domain-Driven Design (Eric Evans) / 適用: ドメインイベント設計 / 目的: ビジネス上の重要な出来事の捕捉 • Implementing DDD (Vaughn Vernon) / 適用: イベントストア実装 / 目的: イベント永続化パターン • CQRS/Event Sourcing (Greg Young) / 適用: 状態再構築 / 目的: イベントストリームからの状態復元 Trigger: Use when designing domain events, implementing event sourcing, building event-driven architecture, modeling state changes as events, implementing CQRS patterns, creating event stores. domain event, event sourcing, CQRS, event-driven, event store, event handler
daishiman
development
architecture-patterns
4
electron-ipc-patterns
Electronプロセス間通信（IPC）パターンの設計と実装専門知識。 安全で効率的なMain-Rendererプロセス通信、contextBridge、型安全なAPI設計を提供。 Anchors: • Electron Security / 適用: contextBridge/preload設計 / 目的: セキュアなIPC実装 • Clean Architecture / 適用: Main/Renderer境界設計 / 目的: 責務分離と保守性 • Type Safety / 適用: TypeScript型契約 / 目的: IPC通信の型安全性確保 Trigger: Use when implementing IPC communication patterns, setting up contextBridge, designing typed IPC handlers, securing renderer-main communication, or structuring bidirectional messaging flows. ipcMain, ipcRenderer, contextBridge, invoke, handle, preload, typed IPC
daishiman
development
architecture-patterns
4
progressive-disclosure
3層開示モデル（メタデータ→本文→リソース）による段階的な情報提供で、トークン効率と知識スケーラビリティを両立。スキル発動信頼性を最大化し、必要な時に必要な知識だけをロードします。 Anchors: • The Pragmatic Programmer (Andrew Hunt, David Thomas) / 適用: 段階的な情報開示と実践的改善 / 目的: トークン効率を維持しながら深い知識を提供 • Progressive Disclosure (Jakob Nielsen) / 適用: 認知負荷の最小化 / 目的: UX設計原則のスキルメタデータへの応用 • Information Architecture (Louis Rosenfeld) / 適用: 階層的知識組織化 / 目的: 遅延読み込みとインデックス駆動設計 Trigger: Use when designing skill metadata, optimizing token usage, implementing progressive disclosure patterns, improving skill activation reliability, organizing knowledge hierarchically, reducing context window consumption, or creating scalable documentation structures.
daishiman
development
architecture-patterns
4
multi-agent-systems
マルチエージェントシステム設計を専門とするスキル。 複数のエージェント間の効果的な協調、ハンドオフプロトコルの設計、情報受け渡しメカニズムにより、 スケーラブルで保守性の高い分散システムを構築する。 Anchors: • Building Microservices (Sam Newman) / 適用: サービス間の協調設計 / 目的: 疎結合で信頼性の高いエージェント連携 • Patterns of Enterprise Application Architecture (Martin Fowler) / 適用: ハンドオフパターン / 目的: 明確なプロトコル設計 • Working Effectively with Legacy Code (Michael Feathers) / 適用: 既存システムとの統合 / 目的: 段階的なエージェント導入 Trigger: Use when designing multi-agent collaboration, defining handoff protocols, optimizing inter-agent communication, or managing agent dependencies. multi-agent, agent collaboration, handoff protocol, delegation, chaining, parallel agents, feedback loop, orchestration
daishiman
development
architecture-patterns
4
tech-details
Database schema (users, messages, photos tables), environment variables, ImageKit storage structure, authentication flow, and service integrations. Use when working on database operations, API logic, authentication, or infrastructure.
adeonir
development
architecture-patterns
4
optimistic-updates
楽観的更新（Optimistic Updates）パターンの実装スキル。サーバーレスポンス前にUIを即座更新し、失敗時のロールバック機構を提供することで、レスポンシブなユーザー体験を実現します。 Anchors: • Designing Data-Intensive Applications (Martin Kleppmann) / 適用: 分散システムにおける楽観的並行制御 / 目的: 競合検出とロールバック戦略の設計 • React Query (TanStack) / 適用: onMutate/onError/onSettledフック / 目的: 楽観的更新とロールバックの自動化 • SWR Documentation (Vercel) / 適用: optimisticDataとrollbackOnError / 目的: 宣言的な楽観的更新の実装 Trigger: Use when implementing instant UI feedback before server response, hiding CRUD latency, implementing optimistic updates with React Query/SWR, designing rollback strategies, or handling conflict states. optimistic update, UI feedback, rollback, React Query, SWR, mutation, conflict resolution
daishiman
development