Discover devops architecture patterns skills, compare source repositories and read the instructions for each workflow.
AI-supervised development workflow. Use when running prep, cook, serve, tidy, or work commands, managing beads issues during sessions, or following prep→cook→serve→tidy cycle. Covers workflow orchestration, gua...
Build, refine, and evolve OpenCode agents with opinionated, research-backed guidance. Combines documentation research (webfetch, exa, context7, grep.app) with architectural best practices. Use for creating new...
AI Developer following TDD principles in AI-Agentic Scrum. Use when implementing PBIs, managing subtasks, or executing the TDD cycle within Scrum.
Functional programming patterns for reliable TypeScript. Use when modeling state machines, discriminated unions, Result/Option types, branded types, or building type-safe domain models.
DDD and hexagonal architecture with functional core pattern. Use when designing features, modeling domains, breaking down tasks, or understanding component responsibilities.
Safe database migration workflow with zero-downtime strategies
ROS 2 System Architect for designing scalable Node graphs, Topic namespaces, and QoS profiles.
Khởi tạo các gói tin ROS 2 (C++/Python) chuẩn kiến trúc Antigravity.
Quản lý quy trình biên dịch gói tin ROS 2 sử dụng Colcon với các cấu hình tối ưu.
Complete Test-Driven Development workflow with red-green-refactor cycle
RESTful and GraphQL API design patterns and best practices
Use when multiple operations access shared state. Use when order of operations matters. Use when "it works most of the time" but occasionally fails mysteriously.
Use when deciding where to catch errors. Use when errors propagate too far or not far enough. Use when designing component/service isolation.
Use when designing or modifying APIs. Use when adding breaking changes. Use when clients depend on API stability.
Use when tempted to use class inheritance. Use when creating class hierarchies. Use when subclass needs only some parent behavior.
Use when a class creates its own dependencies. Use when instantiating concrete implementations inside a class. Use when told to avoid dependency injection for simplicity.
Use when handling errors. Use when tempted to catch and swallow exceptions. Use when returning default values to hide failures.
Use when acquiring multiple locks. Use when operations wait for each other. Use when system hangs without crashing.
Use when creating subclasses or implementing interfaces. Use when tempted to override methods with exceptions or no-ops. Use when inheritance hierarchy feels wrong.
Use when designing interfaces. Use when implementing interfaces with methods you don't need. Use when forced to implement throw/no-op for interface methods.
Use when tempted to add features "for later". Use when building "production-ready" systems before needed. Use when adding flexibility that isn't required yet.
Use when creating custom exceptions. Use when error handling feels chaotic. Use when catch blocks are too broad or too specific.
Use when adding new functionality to existing code. Use when tempted to add if/else or switch branches. Use when extending behavior of existing classes.
Python application architecture with functional core, effectful shell, DDD, and data modeling. Use when designing application layers, separating pure business logic from IO, defining domain models, implementing...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.