skill-visual-feedback

Analyzes screenshot-based UI feedback to locate and fix visual issues in frontend code.

Updated Aug 15, 2026
One-click install
npx skills add https://github.com/GongYuanCaiJi/dsh-claude-octopus --skill skill-visual-feedback-gongyuancaiji
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: skill-visual-feedback
Source: https://github.com/GongYuanCaiJi/dsh-claude-octopus/tree/main/.claude/skills/skill-visual-feedback
Command: npx skills add https://github.com/GongYuanCaiJi/dsh-claude-octopus --skill skill-visual-feedback-gongyuancaiji

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Users often report UI bugs through screenshots rather than precise technical descriptions, leaving developers to guess which components, styles, or states are broken. This Skill turns image-based feedback into a systematic workflow: analyze the screenshot, categorize the visual issues, locate the responsible code, fix it consistently, and verify the result. ## Core Features & Use Cases - Structured Visual Analysis: Categorizes observed problems into styling, layout, component, state, and consistency issues before touching any code. - Systematic Code Investigation: Uses Glob and Grep patterns to locate affected components, detect the styling system in use (Tailwind, CSS Modules, styled-components, design systems), and identify root causes. - Scoped Fix Planning: Offers targeted, systematic, or design-system-level fix options so "fix this everywhere" requests are handled across all instances, not just one. - Use Case: A user shares a screenshot saying "these button styles need to be fixed everywhere." The Skill identifies the inconsistency, finds every button instance across the codebase, updates them to the correct design-system variant, and produces a verification checklist covering responsive breakpoints and interaction states. ## Quick Start Share a screenshot of the UI problem with a short description, for example: this screenshot shows the settings page using text inputs where dropdowns should appear, please fix it.

Frequently Asked Questions about skill-visual-feedback

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

FAQPage Schema
How do I fix UI bugs reported through screenshots?▼

Analyze the screenshot to list observed visual problems, categorize them by type (styling, layout, component, state), then locate the responsible component files with search patterns. Fix each issue systematically and verify against the original screenshot.

How to fix inconsistent button styles across an entire app?▼

Search the codebase for all button instances using Grep patterns, identify the design-system button component, then either update the base component or migrate every instance to the correct variant. Verify consistency across all pages afterward.

Does this approach work with Tailwind CSS and styled-components?▼

Yes, the workflow includes a step to detect the styling approach in use, covering Tailwind CSS, CSS Modules, styled-components, Emotion, plain CSS, and design systems like Material-UI, Ant Design, and Chakra UI.

When should visual feedback not trigger a code fix?▼

Text-only feedback without visual context, pure feature requests, backend or performance issues, and code-only bugs fall outside this workflow. Those cases need debugging, feature planning, or performance tooling instead.

Why do visual fixes sometimes break other parts of the UI?▼

Fixes break other areas when styles are changed with !important overrides, hard-coded values instead of design tokens, or when only one instance is fixed while the pattern exists elsewhere. Scoping the fix before implementation prevents this.