swift-concurrency
Swift 6 strict concurrency model, async/await, actors, @MainActor, Sendable, and thread safety. Use when user asks about concurrency, async/await, actors, MainActor, thread safety, data races, or migrating from...
Découvrez les skills documentation architecture patterns, comparez leurs dépôts et consultez leurs instructions.
Swift 6 strict concurrency model, async/await, actors, @MainActor, Sendable, and thread safety. Use when user asks about concurrency, async/await, actors, MainActor, thread safety, data races, or migrating from...
Rust製非同期Docker APIクライアント「Bollard」の使い方と実装パターン
Analyzes CI/CD pipelines to identify common antipatterns (like slow feedback loops or sequential steps) and recommends best practice patterns (like build images, parallelization, and build-once-deploy-anywhere)...
Container and infrastructure patterns for Go applications. Use when working with Dockerfiles, external binaries, or deployment configuration. Triggers: containerization, external binary integration, dependency...
Go library development patterns. Use when designing library APIs, implementing extensibility, or working on packages in pkg/ directories. Triggers: format extensibility, provider separation, capability composit...
Implement CQRS (Command Query Responsibility Segregation) pattern for Electron services. Use when creating service methods, separating read/write operations, or implementing reactive data streams with Observabl...
Advanced patterns for Hono-based Electron IPC including CQRS, Zod validation, error handling, and reactive data with RxJS. Use when implementing complex IPC patterns or needing guidance on architecture decision...
Rapidly build and launch micro-SaaS applications with best practices, monetization, and deployment
Use when writing async/await code, enabling strict concurrency, fixing Sendable errors, migrating from completion handlers, managing shared state with actors, or using Task/TaskGroup for concurrency.
Reference and adhere to the project's technical stack including frameworks, languages, tools, and dependencies. Use this skill when choosing libraries, frameworks, or tools for implementing features. Use this s...
Implement robust error handling strategies with user-friendly messages and graceful failure patterns. Use this skill when catching and handling exceptions or errors in any code. Use this skill when validating i...
Follow general development conventions for project organization, documentation, version control, and team collaboration. Use this skill when organizing project files and directory structures. Use this skill whe...
Workflow-first design through collaborative dialogue. Use before creating features, building components, or modifying behavior.
Expert assistant for Kumo's Query Module (src/features/query). Use when working with SQL Editor, Monaco editor integration, query execution, result grids, tabs management, AI features, or any query-related comp...
Reference catalog of recurring SAE feature patterns - check when labeling new features, add new patterns as discovered
Use ALWAYS. Core development rules for production-ready code - guard clauses, no shortcuts, no mocking.
Amplifier design philosophy using Linux kernel metaphor. Covers mechanism vs policy, module architecture, event-driven design, and kernel principles. Use when designing new modules or making architectural decis...
Document-Driven Development workflow for existing codebases. Provides systematic planning, documentation-first design, and implementation verification.
Knowledge and patterns for understanding project structures, architectures, and codebases.
Knowledge and patterns for identifying and resolving performance issues.
Knowledge and patterns for designing RESTful and GraphQL APIs.
Knowledge and patterns for designing software architectures and system design.
Knowledge and patterns for designing comprehensive test strategies and writing effective tests.
PRDと機能設計書に基づいてアーキテクチャ設計書を作成するスキル。docs/prd.md と docs/functional-design.md が存在する場合に、テクノロジースタック、レイヤードアーキテクチャ、データ永続化戦略、パフォーマンス要件、セ...
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.