Help us improve
Share bugs, ideas, or general feedback.
From rldyour-browser
Дебаг браузерных багов - console errors, network, runtime, hydration, layout, performance через Chrome DevTools MCP. Используй для: ошибка в браузере, не работает UI, разбери баг, сеть, hydration, layout сломан, runtime exception. EN triggers: browser bug, debug UI, console errors, network failure, hydration error, fix browser issue, Lighthouse audit, layout broken, runtime exception.
npx claudepluginhub nddev-it-com/rldyour-claudecode --plugin rldyour-browserHow this skill is triggered — by the user, by Claude, or both
Slash command
/rldyour-browser:browser-debugThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Diagnose browser-only failures with runtime evidence. Use Chrome DevTools MCP for deep inspection and Playwright MCP for deterministic reproduction and validation.
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
Diagnose browser-only failures with runtime evidence. Use Chrome DevTools MCP for deep inspection and Playwright MCP for deterministic reproduction and validation.
User-facing reports stay in Russian unless requested otherwise. Browser artifacts belong under browser/.
Use this skill without waiting for explicit invocation when the task mentions:
browser-validation flow where evidence is needed to find root cause.Use browser-validation after fixing the issue to prove the user flow works.
Use this skill when:
Use mcp__plugin_rldyour-mcps_chrome-devtools__* tools (primary) and mcp__plugin_rldyour-mcps_playwright__* tools (reproduction):
browser/.get_symbols_overview, find_symbol, find_referencing_symbols) and implement the smallest correct fix.browser/ artifacts unless the user asks to keep evidence.Collect only evidence that matters:
Use Playwright after fixes to prove:
All screenshots, traces, videos, PDFs, and temporary browser evidence must be written under browser/.
Do not commit these artifacts. If the final answer needs evidence, mention filenames and observations. Delete artifacts after the task unless the user explicitly asks to keep them.
For debugging work, report in Russian:
Reproduction: exact browser steps and whether Playwright reproduced the issue.Evidence: console/network/runtime/layout/performance facts from Chrome DevTools.Root cause: file/path/symbol and why it caused the issue.Fix: what changed.Revalidation: Playwright and Chrome DevTools checks after the fix.Residual risks: unavailable environment, untested browsers, missing credentials, or flaky external dependency.