Deep analysis debugging mode for complex issues. Activates methodical investigation protocol with evidence gathering, hypothesis testing, and rigorous verification. Use when standard troubleshooting fails or when issues require systematic root cause analysis.
Debuggt HTML Formulare und JavaScript, findet Frontend-Fehler
TRACE ํ๋ ์์ํฌ(Trace, Read, Analyze, Check, Execute)๋ฅผ ์ฌ์ฉํ ์ฒด๊ณ์ ์ธ ๋๋ฒ๊น ๋ฐ ์๋ฌ ํด๊ฒฐ์ ๋๋ค. ์๋ฌ ๋๋ฒ๊น , ์คํ ํธ๋ ์ด์ค(stack traces) ๋ถ์, ์คํจ ์กฐ์ฌ, ๊ทผ๋ณธ ์์ธ ๋ถ์(root cause analysis) ๋๋ ์ด์ ์ด์ ํธ๋ฌ๋ธ์ํ ์ ์ฌ์ฉํฉ๋๋ค.
Use when the app is slow or when optimizing functions. Enforces profile-first methodology to prevent premature optimization.
Systematic debugging with 5-step loop for issues in spaces/[project]/. Use when encountering bugs, test failures, or unexpected behavior.
Expert Security Analyst for deep research and exploitability analysis of security findings. Use when you have a specific finding from semgrep, trufflehog, or manual code review that needs thorough investigation to determine if it represents an exploitable vulnerability with real-world impact.
This skill should be used when the user asks to "explore claude code source", "find internal features", "investigate cli.js", "check beta headers", "discover hidden settings", or mentions "minified code analysis", "anthropic-beta headers", "context management internals".
Profile and optimize Python backend code using cProfile, memory profilers, and performance best practices. Use when debugging slow FastAPI code, optimizing bottlenecks, or improving application performance.
ะญะบัะฟะตัั ะฟะพ TypeScript. ะัะฟะพะปัะทัะน ะดะปั ัะธะฟะธะทะฐัะธะธ, ะดะถะตะฝะตัะธะบะพะฒ, ะดะตะบะพัะฐัะพัะพะฒ, ะฟะฐััะตัะฝะพะฒ ะฟัะพะตะบัะธัะพะฒะฐะฝะธั ะธ best practices ะฒ TypeScript.
Web performance optimization best practices including Core Web Vitals, loading, and caching.
Bundle size optimization including tree shaking, code splitting, and dependency analysis. Use when reducing bundle size.
This skill should be used when debugging full-stack issues that span UI, backend, and database layers. It provides a systematic workflow to detect errors, analyze root causes, apply fixes iteratively, and verify solutions through automated server restarts and browser-based testing. Ideal for scenarios like failing schedulers, import errors, database issues, or API payload problems where issues originate in backend code but manifest in the UI.
็พๅจใฎClaudeใปใใทใงใณๅ ใงใฏใคใใฏใฌใใฅใผใๅฎๆฝใใพใใใณใณใใญในใใไฟๆใใใพใพๅณๅบงใซใณใผใๅ่ณชใใปใญใฅใชใใฃใใใใฉใผใใณในใ่ฉไพกใใพใใ
Debug and trace WaveCap system events. Use when the user wants to investigate duplicate events, trace event sources, debug recording start/stop issues, or understand event flow.
็จ็ฎๅ็่ฏญ่จๅ็ฑปๆฏ่งฃ้ไปฃ็ ็ๅทฅไฝๅ็๏ผ้ๅๅๅญฆ่ ็่งฃๅคๆไปฃ็
Performance and scalability analysis specialist. Identifies algorithmic inefficiencies, N+1 queries, memory leaks, and concurrency issues. Use when reviewing loops, database queries, file I/O, or high-concurrency code.
Debug Laravel applications systematically with this comprehensive troubleshooting skill. Covers class/namespace errors, database SQLSTATE issues, route problems (404/405), Blade template errors, middleware issues (CSRF/auth), queue job failures, and cache/session problems. Provides structured four-phase debugging methodology with Laravel Telescope, Debugbar, Artisan tinker, and logging best practices for development and production environments.
Expert Go developer specializing in Go 1.21+ features, concurrent programming with goroutines and channels, and comprehensive stdlib utilization. This agent excels at building high-performance, concurrent systems with idiomatic Go patterns and robust error handling.
Analyzes Ecto queries for N+1 problems, missing preloads, and performance issues.
Explore the codebase to find relevant files, patterns, and examples for a feature or bug.
Automated testing with Chrome DevTools MCP server ALWAYS in incognito mode to avoid cache issues
