DeFi

Use when creating new skills, documenting workflows, or standardizing processes into reusable skill definitions.

安全で可逆的なデータベースマイグレーションを設計・運用するスキル。スキーマ変更計画、移行期間、ロールバックまでの実務フローを整理する。Anchors:• Refactoring Databases / 適用: 安全なスキーマ進化 / 目的: 破壊的変更の最小化• Drizzle Kit / 適用: マイグレーション生成 / 目的: 変更管理の自動化• Zero-Downtime Patterns / 適用: 本番適用 / 目的: サービス停止の回避Trigger:Use when planning schema changes, generating migrations, applying them safely, or defining rollback/transition strategies.database migrations, schema change, drizzle kit, rollback, zero downtime

DrizzleORMを使用したデータベーススキーマ設計、マイグレーション、型安全なクエリ構築を専門とするスキル。SQLite、PostgreSQL、MySQLに対応し、TypeScriptの型システムを最大限活用した堅牢なDB層を構築する。Anchors:• Drizzle ORM公式ドキュメント / 適用: スキーマ定義とマイグレーション / 目的: 型安全なDB設計の基盤• TypeScript型システム / 適用: クエリビルダーとスキーマ定義 / 目的: エンドツーエンドの型安全性• Database Design for Mere Mortals (Hernandez) / 適用: リレーション設計 / 目的: 正規化と参照整合性Trigger:Use when defining Drizzle schemas, creating migrations, building type-safe queries, designing relations, or optimizing database performance.drizzle, orm, schema, migration, sqlite, postgresql, type-safe query

ドメイン駆動設計におけるユビキタス言語の確立と適用を専門とするスキル。ドメインエキスパートと開発者が共有する厳密な語彙体系を構築し、コミュニケーションの齟齬を防ぐ。Anchors:• Domain-Driven Design (Eric Evans) / 適用: ユビキタス言語の原則と実践 / 目的: コードとドメインの一貫性確保• Bounded Context / 適用: コンテキスト境界での用語の意味の違いを管理 / 目的: 用語の曖昧さ排除Trigger:Use when establishing domain terminology, creating glossaries, aligning business and technical vocabulary,extracting terms from requirements, defining ubiquitous language for DDD projects,resolving naming conflicts in code, or maintaining domain vocabulary consistency.

This skill should be used when the user requests a code review of changed files. Use this to review git-diffed files for security vulnerabilities (OWASP Top 10), performance issues (O(N) complexity, ORM optimization), bugs, and adherence to project coding standards defined in agents.md and claude.md.

Standardize markdown document creation and updates with proper headers and footers. Use when creating OR updating any markdown file that is NOT a subagent, command, or skill definition. Ensures consistent metadata, classification, and change tracking.

This skill enables Claude to create Application Performance Monitoring (APM) dashboards. It is triggered when the user requests the creation of a new APM dashboard, monitoring dashboard, or a dashboard for application performance. The skill helps define key metrics and visualizations for monitoring application health, performance, and user experience across multiple platforms like Grafana and Datadog. Use this skill when the user needs assistance setting up a new monitoring solution or expanding an existing one. The plugin supports the creation of dashboards focusing on golden signals, request metrics, resource utilization, database metrics, cache metrics, business metrics, and error tracking.

Create custom Task subagents in ~/.claude/agents/. Use when defining new agents for Task tool delegation.

Given-When-Then 形式の受け入れ基準を整理し、テスト可能な完了条件の定義を支援するスキル。要件の明確化、シナリオ設計、検証手順を一貫して整理する。Anchors:• Software Requirements (Karl Wiegers) / 適用: 要件分析・仕様化 / 目的: テスト可能な要件定義の手法• BDD in Action (John Ferguson Smart) / 適用: Given-When-Thenパターン / 目的: 振る舞い駆動開発の基盤Trigger:Use when defining acceptance criteria, user story specifications, or testable requirements.acceptance criteria, user story, GWT, Given-When-Then, testable requirements, definition of done

This skill enables Claude to generate Docker Compose configurations for multi-container applications. It leverages best practices for production-ready deployments, including defining services, networks, volumes, health checks, and resource limits. Claude should use this skill when the user requests a Docker Compose file, specifies application architecture involving multiple containers, or mentions needs for container orchestration, environment variables, or persistent data management in a Docker environment. Trigger terms include "docker-compose", "docker compose file", "multi-container", "container orchestration", "docker environment", "service definition", "volume management", "network configuration", "health checks", "resource limits", and ".env files".

アプリケーションとインフラの監視・アラート設計を専門とするスキル。ゴールデンシグナル（レイテンシー・トラフィック・エラー・飽和度）に基づくメトリクス戦略、構造化ログ設計、SLI/SLO定義、アラート閾値設定、ダッシュボード構成を統合的に提供する。Anchors:• Observability Engineering (Charity Majors) / 適用: ログ設計とメトリクス戦略 / 目的: 高カーディナリティ観測の実現• Site Reliability Engineering (Google) / 適用: SLI/SLO設計 / 目的: ビジネス価値に基づく監視体系• Golden Signals / 適用: 4指標（Latency・Traffic・Errors・Saturation） / 目的: 効果的な監視指標の選定Trigger:Use when designing monitoring strategy, defining SLI/SLO, configuring alerts, implementing structured logging, or building observability dashboards.monitoring, alerting, observability, metrics, logging, SLI, SLO, golden signals, dashboard, Grafana, Prometheus, Discord webhook

