Reviews finished and in-progress digital products to assess adherence to design specifications and discover potential issues with those specifications. Validates implementation against design intent, identifies visual and interaction discrepancies, and provides actionable feedback for design and engineering teams.
Comprehensive metrics dashboard strategy including North Star Metric definition, AARRR Pirate Metrics framework, product engagement tracking, 5 role-specific dashboards, alert configuration, data infrastructure planning, and 90-day implementation roadmap for data-driven decision making
CLAIM a specific GitHub issue to START working on it. Requires an issue number. Performs validation, atomic claim, posts claim comment, and sets up worktree. USE THIS SKILL WHEN: - User says "claim issue #N" or "claim #N" - User says "start working on issue #N" or "take issue #N" - User says "I'll work on #N" or "pick up #N" - User wants to BEGIN work on a specific issue number - User selected an issue from available work and wants to claim it REQUIRED: An issue number must be specified or identifiable from context. DO NOT USE THIS SKILL WHEN: - User just wants to SEE status (use ghe-status) - User is ALREADY working and wants to post update (use ghe-checkpoint) - User wants to CHANGE phases (use ghe-transition) - User wants reports (use ghe-report) - No specific issue number is mentioned EXAMPLES: <example> Context: User wants to start work on a specific issue user: "Claim issue #201" assistant: "I'll use ghe-claim to claim issue #201 with the full protocol" </example> <example> Context: User picks from
Break down complex tasks into parallel workstreams for efficient execution. Use when planning multi-component features, large refactors, or any work that benefits from parallelization.
READ-ONLY quick overview of GitHub Elements workflow state. Shows active threads, phase distribution, and workflow health at a glance. USE THIS SKILL WHEN: - User asks "what's the status" or "show me the status" - User asks "what threads are active" or "what am I working on" - User asks "show me the workflow state" or "what's happening" - User wants a quick overview before starting work - Starting a session and need context DO NOT USE THIS SKILL WHEN: - User wants to CLAIM an issue (use ghe-claim) - User wants to POST a checkpoint (use ghe-checkpoint) - User wants to TRANSITION phases (use ghe-transition) - User wants DETAILED metrics/health reports (use ghe-report) EXAMPLES: <example> Context: User starting a session wants to see current state user: "What's the github elements status?" assistant: "I'll use ghe-status to show you the current workflow state" </example> <example> Context: User wants to know what work is available user: "Show me what threads are active" assistant: "I'll use ghe-status to disp
Semantic versioning, commit message standards, multi-agent coordination, and workflow guidelines
Loads project context, lists existing specs and changes, searches capabilities and requirements. Use when user asks about project state, existing specs, active changes, available capabilities, or needs context discovery. Triggers include "openspec context", "what specs exist", "show changes", "list capabilities", "project context", "find specs", "what's in the spec", "show me specs".
This skill should be used when the user asks about "observability", "logging", "metrics", "tracing", "monitoring", "structured logging", "log format", "log levels", "distributed tracing", "OpenTelemetry", "health checks", or needs guidance on implementing observability and monitoring requirements.
VoltAgent multi-agent system design with natural transformation coordination between agents. Use when building TypeScript multi-agent AI systems, implementing agent coordination with categorical patterns, designing supervisor-worker agent hierarchies, or creating composable agent architectures with typed message passing.
Validate DDD architecture compliance including layer separation, dependency rules, and patterns. Use when validating context before commit, checking new features, reviewing refactored code, or ensuring layer isolation (e.g., "Validate User context", "Check Product domain layer").
Rollback the latest to the previous deployment. Requires authentication. Use for Agentuity cloud platform operations
GitHub Actionsセルフホストランナーの設計、セットアップ、セキュリティ管理を行うスキル。 インストールから運用、トラブルシューティングまでの完全なライフサイクル管理を提供する。 Anchors: • GitHub Actions Documentation / 適用: セルフホストランナー公式仕様 / 目的: 正確なAPI使用と設定 • CIS Benchmark for Linux / 適用: ランナーホストのセキュリティ / 目的: セキュリティ強化 • The Pragmatic Programmer / 適用: 実践的改善 / 目的: 段階的な実装と継続的改善 Trigger: Use when setting up self-hosted runners, configuring runner labels, implementing security measures, troubleshooting runner issues, or optimizing runner performance. self-hosted, runner, GitHub Actions, ephemeral, labels, security, setup, configuration
GitHub Actionsを用いたCI/CDパイプラインの設計・実装・最適化を支援する。品質ゲート、並列化、キャッシング、デプロイ戦略、可観測性の判断を含む。Use when: GitHub Actionsワークフローの新規作成・改善、CI/CD自動化、品質ゲート設計、並列化やキャッシュ最適化が必要なとき。 Anchors: Continuous Delivery, DevOps, GitHub Actions workflow architecture Trigger: ci/cd pipeline design, github actions workflow, quality gate, caching strategy, parallel jobs, deployment automation
Electronアプリケーションのビルド・パッケージング・配布を統一的に管理する専門知識。 electron-builderによるクロスプラットフォーム対応、コード署名、インストーラー生成を支援。 Anchors: • electron-builder / 適用: ビルド設定・パッケージング / 目的: クロスプラットフォーム配布 • Code Signing / 適用: macOS/Windows署名 / 目的: セキュアな配布 • The Pragmatic Programmer / 適用: ビルドプロセス設計 / 目的: 繰り返し可能なワークフロー Trigger: Use when building production Electron applications, generating installers for macOS/Windows/Linux, implementing code signing, or packaging desktop apps for release. electron-builder, dmg, exe, AppImage, code signing, packaging
Service mesh implementation with Istio for traffic management, security, and observability. Use when implementing mTLS, traffic routing, circuit breakers, or service-to-service communication. Triggers: istio, service mesh, virtualservice, destinationrule, gateway, mtls, sidecar, envoy, traffic management.
Monitor a PR through CI, reviews, and merge conflicts until ready for human review. Use when user says "monitor PR", "watch PR", "wait for CI", or wants automated PR workflow. Creates PR if needed, then monitors Dagger CI, automated review comments, and merge conflicts.
This skill should be used for configuring devloop project settings via .devloop/local.md, git workflow preferences, commit settings, review options
This skill should be used when looking up Kyverno Helm chart versions, release dates, and corresponding app versions from Artifact Hub. Use for version planning, upgrade decisions, and release timeline analysis.
