AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Frontend Debugging Workflow

skill-eric861129-workflow-skill-router-frontend-debugging-workflow · by eric861129

Use when investigating rendered frontend bugs, browser-only failures, broken interactions, visual regressions, hydration issues, or UI behavior that needs browser reproduction and regression coverage.

No reviews yet
0 installs
39 views
0.0% view→install

Install

$ agentstack add skill-eric861129-workflow-skill-router-frontend-debugging-workflow

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-eric861129-workflow-skill-router-frontend-debugging-workflow)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Frontend Debugging Workflow? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Frontend Debugging Workflow

Use this skill when the failure is visible or interactive in a browser.

Workflow

  1. Reproduce the symptom in the browser.
  2. Record the URL, viewport, user action, expected behavior, and actual behavior.
  3. Check console, network, DOM state, and application state.
  4. Trace the symptom back to source code.
  5. Fix the smallest cause.
  6. Add a regression check with Playwright or the repo's test framework when useful.
  7. Re-run browser verification.

Browser vs Playwright

  • Use browser inspection first when the issue is not understood.
  • Use Playwright after the scenario is stable enough to automate.
  • Use existing Chrome state only when login, cookies, extensions, or current tabs matter.

Common Supporting Skills

  • browser:control-in-app-browser for local visual reproduction.
  • playwright for scripted regression.
  • systematic-debugging for causal investigation.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.