コマンド引数（$ARGUMENTS、位置引数）の設計と検証を整理し、引数仕様・検証・エラー設計を一貫して支援するスキル。引数設計方針、検証ルール、テンプレート運用を段階化する。Anchors:• The Pragmatic Programmer (Andrew Hunt, David Thomas) / 適用: 引数仕様と検証の設計 / 目的: 堅牢な引数システムの確立Trigger:Use when adding command arguments, defining $ARGUMENTS or positional arguments, or designing argument validation/error handling.command arguments, $ARGUMENTS, positional arguments, argument validation, error message design

Implements reliability patterns including circuit breakers, retries, fallbacks, bulkheads, and SLO definitions. Provides failure mode analysis and incident response plans. Use for "SRE", "reliability", "resilience", or "failure handling".

This skill enables Claude to monitor and analyze application error rates to improve reliability. It is used when the user needs to track and understand errors occurring in their application, including HTTP errors, application exceptions, database errors, external API errors, background job errors, and client-side errors. Use this skill when the user asks to "monitor errors", "analyze error rates", "track application errors", or requests help with "error monitoring". It sets up comprehensive error tracking and alerting based on defined thresholds.

ORMベストプラクティスの専門スキル。Drizzle ORMを活用したエンティティ設計、リレーション管理、パフォーマンス最適化を提供します。Anchors:• Designing Data-Intensive Applications (Martin Kleppmann) / 適用: データモデリング / 目的: 型安全なスキーマ定義とパフォーマンス最適化• Drizzle ORM Documentation / 適用: TypeScript ORM / 目的: 型推論とクエリビルダーの活用• High Performance MySQL (Baron Schwartz) / 適用: クエリ最適化 / 目的: N+1問題とインデックス戦略Trigger:Use when defining Drizzle ORM schemas, mapping entity relationships, optimizing database queries, solving N+1 problems, or implementing type-safe data access patterns.ORM, Drizzle, schema, relation, N+1, query builder, type-safe, entity mapping

Model Context Protocol (MCP) 仕様と実装パターン。サーバー設定、ツール定義、LLM統合向けJSONスキーマ設計を提供。Anchors:• MCP Official Specification / 適用: プロトコルバージョン、メッセージフォーマット / 目的: 仕様準拠• JSON Schema Draft-07 / 適用: inputSchemaバリデーション / 目的: 型安全ツール定義• The Pragmatic Programmer / 適用: DRY、直交性 / 目的: 保守性の高い設定Trigger:Use when configuring MCP servers, designing tool definitions with JSON Schema,validating MCP protocol compliance, or troubleshooting connection/timeout errors.

This skill enables Claude to validate application performance against defined budgets. It's useful for identifying performance regressions early in the development lifecycle. The skill is triggered when the user mentions "performance budget", "validate budget", "performance regression", or requests a check against performance metrics like "page load times", "bundle sizes", "API response times", or "Lighthouse scores". The plugin validates against predefined thresholds and alerts on violations. It is especially helpful in CI/CD pipelines to prevent performance degradation in production.

This skill allows Claude to construct and configure neural network architectures using the neural-network-builder plugin. It should be used when the user requests the creation of a new neural network, modification of an existing one, or assistance with defining the layers, parameters, and training process. The skill is triggered by requests involving terms like "build a neural network," "define network architecture," "configure layers," or specific mentions of neural network types (e.g., "CNN," "RNN," "transformer").

This skill enables Claude to create intelligent alerting rules for proactive performance monitoring. It is triggered when the user requests to "create alerts", "define monitoring rules", or "set up alerting". The skill helps define thresholds, routing, and escalation policies, and offers options for multi-category alert creation, including latency, error rate, throughput, resource utilization, availability, and SLO violation alerts. It is useful for Site Reliability Engineers (SREs) and DevOps teams looking to improve system observability.

React Server Components（RSC）の実装パターンとNext.js App Routerにおけるベストプラクティスを提供する専門スキル。サーバーコンポーネントとクライアントコンポーネントの責務分離、データフェッチの最適化、Suspenseとストリーミングの活用を支援します。Anchors:• 『Learning React Server Components』（Tejas Kumar）/ 適用: RSCアーキテクチャ / 目的: サーバーとクライアント間の責務分離• Next.js App Router公式ドキュメント / 適用: RSC実装パターン / 目的: Next.js固有の最適化手法• Dan Abramovのブログ / 適用: RSC設計思想 / 目的: 第一原理からの理解Trigger:Use when implementing Next.js App Router, designing Server Components, defining Client Component boundaries, optimizing data fetching, integrating Suspense, or implementing streaming SSR.rsc, server components, client components, next.js app router, use client, suspense, streaming, data fetching