This skill should be used when the user asks about "lazy.nvim", "plugin performance", "neovim startup time", "slow neovim", "optimize plugins", "lazy-loading", "startuptime profiling", or wants to improve Neovim performance through better plugin management.
Find and fix unsafe error handling in Leavn - try! force unwraps, empty catch blocks, silent try? failures
Hybrid search strategy for finding relevant code: fast targeted search, then deep analysis if needed.
Expert in system optimization, profiling, and scalability. Specializes in eBPF, Flamegraphs, and kernel-level tuning.
Analyse throughput, case duration, and activity sojourn times from the filtered log.
Chrome DevTools MCPを使用したWebアプリのデバッグ支援スキル。ブラウザ操作、コンソールログ監視、ネットワークリクエスト分析、パフォーマンス計測を行う。 使用タイミング: (1) Webアプリの動作確認・デバッグ (2) UIの自動操作テスト (3) ネットワークエラーの調査 (4) コンソールエラーの確認 (5) パフォーマンス問題の診断 (6) フォーム入力の自動化 (7) スクリーンショット取得
Gemini Elite MCP Orchestrator. Master of Chrome DevTools, Context7 and Auto-Configuration.
運用観測性の確保。ログ、メトリクス、ヘルスチェック、設定検証でバグを扱う能力を担保。Use when: デプロイ前チェック、障害調査が困難、原因不明、ログ設計、メトリクス設計、設定管理実装。
Develop working exploits using pwntools. Includes exploit template and common patterns.
Optimize code for Cloudflare Workers free plan with 10ms CPU limit. Use when writing API routes, server code, middleware, or discussing performance optimization.
30 pragmatic rules for production JavaScript covering async operations, V8 optimization, memory management, testing, error handling, and performance. Use when writing JavaScript, optimizing performance, handling promises, or building production-grade applications. Includes promise rejection handling, V8 hidden classes, memory leak prevention, and structured testing patterns.
Analyze TypeScript errors and provide detailed diagnostics with root cause analysis and specific fix recommendations
Guide for debugging and performance optimization of EDS blocks including error handling, FOUC prevention, Core Web Vitals optimization, and debugging workflows for Adobe Edge Delivery Services.
This skill should be used when working on Obsidian plugins, testing plugin changes, verifying plugin UI, debugging plugin behaviour, or running automated tests against Obsidian. Also triggers on "start Obsidian", "take Obsidian screenshot", "test plugin", "run plugin command", "execute in Obsidian", or any Obsidian automation task. Use proactively during plugin development to verify changes visually.
Master network protocol reverse engineering including packet analysis, protocol dissection, and custom protocol documentation. Use when analyzing network traffic, understanding proprietary protocols, or debugging network communication.
Dumps and analyzes Graal IR compiler graphs showing optimization decisions. Use BGV format with bgv2json/seafoam to inspect escape analysis, boxing removal, inlining decisions, and call node types. Reveals what compiler actually optimized vs intended. Use as last resort after basic profiling when root cause remains unclear.
Systematically trace bugs backward through call stack to find original trigger
Use when animation doesn't work as expected, has bugs, or behaves inconsistently
Sagebaseのロギング規約とベストプラクティス。print文禁止、loggerの使用基準、ログレベルの使い分けをカバー。ログ出力を追加・修正する時、デバッグコードを書く時にアクティベートします。
Find root cause before attempting fixes through systematic investigation phases. WHEN: MUST use when encountering bugs, test failures, errors, build failures. Invoke with "/systematic-debugging" or "debug systematically". Use ESPECIALLY after multiple failed fixes or under time pressure. WHEN NOT: Issue is already understood with clear root cause, writing new features, simple typos.
