operability-observation
運用観測性の確保。ログ、メトリクス、ヘルスチェック、設定検証でバグを扱う能力を担保。Use when: デプロイ前チェック、障害調査が困難、原因不明、ログ設計、メトリクス設計、設定管理実装。
Discover data ai debugging skills, compare source repositories and read the instructions for each workflow.
運用観測性の確保。ログ、メトリクス、ヘルスチェック、設定検証でバグを扱う能力を担保。Use when: デプロイ前チェック、障害調査が困難、原因不明、ログ設計、メトリクス設計、設定管理実装。
PCE(Process-Context Engine)とLDE(Law-Driven Engineering)を統合した実行時Law違反監視スキル。 本番環境でのLaw違反を検知し、pce-memoryにフィードバックして継続的改善を促す。 使用タイミング: (1) 本番ログからLaw...
Chrome DevTools MCPを使用したWebアプリのデバッグ支援スキル。ブラウザ操作、コンソールログ監視、ネットワークリクエスト分析、パフォーマンス計測を行う。 使用タイミング: (1) Webアプリの動作確認・デバッグ (2) UIの自...
4-phase root cause debugging process. Use when fixing bugs or investigating issues.
Security vulnerability detection based on OWASP Top 10. Use when reviewing code for security issues.
React and Next.js performance optimization guidelines from Vercel Engineering. Contains 45+ rules across 8 categories, prioritized by impact. Use when writing new React components, implementing data fetching, r...
AI-assisted pair programming with multiple modes (driver/navigator/switch), real-time verification, quality monitoring, and comprehensive testing. Supports TDD, debugging, refactoring, and learning sessions. Fe...
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers onKeywords: lint, format, check, validate, type...
4-phase systematic debugging methodology with root cause analysis and evidence-based verification. Use when debugging complex issues.
Performance profiling principles. Measurement, analysis, and optimization techniques.
VictoriaMetrics + Loki + Grafana. Light or full mode.
Diagnose compile errors and runtime issues using logs and headless runs
Use when the root cause is unclear. Trace the failure back through the call stack and isolate the first bad state.
This skill should be used when the user asks to "detect project type", "analyze this project", "create project profile", "what tech stack is this", "scan project structure", "what database does this use", or wh...
This skill should be used when the user asks to "optimize performance", "improve caching", "speed up my app", "reduce latency", "configure Argo", "setup tiered caching", or is working on performance improvement...
This skill should be used when the user asks to "debug a Worker", "view logs", "check analytics", "monitor performance", "trace errors", "setup logging", "wrangler tail", "check metrics", or needs to troublesho...
OpenAI Codex CLIを使用したコードレビュー、分析、コードベースへの質問を実行する。使用場面: (1) コードレビュー依頼時、(2) コードベース全体の分析、(3) 実装に関する質問、(4) バグの調査、(5) リファクタリング提案、(6...
Creates, analyzes, updates, and improves Claude Code hooks including configuration, scripts, and security validation. Use when user asks how hooks work, explaining hook concepts, understanding hook types and ev...
Discover available effects, actions, and placeholders in a Sandestin project. Use when asking what effects exist, searching for functionality, or needing example invocations. Keywords: effects, actions, dispatc...
Discover available effects, actions, and placeholders in a Sandestin project. Use when asking what effects exist, searching for functionality, or needing example invocations. Keywords: effects, actions, dispatc...
Use when generate test coverage, or when asked "generate test coverage", "generate coverage", "find coverage". Provide how to get test coverage of specific component.
This skill shoudl be used when the user ask to "behaviors", "specification", "read implementation", "analyze component", "振る舞いを分析", "振る舞いを理解". Analyze component(module, package, class, function) b...
Use when optimizing code for performance, reducing bundle size, improving load times, or fixing performance bottlenecks. Emphasizes measurement-driven optimization.
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.