tidb-optimizer-bugfix
Fix TiDB optimizer bugs with minimal diffs, hypothesis-driven validation, and regression tests. Use the bundled issue precedents only to avoid re-fixing already solved bugs or inspect suspect historical fixes.
tidb-profiler-analyzer
Processes and analyzes TiDB profiler zip packages (CPU or heap) for components like TiDB, TiKV, PD, or TiFlash. It unzips, aggregates the profiler data, and uses `go tool pprof` to report on the most time-consuming functions (CPU) or highest memory allocations (heap).
orchestrator
タスクの調整と他のロールへの委譲を行うコーディネーターロール
aegis-architect
アーキタイプベースのスキャフォールドツール - プロジェクトの重さに応じた型を選択
common
全ロール共通で使用できる基本ツール
browser-testing
ブラウザ自動化とE2Eテストを行うスキル
code-reviewer
コードレビューとベストプラクティスの提案を行うスキル
data-analyzer
データ分析と可視化を行うスキル
docx-handler
Word文書の読み取り、編集、作成を行うスキル
reindex-docs
Re-index all PDF and HTML documents, update index.html, and commit/push changes to the repository
repo-docs
Update and maintain core repository documentation files (README.md, CHANGELOG.md, LICENSE, CONTRIBUTING.md) before commits or releases. Use when users need to update documentation to reflect code changes, prepare for releases, or ensure documentation consistency.
aspose-slides
Comprehensive skill for manipulating Microsoft PowerPoint presentations using Aspose.Slides.NET library with modern C# patterns
dotnet-cqrs-api
Guide for building .NET APIs using CQRS pattern with MediatR, FluentValidation, and Carter modules
maker
Generate .NET Core data API code from model definitions using the Maker XML specification and CLI. Use when users need to: (1) Create Maker XML models from JSON objects, SQL scripts, or database schemas, (2) Generate .NET Core CRUD API endpoints from Maker XML, (3) Understand or validate Maker XML model definitions, or (4) Work with the Maker CLI tool for code generation.
ecto-query-analysis
Analyzes Ecto queries for N+1 problems, missing preloads, and performance issues.
elixir-architect
Use when designing or architecting Elixir/Phoenix applications, creating comprehensive project documentation, planning OTP supervision trees, defining domain models with Ash Framework, structuring multi-app projects with path-based dependencies, or preparing handoff documentation for Director/Implementor AI collaboration
api-versioning
API versioning strategies including URL-based, header-based, and breaking change management
containerization
Docker and Kubernetes deployment patterns for Elixir/Phoenix applications
distributed-systems
Distributed systems patterns for BEAM/OTP including clustering, supervision, and multi-region deployment
nerves-patterns
Nerves embedded development patterns for Elixir/Nerves systems
security-patterns
Elixir-specific security patterns, OWASP mitigations, and compliance best practices
test-generation
Generates comprehensive Elixir tests using ExUnit following TDD principles.
data-pipeline
GenStage, Broadway, and Flow for Elixir data pipelines
elixir-guidelines
Official Elixir community standards, naming conventions, and best practices
elixir-scribe
Single Responsibility Code in Self-Documented Folder Structure
git-workflow
Git and GitHub workflow automation skills for OpenCode agents
graphql-patterns
GraphQL patterns with Absinthe framework for Elixir/Phoenix applications
liveview-patterns
Phoenix LiveView UI and real-time feature patterns
migration-patterns
Zero-downtime Elixir/Phoenix database migrations and rollback strategies
nx-patterns
Nx and Livebook patterns for machine learning in Elixir
observability
Telemetry, metrics, tracing, and observability for Elixir/BEAM applications
otp-patterns
Implements OTP design patterns including GenServer, Supervisor, and Application behaviors.
performance-profiling
Performance profiling and optimization for Elixir/BEAM applications
resilience-patterns
Resilience and error recovery patterns including circuit breaker, retry strategies, and graceful degradation
ai-orchestration
LLM keyring management, multi-provider support, and AI agent orchestration
api-design
REST vs GraphQL, API versioning, rate limiting, and documentation for Elixir/BEAM APIs
measuring-pr-performance-impact
Measures GraphQL resolver latency changes before/after a PR merge using Datadog metrics. Use when analyzing PR performance impact, measuring latency changes, or comparing resolver performance before and after a code change.
gh-project-workflow
End-to-end GitHub execution workflow for project delivery: create project items, assign available single-select fields (such as Status and optional Area), convert draft items to issues when needed, create and check out development branches via `gh issue develop`, then commit, push, create/merge pull requests, and run deployment commands on request. Use when the user explicitly asks to operate GitHub issue/PR lifecycle, or when another repo workflow skill delegates the GitHub tracking and delivery steps to it.
learning-app-cdp
Inspect or debug the learning app in a real browser through the project-specific Windows Chrome CDP workflow. Prefer this skill for browser testing, browser debugging, console inspection, network capture, DOM/runtime inspection, and service-worker-aware refreshes against http://sprecha.localhost or https://sprecha.de. Commands: doctor, start-local/start-prod (launches Chrome with the debug port — use this when Chrome is down, never launch chrome.exe by hand), refresh-*, wait-* (--path/--selector), eval-* (--expression/--file), console-*, monitor-*, read, clear, stop.
learning-app-remote-inspect
Step-by-step debugging workflow for the learning app through a phone's Chrome remote-inspect target. Use when the user has `chrome://inspect/#devices` open and wants a copy-paste command loop for Console/Elements/Network instead of direct automation.
openspec-propose-change
Start a new OpenSpec change and create the first ready artifact for it. Use this when the user wants to propose a feature, fix, or structured change in this repository using the repo's OpenSpec workflow, or when a newly reported repo bug/feature is being translated into tracked work.
openspec-propose
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
repo-task-delivery
Use this when the user reports any problem, regression, warning, bug, improvement, or proposed repo change that is likely to result in a committed repository edit. Default to the full repo workflow: GitHub issue/project tracking, OpenSpec change, implementation, verification, pull request, merge, and closeout.
openspec-continue-change
Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.
openspec-archive-change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
openspec-verify-change
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
openspec-apply-change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
openspec-sync-specs
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
openspec-new-change
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
openspec-onboard
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
Page 1299 of 1665 · 83248 results