আপনার এজেন্টের জন্য উপযুক্ত সক্ষমতা খুঁজে নিন।
This skill should be used when the user asks about "metaprogramming", "DSL", "domain-specific language", "method_missing", "define_method", "class_eval", "instance_eval", "module_eval", "hooks", "included", "extended", "inherited", "singleton class", "eigenclass", "dynamic methods", "eval", or needs guidance on Ruby metaprogramming techniques.
Debug WebF app runtime issues with Chrome DevTools (console/network/elements) and JS-side troubleshooting. Use when the user mentions DevTools console, network tab, stack traces, blank screen, layout measurement issues, or failing network requests.
Phrack magazine article analysis, binary exploitation, vulnerability research, exploit development, Use-After-Free (UAF), heap exploitation, ROP chain, GDB debugging, pwntools, memory corruption, CVE analysis, ProFTPd exploitation, Docker exploit lab, security research, educational hacking, buffer overflow, stack exploitation, shellcode development
[PHASE 4] Implements and validates fixes for verified theories. Entry: PERFORMANCE_THEORIES.md has a verified theory. Outputs: Code fix, BENCHMARK_BASELINE.md new column, theory marked fixed/fix-failed. Next: Loop to PHASE 2 if performance gaps remain, otherwise done.
Debug bugs and errors using intel-first approach with systematic root cause analysis. Use proactively when errors occur, tests fail, or unexpected behavior appears. MUST trace from symptom to root cause with CoD^Σ reasoning.
Analyze the impact of code changes by mapping call graphs and identifying all direct and indirect dependencies. Use when users ask about blast radius analysis, code change impact, who calls a function, downstream dependencies, or risk assessment before refactoring. Traces call chains, identifies high-risk modules, and provides ranked impact analysis.
Find and fix performance issues in Leavn - main thread blocking, heavy View body computation, missing lazy loading, inefficient list rendering
Toolkit para interagir e testar aplicações web locais usando Chrome DevTools MCP. Suporta verificação de funcionalidade frontend, debugging de UI, captura de screenshots, análise de performance, inspeção de network e visualização de logs do console.
Web performance optimization and Core Web Vitals. Covers LCP, FID, CLS, code splitting, lazy loading, caching strategies, image optimization, and performance monitoring. Trigger: When optimizing performance, when improving Core Web Vitals, when implementing code splitting, when optimizing images, when setting up caching.
pprof usage and performance analysis. Use when profiling applications.
Debug Svelte application issues systematically. This skill helps diagnose and resolve Svelte-specific problems including reactivity failures, runes issues ($state, $derived, $effect), store subscription memory leaks, SSR hydration mismatches, and compiler warnings. Covers both Svelte 4 legacy patterns and Svelte 5 runes-based reactivity. Provides debugging tools like $inspect(), {@debug} tags, and svelte-check CLI usage.
Comprehensive guide to CPU and memory profiling in Node.js and Python for identifying bottlenecks and optimizing performance
Explain code operation, logic, and design clearly and systematically. Use when the user asks to explain code, understand how something works, what a function does, or requests logic analysis.
Analyze system processes and resource usage to diagnose runaway processes. Use when investigating CPU/memory/IO spikes.
Debug ASP.NET Core and .NET applications with systematic diagnostic approaches. This skill covers troubleshooting dependency injection container errors, middleware pipeline issues, Entity Framework Core query problems, configuration binding failures, authentication/authorization issues, and startup failures. Includes Visual Studio and VS Code debugging, dotnet-trace, dotnet-dump, dotnet-counters tools, Serilog configuration, Application Insights integration, and four-phase debugging methodology.
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.
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".
Use for bugs, test failures, or unexpected behavior needing root cause
