Visual Qa logo

Visual Qa

Community
dev-ik
visual-qa

Use when an implemented screen, screenshot, or UI change needs visual QA for spacing, alignment, wrapping, clipping, overlap, hierarchy, component states, or comparison with a supplied design reference. Skip backend-only changes.

Overview

Publisherdev-ik
Repositoryai-design-rules
Skill namevisual-qa
Stars
3
Forks
0
Bundled files
Instructions only
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.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by dev-ik on GitHub. Read the source before you install it.

Installation

Install the Visual Qa 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/dev-ik/ai-design-rules/tree/main/skills/visual-qa
  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/dev-ik/ai-design-rules.git /tmp/ai-design-rules
mkdir -p .claude/skills
cp -r /tmp/ai-design-rules/skills/visual-qa .claude/skills/visual-qa
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Visual Qa 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 Qa 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 Qa 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.

Visual QA

Review observed UI against the user's task, existing design system, and retrieved graph context. This execution skill complements design-reviewer, which owns the final traceability review.

Inputs and capabilities

Identify the screen, primary action, changed components, relevant states, target devices, and any supplied reference. Retrieve focused context with npx --no-install ai-design-context context --review "<graph ID or matching phrase>" --intent qa; read the returned research and rules. An arbitrary application path is not automatically a graph match.

Record which tools are actually available:

  • A browser tool or the project's existing Playwright setup for navigation, viewport changes, clicks, keyboard input, scrolling, DOM measurements, and screenshots.
  • An image-viewing tool and an image-capable model for inspecting captured pixels and references.
  • Source and DOM inspection for relating a visible issue to its implementation.

If a capability is unavailable, continue with the available evidence and mark the missing checks unverified. Skills do not install browser binaries, provision model vision, or enable MCP tools. A code-only review cannot establish rendered quality; a screenshot cannot establish keyboard or responsive behavior.

Browser and image loop

  1. Open the actual implementation. Record its URL or fixture path, browser, viewport in CSS pixels, theme, zoom, data, and state. Exercise the primary action and relevant default, loading, empty, error, success, and disabled states; mark inapplicable states with a reason.
  2. Check narrow and wide layouts with responsive-check. Open and close menus, dialogs, and sheets, scroll past sticky regions, and exercise keyboard focus with accessibility-check.
  3. Save viewport screenshots for geometry and separate full-page screenshots for long content. Use the project's evidence convention; otherwise create a dated review folder under output/playwright/. Record the steps that reproduce each capture.
  4. Open the captured images, not just their filenames. Inspect alignment, spacing consistency, typography, line breaks, clipped text, collisions, icon alignment, button/input sizing, content density, primary-action prominence, and state feedback. Confirm suspected geometry problems with DOM measurements where possible.
  5. If a design reference exists, compare matching viewport, state, theme, content, and scale. Record unmatched conditions instead of attributing every pixel difference to a defect. Without a reference, assess task clarity and existing tokens; do not invent a target composition from taste.
  6. For authorized fixes, make a focused patch, repeat the failed interaction, and recapture the same conditions. Run the project's relevant code checks. Preserve product logic and the existing UI stack.

Report contract

Lead with PASS, NEEDS WORK, or PARTIAL, scoped to the surfaces and states actually reviewed. PARTIAL means missing evidence prevents completing that scope. Separate observed defects from coverage gaps; a skipped check is not a confirmed product defect.

For each finding, include:

FieldRequired evidence
ID and severityStable review-local ID; Critical, Major, Minor, or Polish based on impact on the primary task.
Surface and conditionsScreen/component, viewport, data/state, and input method.
ReproductionActions another reviewer can repeat.
Observed / expectedWhat happened; applicable rule, pattern, reference, or explicit knowledge gap.
EvidenceScreenshot path and inspected region; DOM measurement or interaction observation when available.
Impact and fixUser consequence, focused correction, likely file/component when verified.
RetestOutcome and matching after-capture, or pending.

Finish with a coverage table: surface | viewport | state/input | evidence | checked/unverified/not applicable. List missing tools and any reference-comparison gaps. Do not infer a global pass from one desktop screenshot.

Graph anchors and tool references

  • CHECK-00001 / checklists/DESIGN_QA.md: state, responsive, accessibility, and evidence boundaries.
  • RULE-00008 / VIS-001: existing semantic tokens.
  • RULE-00014 / VIS-002: content and primary-action hierarchy.
  • RULE-00011 / PERF-001: loading-state layout stability.
  • Playwright screenshots and emulation describe capture and viewport capabilities, not proof that those tools are installed.

Frequently asked questions

What does the Visual Qa AI skill do?

Use when an implemented screen, screenshot, or UI change needs visual QA for spacing, alignment, wrapping, clipping, overlap, hierarchy, component states, or comparison with a supplied design reference. Skip backend-only changes.

Why use Visual Qa on TypingMind?

Because you install it once and use it with any model. Visual Qa 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 Qa in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/dev-ik/ai-design-rules/tree/main/skills/visual-qa. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Visual Qa?

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 Qa?

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

Is the Visual Qa AI skill free?

Yes. It is published on GitHub by dev-ik 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 👇