browser-feedback

Route browser click feedback to specialist design owners with evidence validation.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/vTRKA/supervibe --skill browser-feedback
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-feedback
Source: https://github.com/vTRKA/supervibe/tree/main/skills/browser-feedback
Command: npx skills add https://github.com/vTRKA/supervibe --skill browser-feedback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces confusion in AI-assisted UI changes by turning browser click feedback into a bounded, evidence-backed decision and handoff to the design/implementation owner.

Core Features & Use Cases

  • Real-time triage: Converts incoming browser-feedback context (prototype/mockup, selector/viewport, comment, suggested agent) into an actionable routing decision.
  • Evidence-driven validation: Verifies selector existence and prototype preview state before dispatching work and before claiming completion.
  • Durable resolution record: Writes a feedback-resolution artifact and updates feedback status (in_progress/resolved/rejected) while preserving required approvals.
  • Specialist routing by comment type: Routes visual/motion to creative-director and layout/a11y/copy to prototype-builder (with accessibility review when needed).
  • Anti-slop compliance: Produces required anti-slop reporting and uses a compact Anti-AI-Slop stamp for design-review/handoff evidence.

Quick Start

Use the browser-feedback system-reminder flow: when it appears with click-region context and the preview shows the feedback button, respond through the skill’s triage to get changes proposed and a confirmation prompt.

Frequently Asked Questions about browser-feedback

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

FAQPage Schema
How do I route real-time prototype feedback to the correct design owner?

To route real-time prototype feedback, the system reads a feedback queue entry containing selector, viewport, and comment data, verifies the selector in the preview HTML, and dispatches the packet to the correct specialist agent for resolution.

How does browser click feedback validation work for UI prototypes?

Browser click feedback validation works by verifying the target selector existence and prototype preview state before dispatching any work, ensuring evidence-backed decisions and preventing unverified design changes.

What is the best way to triage accessibility and layout issues in a mockup preview?

Triage of accessibility and layout issues routes comments directly to a prototype-builder agent, while visual and motion feedback routes to a creative-director, ensuring specialist handling of each design dimension.

How do I track the status of design triage decisions in a feedback workflow?

You track design triage decisions by writing a feedback-resolution artifact and updating a feedback-status.json file, which maintains durable records of in-progress, resolved, or rejected states.

What happens when evidence or approval signals are missing during UI prototype feedback?

When evidence, approval signals, or gates are missing during UI prototype feedback, the system fails closed with a BLOCKED status to prevent unverified changes and ensure compliance.

Can I use this browser feedback routing for copy and motion review in addition to layout?

Yes, you can use this routing for copy, motion, layout, visual, and accessibility review types, dispatching each category to specialized agents based on the comment packet contents.