spec-miner
Reverse-engineer specifications from undocumented code. Use for legacy systems or creating documentation from implementations.
code-review-repo
Review local codebase for bugs and CLAUDE.md compliance using multi-agent analysis
profiling-with-cpu-sampler
Time-based sampling profiler showing WHERE execution time is spent (wall-clock time, not frequency). Provides histogram with self/total time, compilation tiers (T0/T1/T2), and flame graphs. Use as FIRST step to identify hot functions consuming most time. Low overhead, suitable for longer runs. Pair with tracing-execution-counts to understand time-per-execution vs execution frequency.
chrome-devtools
Complete guide to using Chrome DevTools MCP server for browser automation with Claude Code
a11y-checker
Accessibility audit for CSS covering focus styles, color contrast, text sizing, screen reader support, and WCAG compliance. Provides actionable fixes. Use when auditing accessibility or fixing a11y issues.
browser-forensics
Analyze web browser artifacts for forensic investigation. Use when investigating user browsing activity, downloaded files, cached content, or web-based attacks. Supports Chrome, Firefox, Edge, Safari, and Internet Explorer artifacts.
oe-backend-prod-hardening
Production hardening review for the OpenEvent backend. Use when scanning for LLM smells, noisy prints, swallowed exceptions, dev-only defaults, fallback diagnostic leakage, and inconsistent error/logging patterns; produce a prioritized, PR-sized cleanup plan.
refactoring-09-performance-profiling
Use when profiling and making small performance improvements in Python research code.
cloudflare-workers-observability
This skill should be used when the user asks about "worker logs", "debug worker", "worker errors", "request analytics", "worker metrics", "performance monitoring", "error rate", "invocation logs", "troubleshoot worker", "worker analytics", or needs to debug and monitor Cloudflare Workers.
core-web-vitals
Measure and optimize Core Web Vitals (LCP, INP, CLS). Use when implementing CWV tracking or debugging performance.
anti-reversing-techniques
Understand anti-reversing, obfuscation, and protection techniques encountered during software analysis. Use when analyzing protected binaries, bypassing anti-debugging for authorized analysis, or understanding software protection mechanisms.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior in C#/.NET code before proposing fixes; applies to gRPC services, EF Core queries, async operations, and build failures
chrome-devtools-site-search
Validate website parsing and browser automation feasibility by browsing and searching within a user-specified website scope using the chrome-devtools MCP server (mcp_servers.chrome-devtools); summarize results backed by observed page content (real titles/URLs), and open matching pages for review. Use when the user asks you to open a site, find specific content on it, run a site-scoped query, and keep the relevant pages open.
cache-observability
Track cache hit rates, latency, and detect cache-related issues
chrome-devtools
This skill should be used when the user asks to "inspect the page", "take a screenshot", "check how it looks", "check console", "console errors", "JavaScript errors", "debug the page", "analyze performance", "page speed", "performance trace", "why is it slow", "check network", "API calls", "network requests", "loading issues", "check localhost", or mentions frontend debugging, browser inspection, or DevTools analysis.
javascript-best-practices
JavaScript coding standards and best practices. This skill should be used when writing, reviewing, or refactoring JavaScript code. Triggers on tasks involving vanilla JavaScript, DOM manipulation, async operations, or performance optimization.
debug-console
Debug web app by capturing and analyzing console errors using Chrome DevTools MCP
go-performance-best-practices
Go performance optimization guidelines for profiling, allocation, GC tuning, concurrency, PGO, and I/O. This skill should be used when writing, reviewing, or optimizing Go code for performance. Triggers on tasks involving slow services, high latency, high memory usage, memory leaks, goroutine leaks, GC pressure, CPU profiling, pprof analysis, allocation reduction, sync.Pool, mutex contention, HTTP client tuning, Profile-Guided Optimization, GOMEMLIMIT tuning, Go 1.24 features, Swiss Tables, or any Go performance investigation.
ios-sim-interrogate
iOS Simulator interrogation: simctl screenshots/video, Web Inspector for web content, Instruments for native behaviors.
chrome-devtools-mcp
Use Chrome DevTools MCP for browser-side dev/test/debug (console, network, performance, UI issues). Trigger when debugging frontend behavior or performance.