Visual Diff Fix logo

Visual Diff Fix

Community
Jason904
visual-diff-fix

This skill should be used after visual-acceptance-review has generated fix-tasks.json. It applies precise visual fixes from structured diff tasks, preserves source-of-truth contracts, avoids redesign and unrelated refactors, validates each batch, and outputs resolved fix task reports.

Overview

PublisherJason904
Repositoryui-skill-lab
Skill namevisual-diff-fix
Stars
144
Forks
9
Bundled files
14
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 14 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by Jason904 on GitHub. Read the source before you install it.

Installation

Install the Visual Diff Fix AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Jason904/ui-skill-lab/tree/main/.codex/skills/visual-diff-fix
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Jason904/ui-skill-lab.git /tmp/ui-skill-lab
mkdir -p .claude/skills
cp -r /tmp/ui-skill-lab/.codex/skills/visual-diff-fix .claude/skills/visual-diff-fix
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Visual Diff Fix in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Visual Diff Fix on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Visual Diff Fix is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Version: 2.0.0

visual-diff-fix

Apply precise visual fixes from fix-tasks.json.

This skill only fixes listed visual diff tasks. It does not redesign, does not rewrite visual specs, and does not expand scope.

Trigger Conditions

Use this skill when:

  • 07_validation/visual_acceptance/fix-tasks.json exists
  • visual-acceptance-review returned Fail or Conditional Pass
  • user asks to fix visual differences
  • user asks Codex to apply visual diff fixes

Required Inputs

text
ui/07_validation/visual_acceptance/
  fix-tasks.json
  comparison-report.md
  acceptance-summary.md
  region-diffs/

ui/03_visual_spec/
  visual-analysis.md
  layout-spec.md
  component-tree.md
  DESIGN.md
  tokens.json
  implementation-risks.md
  human-review-needed.md

ui/04_visual_spec_review/
  spec-review-report.md
  conflict-log.md
  revised-files-needed.md

ui/05_design_system/
  MASTER.md
  pages/target-page.md
  ux-checklist.md
  component-state-spec.md
  responsive-spec.md
  accessibility-spec.md
  implementation-constraints.md

Recommended:

text
ui/06_spec_review/
  compliance-report.md
  violation-list.json

package.json
playwright.config.*
src/
app/
components/
styles/

Source of Truth

  1. fix-tasks.json
  2. reference.png
  3. visual-analysis.md / UI Type Classification
  4. layout-spec.md / Layout Paradigm
  5. implementation-risks.md / Asset Strategy
  6. component-tree.md
  7. tokens.json
  8. 05_design_system/
  9. Implementation code

Main Workflow

  1. Run preflight gates.
  2. Load and validate fix-tasks.json.
  3. Sort tasks by priority, blocking, strictness, source, and dependency.
  4. Group related tasks by root cause and file.
  5. Apply one small batch of fixes.
  6. Run available validation commands.
  7. Capture screenshot if available.
  8. Update resolved task status.
  9. Repeat until high/medium blocking issues are fixed or convergence is reached.
  10. Write outputs under 08_diff_fix/.

Hard Rules

  • Only fix tasks listed in fix-tasks.json.
  • Do not redesign.
  • Do not refactor unrelated code.
  • Do not introduce new visual style.
  • Do not create new tokens unless task explicitly requires it and source-of-truth allows it.
  • Do not overwrite screenshot-derived required tokens without impact analysis.
  • Do not modify visual spec files.
  • Do not modify design system files.
  • Do not modify OpenSpec files.
  • If a task is review-required, do not auto-fix it.
  • If a task requires UI Type or Asset Strategy restoration, do not substitute with local spacing/color tweaks.
  • If a fix causes regression, rollback or mark caused-regression.

Output

Write:

text
08_diff_fix/
  fix-report.md
  fix-tasks.resolved.json
  convergence-report.md
  escalation-report.md
  screenshots/
    after-batch-1.png
    after-batch-2.png
    final.png
  validation/
    lint.log
    build.log
    test.log
    screenshot.log

convergence-report.md and escalation-report.md are only required when applicable.

Supporting Files

Read these references directly:

  • references/fix-workflow.md
  • references/preflight-gates.md
  • references/prioritization-rules.md
  • references/fix-handlers.md
  • references/token-protection-rules.md
  • references/validation-rules.md
  • references/convergence-rules.md
  • references/fix-task-schema.md
  • references/output-files.md

Examples:

  • examples/fix-tasks.example.json
  • examples/fix-tasks.resolved.example.json
  • examples/fix-report.example.md
  • examples/convergence-report.example.md
  • examples/escalation-report.example.md

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Visual Diff Fix AI skill do?

This skill should be used after visual-acceptance-review has generated fix-tasks.json. It applies precise visual fixes from structured diff tasks, preserves source-of-truth contracts, avoids redesign and unrelated refactors, validates each batch, and outputs resolved fix task reports.

Why use Visual Diff Fix on TypingMind?

Because you install it once and use it with any model. Visual Diff Fix is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Visual Diff Fix in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Jason904/ui-skill-lab/tree/main/.codex/skills/visual-diff-fix. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Visual Diff Fix?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Visual Diff Fix?

As many as you like. As long as a model supports skills, you can use Visual Diff Fix with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Visual Diff Fix AI skill free?

Yes. It is published on GitHub by Jason904 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