skill visual feedback

Engineering Community

Skill notes

Overview

Systematic approach to processing image-based UI/UX feedback, identifying visual issues, and implementing fixes. Core principle: Analyze image → Identify issues → Locate code → Fix systematically → Verify visually.

When to Use

Use this skill when user provides: Screenshots with UI/UX problems "[Image]" prefix with description of visual issues Complaints about "messy UI" or "hot mess UX" Button styling or layout issues with visual examples

Phase 1: Visual Analysis

When user provides image feedback: Step 1: Acknowledge and Examine Step 2: Categorize Issues Issue Type · Examples Styling · Colors, fonts, spacing, borders

Phase 2: Code Investigation

Step 1: Locate Relevant Components Use Glob to find component files: Use Grep to find specific elements: Step 2: Identify Styling System Step 3: Read Affected Files

Phase 3: Root Cause Analysis

Step 1: Identify Why Issue Exists Common root causes: Root Cause · Indicators Inconsistent styling · Multiple ways to style same element Missing design tokens · Hard-coded colors/spacing

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@nyldn · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1: Visual Analysis

When user provides image feedback: Step 1: Acknowledge and Examine Step 2: Categorize Issues Issue Type · Examples Styling · Colors, fonts, spacing, borders

02
Phase 2: Code Investigation

Step 1: Locate Relevant Components Use Glob to find component files: Use Grep to find specific elements: Step 2: Identify Styling System Step 3: Read Affected Files

03
Phase 3: Root Cause Analysis

Step 1: Identify Why Issue Exists Common root causes: Root Cause · Indicators Inconsistent styling · Multiple ways to style same element Missing design tokens · Hard-coded colors/spacing

04
Phase 4: Implementation

Step 1: Create Fix Plan For each identified issue: Step 2: Implement Fixes Apply fixes one at a time, using Edit tool: Step 3: Ensure Consistency

05
Phase 5: Verification

Step 1: Visual Verification Checklist Step 2: Request User Confirmation

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.