feat(ui-debugging): UI debugging skill — fix bugs with exact browser checks#131
Open
shubh24 wants to merge 1 commit into
Open
feat(ui-debugging): UI debugging skill — fix bugs with exact browser checks#131shubh24 wants to merge 1 commit into
shubh24 wants to merge 1 commit into
Conversation
Reproduce with a source-blind probe, apply a minimal fix, verify with a
page-side check that returns {passed, measurements, passCondition,
instructionToFixer} and feed the JSON back on failure. Benchmarked at
7/18 -> 11-12/18 over one-shot fixing on an 18-bug suite (ui-debug-bench),
with zero re-browsing during repair. Complements ui-test (finding bugs)
with the fixing half.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
A new
ui-debuggingskill: fix user-reported UI bugs by treating the browser as a diagnostic instrument, not an explorer.The loop: reproduce with a source-blind browser probe → fix (smallest credible change) → verify with an exact page-side check returning
{passed, measurements, passCondition, instructionToFixer}→ on failure, feed the check's raw JSON back into the next fix attempt. No re-browsing during repair.Why
Benchmarked on an 18-bug suite (6 vibe-coded React apps, planted bugs, browse CLI + claude-opus-4-8):
The bugs recovered at attempt 2 are ones where the check named the exact wrong element (e.g. selector matching a hidden desktop nav before the mobile menu) — evidence that sharper assertions, not more browsing, convert failed fixes.
Relationship to existing skills
ui-testfinds unknown bugs in changed UI;ui-debuggingfixes a reported bug and proves the fix. The skill cross-references ui-test.--remotefor Browserbase sessions on deployed sites, or any tool withpage.evaluate.🤖 Generated with Claude Code
Note
Low Risk
Documentation-only addition (skill markdown and README); no application or auth/runtime code changes.
Overview
Adds a new
ui-debuggingagent skill that documents a reproduce → fix → verify loop for user-reported UI bugs, centered on source-blind browser probes and page-side check contracts (passed, measurements,passCondition,instructionToFixer) with failed-check JSON fed into the next fix attempt instead of more browsing.The skill includes
browseCLI examples (local and--remote), React input probing notes, anti-patterns, and benchmark provenance; it is positioned inREADME.mdnext toui-test(find bugs vs fix reported bugs).LICENSE.txt(MIT) is added underskills/ui-debugging/.Reviewed by Cursor Bugbot for commit eeb2719. Bugbot is set up for automated code reviews on this repo. Configure here.