debug-frontend
Debug the Nuxt 3 admin UI using Playwright MCP for visual inspection, console error analysis, and network request tracing. Use when user says 'UI is broken', 'page not loading', 'frontend bug', 'console errors', 'API call failing in UI', 'component not rendering', 'blank page', 'verify my UI changes
Install
mkdir -p .claude/skills/debug-frontend && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14711" && unzip -o skill.zip -d .claude/skills/debug-frontend && rm skill.zipInstalls to .claude/skills/debug-frontend
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Debug the Nuxt 3 admin UI using Playwright MCP for visual inspection, console error analysis, and network request tracing. Use when user says 'UI is broken', 'page not loading', 'frontend bug', 'console errors', 'API call failing in UI', 'component not rendering', 'blank page', 'verify my UI changes', or 'check the admin interface'. Do NOT use for static code quality audits (use audit-frontend), backend agent debugging (use debug-agent), or bot platform issues (use debug-bot).About this skill
Frontend Debugging Assistant
Debug the Nuxt 3 admin interface visually. Issue description or page URL via $ARGUMENTS.
Prerequisites
The admin UI must be running at http://localhost:3333. If not running:
cd packages/web && pnpm dev
Step 1: Navigate to the Page
Use the Playwright MCP browser_navigate tool to open the page. Common entry points:
- Dashboard:
http://localhost:3333/en - Agents:
http://localhost:3333/en/service/agents - Processes:
http://localhost:3333/en/service/processes - Threads:
http://localhost:3333/en/service/threads - Knowledge:
http://localhost:3333/en/service/databases - Users:
http://localhost:3333/en/service/users - Roles:
http://localhost:3333/en/service/roles
Step 2: Capture Page State
Use these Playwright MCP tools to gather diagnostic information:
browser_snapshot: Get the accessibility tree (DOM structure, interactive elements)browser_take_screenshot: Visual capture of the current statebrowser_console_messageswithlevel: "error": Check for JavaScript errorsbrowser_network_requests: Inspect API calls (failed requests, wrong payloads)
Step 3: Diagnose Common Issues
API Errors (4xx/5xx)
- Check
browser_network_requestsfor failed API calls - Look at the request URL and response status
- Cross-reference with SDK functions in
packages/web/sdk/client/ - Check if the API server is running (
curl http://localhost:8000/api/v1/active/docs)
Rendering Issues
- Take a screenshot to see the visual state
- Use
browser_snapshotto check the DOM structure - Look for missing data (composable not returning data)
- Check if
StructuralColumnhasloading: true(blocks child rendering)
Auth/Redirect Issues
- Check if redirected to
/auth/login - Verify the OIDC plugin is configured:
packages/web/plugins/oidc-client.ts - Check
middleware/auth.global.tsfor route guard logic - In dev mode, fake auth should bypass OIDC
i18n Missing Keys
- Look for raw key paths displayed instead of translated text (e.g.,
agent.titleshown literally) - Check locale files:
packages/web/i18n/locales/en.yaml - Verify the key exists at the expected path
Component Not Updating
- Check Pinia-Colada query keys — mismatched keys prevent cache hits
- Verify
enabledflag on queries (must betrueor a reactive ref) - Check if mutation calls
queryCache.invalidateQueries()after success - Use
browser_evaluateto inspect Vue component state if needed
Step 4: Interact and Reproduce
Use Playwright MCP to interact with the UI:
browser_click: Click buttons, links, menu itemsbrowser_type: Fill form fieldsbrowser_fill_form: Fill multiple form fields at oncebrowser_select_option: Select dropdown valuesbrowser_press_key: Keyboard shortcuts (Escape, Enter, Tab)
Reproduce the issue step by step and capture screenshots at each stage.
Step 5: Trace to Source Code
Once the issue is identified:
- Find the page component:
packages/web/pages/service/{resource}/ - Find composables:
packages/web/composables/{resource}/ - Find child components:
packages/web/components/{Resource}/ - Check SDK types:
packages/web/sdk/client/
Step 6: Report
Provide a structured report with:
- What was observed: Screenshot + console errors + failed network requests
- Root cause: Which file and line is responsible
- Suggested fix: Specific code change to resolve the issue
Step 7: Verify Fix
After applying the suggested fix, re-run Steps 1-2 to confirm:
- Navigate to the same page with
browser_navigate - Take a new screenshot with
browser_take_screenshot - Check
browser_console_messagesfor remaining errors - Verify
browser_network_requestsshows successful API calls
Examples
/debug-frontend the agents page shows a blank table-- Navigate to agents page, check network requests for API failures, inspect DOM for missing data bindings/debug-frontend console errors on the dashboard-- Open dashboard, capture console errors, trace to source component/debug-frontend verify my changes to the roles page-- Navigate to roles page, take screenshot, check for regressions
Troubleshooting Quick Reference
| Symptom | Likely Cause | Where to Look |
|---|---|---|
| Blank page | JavaScript error blocking render | browser_console_messages with level "error" |
| Spinner never stops | API call hanging or query enabled flag is false | browser_network_requests + composable enabled prop |
| 401 on API calls | Auth not configured for dev | plugins/oidc-client.ts, check dev mode fake auth |
| Missing translations | i18n key not in locale file | i18n/locales/en.yaml, search for the raw key |
| Stale data after mutation | Missing queryCache.invalidateQueries() | Composable mutation onSuccess callback |
| Component not found | Auto-import name mismatch | Verify component file path matches Nuxt auto-import convention |