# Visual Feedback > Use when the user wants to give feedback on a document, concept, design, plan, or report section by section - e.g. asks for a "Review-Seite", "Feedback-Seite", a kommentierbare HTML-Version, "Feedback zu jedem Abschnitt/jeder Box/jedem Element", comment pins in SVG diagrams, or wants to annotate a deliverable and paste the collected feedback back into the chat. Also when retrofitting an existing HTML page so every element accepts comments. - Skill: `okuegow/visual-feedback` (Agent Skill, multi-file: 11 files) - Install (CLI): `npx skillmds@latest add okuegow/visual-feedback` - Raw SKILL.md: https://api.skillmd.com/api/skills/okuegow/visual-feedback/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Web & Frontend - Author: okuegow (https://skillmd.com/u/okuegow) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/okuegow/visual-feedback --- # Visual Feedback ## Overview Turn any deliverable (concept, report, design, plan) into ONE self-contained HTML review page where every meaningful element is an inline comment point. Each comment can carry a category (Question/Error/Change/Praise) and priority (Must/Optional). Comments persist in localStorage, and the user exports them as structured markdown WITH a JSON attachment (clipboard or .md file) to paste back into the chat. The chat paste-back closes the loop: the agent maps each comment to its target `id` and works the feedback in. Built for **multiple rounds**: when you produce a follow-up version you embed a round manifest that records, per prior comment, what you did with it (addressed / declined / deferred / noted). Resolved points move into a collapsed history and stop reappearing as open fields; the page builds a per-version changelog and marks changed sections. See "Iterating across versions". The UI defaults to English and carries a small EN/DE toggle in the toolbar; the toggle switches every visible string AND the exported markdown, and persists in localStorage under `fb:lang`. Category/priority are stored as stable, language- independent ids (`frage/fehler/aenderung/lob`, `muss/optional`); only their display labels translate, so the JSON block reads the same in either language. **Template:** copy and adapt `template.html` in this skill directory. It contains the complete widget CSS/JS and one example of every target type. Do not rebuild the mechanics from scratch - that is how past pages drifted into incompatible variants. The script builds its own toolbar, toast and preview overlay, so retrofitting an existing HTML page = paste the template's widget CSS block and complete `