chrome-extension-consultant
Chrome ํ์ฅ ํ๋ก๊ทธ๋จ ๊ฐ๋ฐ ์ปจ์คํดํธ
Essential command-line tools and system utilities.
Chrome ํ์ฅ ํ๋ก๊ทธ๋จ ๊ฐ๋ฐ ์ปจ์คํดํธ
Handle MoonBit bit-level parsing and pattern matching over BytesView slices, including using bytes[start:end] and bit patterns like [u1(i), u2(j), ..] or mixed-width fields. Use when extracting or validating packed fields from Bytes/BytesView with bit patterns.
Review OBS Studio plugins for correctness, memory safety, thread safety, and best practices. Audits module registration, callback implementations, resource cleanup, and common anti-patterns. Use when reviewing OBS plugin code or preparing for release.
Inspect and automate Obsidian using Chrome DevTools Protocol
Go performance optimizations including memory allocation reduction, efficient string building, I/O operations, and resource pooling. Use when optimizing Go code for speed or memory efficiency.
Analyze volatile memory (RAM) dumps for forensic investigation. Use when investigating malware infections, rootkits, process injection, credential theft, or any incident requiring analysis of system memory state. Supports Windows, Linux, and macOS memory images.
C# static analysis tool for call graphs, unused code detection, impact analysis, HTML documentation generation, and Graphviz diagram export
Debug โbackend wonโt start / first request 500 / ports stuckโ quickly. Use when uvicorn reload behaves strangely, ports 8000/3000 are blocked, or you see first-request errors like โunexpected keyword argumentโ due to stale bytecode caches.
This skill should be used when investigating .NET project dependencies, understanding why packages are included, listing references, or auditing for outdated/vulnerable packages.
Systematic debugging with root cause tracing. Use when encountering bugs, test failures, or unexpected behavior - find root cause before attempting fixes, trace backward through call chain.
Use this skill when the user asks about Rust module dependencies, dependency graphs, architecture visualization, cycle detection, DAG analysis, or module structure. Activate when you see phrases like "show module structure", "dependency graph", "visualize architecture", "check for circular dependencies", or "Mermaid diagram of modules".
WebSocket server and client patterns with heartbeat and reconnection. Use when implementing real-time features, debugging connection issues, or reviewing WebSocket code. Triggers on: WebSocket, wss, heartbeat, reconnect, real-time.
Gather threat intelligence using Shodan. Use for tracking threat actors, identifying attack infrastructure, and monitoring emerging threats. Triggers on requests for "threat intelligence", "track attackers", "C2 servers", or "threat hunting".
Use for bugs, test failures, or unexpected behavior needing root cause
Analyze and visualize state flow in LangGraph pipelines. Use when debugging state mutations, tracing data flow between nodes, identifying orphan state keys, detecting read/write dependencies, or generating Mermaid diagrams of state transitions. Triggers on phrases like "visualize state flow", "trace state key", "which nodes touch X", "state dependencies", "debug state mutation", "orphan state keys", "state flow diagram".
WHEN: Coverage analysis, finding untested files, test prioritization, coverage gap identification WHAT: Line/Branch/Function coverage + untested file list + priority by importance + improvement roadmap WHEN NOT: Test generation โ test-generator, Test quality โ code-reviewer
Bundle size analysis, budget enforcement, and regression detection for Vite/Rollup builds. This skill should be used when: (1) analyzing bundle composition or total size, (2) checking size budgets, (3) comparing PR vs baseline for regressions, (4) investigating why bundle size increased, or (5) optimizing bundle size. Reads Vite manifest for chunk graph (Tier B). Cannot attribute sizes to specific npm packages without stats.json (Tier C unavailable by default).
Expert JavaScript developer specializing in ES2024+, modern language features, and performance optimization. Masters closures, prototypes, async patterns, and building production-grade JavaScript applications.
Systematically trace bugs backward through call stack to find original trigger
Debugs issues in the Moonbeam parachain including runtime panics, EVM execution failures, XCM message delivery problems, and client-side errors. Use when encountering transaction failures, unexpected behavior, state inconsistencies, block production issues, or RPC errors.
Use when planning or designing features and need to understand current codebase state, find existing patterns, or verify assumptions about what exists - prevents hallucination by grounding plans in reality
Systematic debugging framework ensuring root cause investigation before fixes. Includes four-phase debugging process, backward call stack tracing, multi-layer validation, and verification protocols. Use when encountering bugs, test failures, unexpected behavior, performance issues, or before claiming work complete. Prevents random fixes, masks over symptoms, and false completion claims.