home/categories/architecture-patterns
category focus

Architecture

Design patterns and architectural blueprints.

4113 स्किल्सall categories
sorting
stars
current ordering strategy
query
all entries
refine the visible subset
architecture-patterns
90

rust-async-patterns

Master Rust async programming with Tokio, async traits, error handling, and concurrent patterns. Use when building async Rust applications, implementing concurrent systems, or debugging async code.

aiskillstore
aiskillstore
development
open
architecture-patterns
90

develop-backend

Spring Boot/MyBatisによるバックエンド実装スキル - RESTful API設計、データベース設計(Flywayマイグレーション)、Controller/Service/Mapper層の実装、単体テスト作成を行います。DRY原則を徹底し、product.utilパッケージの既存実装やAOPによる自動ログ出力を活用します。未使用コード削除をIDE警告で確認し、./gradlew checkでLint/テスト/カバレッジ80%以上を保証します。サーバー起動による動作確認も必須です。

aiskillstore
aiskillstore
development
open
architecture-patterns
90

execution-engine-analysis

Analyze control flow, concurrency models, and event architectures in agent frameworks. Use when (1) understanding async vs sync execution patterns, (2) classifying execution topology (DAG/FSM/Linear), (3) mapping event emission and observability hooks, (4) evaluating scalability characteristics, or (5) comparing execution models across frameworks.

aiskillstore
aiskillstore
development
open
architecture-patterns
90

swift-concurrency

Expert guidance on Swift Concurrency best practices, patterns, and implementation. Use when developers mention: (1) Swift Concurrency, async/await, actors, or tasks, (2) "use Swift Concurrency" or "modern concurrency patterns", (3) migrating to Swift 6, (4) data races or thread safety issues, (5) refactoring closures to async/await, (6) @MainActor, Sendable, or actor isolation, (7) concurrent code architecture or performance optimization.

aiskillstore
aiskillstore
development
open
architecture-patterns
90

event-store-design

Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.

aiskillstore
aiskillstore
development
open
architecture-patterns
90

architecture-patterns

Organizational coding standards and architectural patterns. References comprehensive skills for detailed patterns. Use when making architecture decisions or implementing features.

aiskillstore
aiskillstore
development
open
architecture-patterns
90

architecture-patterns

AI-friendly architecture patterns for TypeScript projects including Domain-Driven Design, Clean Architecture, Hexagonal Architecture, and Page Object Model testing patterns

aiskillstore
aiskillstore
development
open
architecture-patterns
90

the-archivist

This skill should be used when engineering decisions are being made during code implementation. The Archivist enforces decision documentation as a standard practice, ensuring every engineering choice includes rationale and integrates with Architecture Decision Records (ADRs). Use when writing code that involves choosing between alternatives, selecting technologies, designing architectures, or making trade-offs.

aiskillstore
aiskillstore
development
open
architecture-patterns
90

decisions

Load past architectural decisions. Use when making new decisions to ensure consistency.

aiskillstore
aiskillstore
development
open
architecture-patterns
90

allra-error-handling

Allra 백엔드 에러 핸들링 및 예외 처리 표준. Use when handling errors, creating custom exceptions, or implementing error responses.

aiskillstore
aiskillstore
development
open
architecture-patterns
90

data-substrate-analysis

Analyze fundamental data primitives, type systems, and state management patterns in a codebase. Use when (1) evaluating typing strategies (Pydantic vs TypedDict vs loose dicts), (2) assessing immutability and mutation patterns, (3) understanding serialization approaches, (4) documenting state shape and lifecycle, or (5) comparing data modeling approaches across frameworks.

aiskillstore
aiskillstore
development
open
architecture-patterns
90

test-kitchen

This skill should be used when implementing features with parallel exploration or competition. Triggers on "build", "create", "implement", "try both approaches", "compare implementations". Routes to omakase-off (entry gate for design exploration) or cookoff (exit gate for parallel implementation).

aiskillstore
aiskillstore
development
open
architecture-patterns
90

golang-enterprise-patterns

Enterprise-level Go architecture patterns including clean architecture, hexagonal architecture, DDD, and production-ready application structure.

aiskillstore
aiskillstore
development
open
architecture-patterns
90

cqrs-implementation

Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.

aiskillstore
aiskillstore
development
open
architecture-patterns
90

software-architecture

Clean Architecture and SOLID principles guide. Use this when designing systems, reviewing architecture, or making structural decisions.

aiskillstore
aiskillstore
development
open
architecture-patterns
90

error-recovery

Strategies for handling subagent failures with retry logic and escalation patterns.

aiskillstore
aiskillstore
development
open
architecture-patterns
90

openspec-daem0n-bridge

Bridges OpenSpec (spec-driven development) with Daem0n-MCP memory - auto-imports specs, informs proposals with past outcomes, converts archived changes to learnings

aiskillstore
aiskillstore
development
open
architecture-patterns
90

checkpoint

Robust workflow checkpoint and resume. Handles session interruption, state recovery, and safe resume across all workflow phases.

aiskillstore
aiskillstore
development
open
architecture-patterns
90

system-design

CTO's deputy for software architecture using Clean/Hexagonal Architecture principles. Socratic approach - asks probing questions to help YOU make informed design decisions. Guides through Discovery → Modeling → Boundaries → Scaffolding phases. Outputs TypeScript scaffolds with ports, adapters, and domain layers. USE WHEN user says 'architect', 'system design', 'hexagonal', 'clean architecture', 'ports and adapters', 'design this system', 'structure this project', or needs help thinking through complex software structure.

aiskillstore
aiskillstore
development
open
architecture-patterns
90

refactor-code

コードリファクタリングスキル(DRY原則適用、複雑度削減、パフォーマンス最適化、デグレーション防止)

aiskillstore
aiskillstore
development
open
architecture-patterns
90

blueprinteventbus-integration

Implement event-driven communication using BlueprintEventBus for cross-module coordination. Use this skill when modules need to communicate without tight coupling, broadcasting domain events (task.created, member.added), subscribing to events with proper lifecycle management, and implementing event-driven workflows. Ensures events follow naming conventions ([module].[action]), include Blueprint context, and use takeUntilDestroyed() for automatic cleanup.

aiskillstore
aiskillstore
development
open
architecture-patterns
90

planning-framework

Apply structured thinking before coding. Use when: starting new features, making architectural decisions, refactoring large components, or evaluating implementation approaches. Includes Musk's 5-step algorithm and ICE scoring framework.

aiskillstore
aiskillstore
development
open
Previous
Page 55 / 172
Next