browser-repro-ui-triage

Reproduce browser UI bugs and triage root causes across technical layers.

Updated Aug 27, 2026

Search Tags:#workflow #debugging #evidence #reproduce #browser #triage #ui-bug

Ready to run

npx skills add https://github.com/ringlochid/Homura-WorkSpace --skill browser-repro-ui-triage

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: browser-repro-ui-triage
Source: https://github.com/ringlochid/Homura-WorkSpace/tree/main/skills/browser-repro-ui-triage
Command: npx skills add https://github.com/ringlochid/Homura-WorkSpace --skill browser-repro-ui-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reproduce frontend/UI bugs in-browser and triage root causes across UI code, client state, auth/session, network, API contracts, backend behavior, and deployment/config drift. It serves as the first-pass tool for visual glitches, broken interactions, or browser-visible symptoms when the root cause is unclear, and is not intended for backend-first incidents or repro-pack packaging.

Core Features & Use Cases

Systematic repro of browser UI issues with step-by-step guidance
Evidence collection guidance (screenshots, console logs, network traces)
Layer pinning and routing to the correct fix skill
Visual-triage guidance and DevTools checks

Quick Start

Reproduce the reported UI issue in a browser, capture a minimal repro, and route to the correct fix bucket.

Frequently Asked Questions about browser-repro-ui-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I systematically reproduce and triage a browser UI bug with an unclear root cause?▼

To triage a browser UI bug, systematically reproduce the issue in-browser, capture deterministic repro steps, collect DevTools evidence like console logs and network traces, and pin the responsible layer for routing to the correct fix.

What is the best way to find out if a visual glitch is caused by client state or an API contract issue?▼

Finding if a visual glitch is caused by client state or an API contract issue requires in-browser triage that captures network traces and console logs to isolate the symptom across UI, client state, auth/session, network, API contract, backend behavior, or deployment/config drift.

How do I capture deterministic repro steps and browser evidence for a broken frontend interaction?▼

Capture deterministic repro steps and browser evidence for a broken frontend interaction by reproducing the issue systematically, documenting exact user actions, and recording visual screenshots, console logs, and network traces for diagnostic context.

Can I use this triage process for backend-first incidents and deployment config drift?▼

This triage process is not intended for backend-first incidents or repro-pack packaging, but it does diagnose deployment/config drift when it manifests as a browser-visible symptom with an unclear root cause before escalation.

When should I not use browser UI triage for troubleshooting blank screens?▼

You should not use browser UI triage for blank screens when the root cause is already known as a backend-first incident, or when you need repro-pack packaging instead of first-pass visual triage and layer routing.

What diagnostic data do I need to route a blank screen symptom to the correct fix?▼

Routing a blank screen symptom to the correct fix requires diagnostic data including deterministic repro steps, browser evidence such as screenshots and network traces, and explicit context to identify whether the UI, auth/session, or network layer is responsible.