script-extractor
Detects inline logic anti-pattern in prompts and identifies opportunities to extract deterministic operations to scripts
Detects inline logic anti-pattern in prompts and identifies opportunities to extract deterministic operations to scripts
Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior
Browser console message analysis for debugging JavaScript errors, warnings, and application logs. Use when investigating frontend issues, tracking console output, or diagnosing JavaScript problems.
Query Logfire logs via the Logfire query API using read tokens and JSONL output. Use when you need to fetch or filter Logfire records, build log queries, or provide agent-ready log retrieval from this repo. Triggers: Logfire read, query API, JSONL logs, read token, log retrieval, log queries.
高頻度イベントに対するデバウンス/スロットリングの設計・実装・検証を整理するスキル。 UIイベントやファイル監視の負荷を最適化し、応答性と安定性を両立する。 Anchors: • Debounce Pattern / 適用: 連続入力の抑制 / 目的: 不要な処理の削減 • Throttle Pattern / 適用: 定期的な処理制御 / 目的: リソース負荷の平準化 • Web Performance Patterns / 適用: UIイベント最適化 / 目的: UX改善 Trigger: Use when optimizing high-frequency events, selecting debounce/throttle strategies, tuning delay intervals, or validating performance impacts. debounce, throttle, event optimization, scroll resize, input performance
Evaluate captured screenshots for layout issues, masked elements, and rendering problems. Use after taking screenshots to validate visual correctness and automatically resize viewport if elements are unexpectedly clipped.
Language-specific vulnerability detection patterns for JavaScript/TypeScript, Python, Go, Java, Ruby, and PHP. Provides regex patterns and grep commands for common security vulnerabilities.
Index of vulnerability detection pattern skills. Routes to core patterns (universal) and language-specific patterns for security scanning.
System diagnostics using osquery. Use when asked about CPU usage, memory consumption, network connections, running processes, disk I/O, fan speeds, temperatures, or system security. Triggers: "why is my computer slow", "what's using memory", "what's using CPU", "network connections", "suspicious processes", "system health", "fan running", "overheating", "disk activity", "what processes are running", "file changes", "browser extensions", "Docker containers", "startup programs", "file hash", "installed apps", "what runs at boot".
Performance - Core Web Vitals, bundle size. Use when optimizing speed.
コマンドのパフォーマンス最適化(トークン効率化/並列実行/モデル選択/速度改善)を整理し、性能改善の判断と適用を支援するスキル。 計測観点、最適化手順、テンプレート運用を一貫して整理する。 Anchors: • High Performance Browser Networking (Ilya Grigorik) / 適用: パフォーマンス測定 / 目的: レイテンシー削減 • Design of Computer Programs (Peter Norvig) / 適用: 最適化設計 / 目的: 実行速度向上 • Programming Pearls (Jon Bentley) / 適用: トークン効率化 / 目的: リソース削減 Trigger: Use when optimizing command performance, reducing token usage, or designing parallel execution flows and model selection. command performance, token optimization, parallel execution, model selection
Reactアプリケーションのパフォーマンス最適化を体系的に実施するスキル。測定駆動の最適化アプローチで、不要な再レンダリングを削減し、ユーザー体験を向上させる。 Anchors: • High Performance Browser Networking (Ilya Grigorik) / 適用: パフォーマンス測定手法 / 目的: データに基づいた最適化判断 • React公式ドキュメント (Dan Abramov) / 適用: React.memo・useCallback・useMemo / 目的: 測定駆動の最適化実践 • Clean Code (Robert C. Martin) / 適用: 早すぎる最適化を避ける原則 / 目的: 必要な最適化のみ実施 Trigger: Use when optimizing React performance, reducing re-renders, applying React.memo, analyzing with React DevTools Profiler, implementing Context splitting, or diagnosing rendering performance issues. performance optimization, React performance, re-rendering, React.memo, useCallback, useMemo, profiler
Analyze specialized file types beyond standard PE executables - .NET assemblies, Office macros, PDFs, PowerShell scripts, JavaScript, archives, and Linux ELF binaries. Use when you encounter documents, scripts, or non-Windows executables that require format-specific analysis tools and techniques.
This skill should be used when debugging frontend/UI bugs that need runtime evidence. USE THIS SKILL (instead of adding console.log) when you're about to: "add console.log and ask user to check", "open DevTools and tell me what you see", "reproduce the bug and share the output", "check the browser console". Triggers: "debug this", "fix this bug", "why isn't this working", "investigate this issue", "trace the problem", "figure out why X happens", "UI not updating", "state is wrong", "value is null/undefined", "click doesn't work", "modal not showing". Automates log collection server-side - you read logs directly, no user copy-paste needed.
Runs performance benchmarks for SDL3 HammerEngine and detects regressions by comparing metrics against baseline. Use when testing performance-sensitive changes to AI, collision, pathfinding, particle systems, or before merging features to ensure no performance degradation.
Code tracing, debugging, "why not called", flow analysis, state dependencies
Elixir and Phoenix development guidelines with critical language-specific gotchas. Use when writing Elixir code, Phoenix applications, or Mix tasks. Prevents common mistakes with list access, variable rebinding, struct access, and OTP patterns that cause subtle bugs or compilation errors.
Performs comprehensive diagnostics on the codex cache system, detects issues, and can fix them automatically with repair operations. Delegates to fractary CLI for health checks and diagnostics.
システムのパフォーマンス測定・分析・最適化を行うスキル。 負荷テスト、ストレステスト、ボトルネック分析を通じて性能改善策を提示します。 Anchors: • The Art of Application Performance Testing (Ian Molyneaux) / 適用: パフォーマンステスト戦略 / 目的: 体系的な性能評価手法の確立 • Systems Performance (Brendan Gregg) / 適用: USE/REDメソッド / 目的: メトリクス分析とボトルネック特定 • Google SRE Book / 適用: SLO/SLI設計 / 目的: 目標ベースの性能評価 Trigger: Use when measuring system performance, identifying bottlenecks, load testing, or optimizing application speed. performance testing, load testing, stress testing, bottleneck analysis, latency, throughput, response time, profiling, benchmarking, performance optimization
System diagnostics, verification, and troubleshooting for Badger 2350. Use when checking firmware version, verifying installations, diagnosing hardware issues, troubleshooting errors, or performing system health checks on Badger 2350.
This skill should be used when writing Claude Code plugin hooks or debugging the "operation was aborted" error. Teaches the critical "immediate response" pattern that prevents Claude Code's internal timeout from aborting hooks. Essential knowledge for plugin developers creating PreToolUse, PostToolUse, UserPromptSubmit, Stop, or SessionStart hooks.
Universal vulnerability detection patterns applicable across all programming languages. Includes hardcoded secrets, SQL/command injection, path traversal, and configuration file patterns.