A workflow for checking a built website against automated project rules and its design. It combines scripts for checks such as linting, type checking, and builds with human review of visual match, semantics, responsiveness, and browser code size.

Use it to run the project's verification and build commands, fix failures, review designs in Figma, check responsive behaviour and motion choices, and report warnings or skipped checks clearly.

A passing script cannot detect every visible or usability problem, while a visual review can miss repeatable technical failures. Using both gives a fuller check before reporting the work as complete.

How textura-agency/ai-design-vault configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to textura-agency/ai-design-vault. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/textura-agency/ai-design-vault/main/.claude/skills/qa-verify/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/textura-agency/ai-design-vault

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/textura-agency/ai-design-vault/qa-verify/github.svg)](https://agentmods.dev/skills/textura-agency/ai-design-vault/qa-verify)

Your own site

<a href="https://agentmods.dev/skills/textura-agency/ai-design-vault/qa-verify"><img src="https://agentmods.dev/badge/skills/textura-agency/ai-design-vault/qa-verify/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/textura-agency/ai-design-vault/qa-verify"><img src="https://agentmods.dev/badge/skills/textura-agency/ai-design-vault/qa-verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 105 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,211 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 86% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00105	$0.01211
Opus 5.5	$0.00042	$0.00484
Sonnet 5.5	$0.00021	$0.00242
Haiku 4.5	$0.00011	$0.00121

Measured 23d ago against content hash a8beddc377b1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

qa-verify scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 23d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

86% identical to qa-verify — 109 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/skills/qa-verify/SKILL.md · 107 lines

How it starts

The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.

QA & verification

Two layers. The script decides what is decidable; you decide the rest. Never report "done" on the script alone — it cannot see a design.

Layer 1 — mechanical (always run first)

.claude/scripts/verify.sh                      # whole source root
.claude/scripts/verify.sh src/views/about.tsx  # scoped

Then the project's own gates — read them from .claude/stack.json, do not guess the package manager:

node -e 'const c=require("./.claude/stack.json").commands;console.log([c.lint,c.typecheck,c.build].filter(Boolean).join("\n"))'

Run each. Every FAIL must be fixed. WARNs are judgement calls: fix or justify in your summary, never silently ignore. SKIPs mean a check could not apply — if one is skipped because a stack.json path is null, that is a gap in the profile, not a pass.

Layer 2 — judgement checks

Work section by section. For each one:

Design fidelity (only when a design exists)

Re-fetch the Figma node — do not QA from memory or from your own earlier summary. get_design_context for values, get_screenshot for layout. Then compare:

Copy — character for character. Flag anything paraphrased, shortened or invented.
Layout — column count, flex direction, alignment, order, positioning.
Spacing — margins, padding, gaps against the design values.
Typography — size, weight, line-height, letter-spacing. Never assume a heading is bold; designs often use 400.
Colour — exact values, resolved through tokens rather than matched by eye.
Images — aspect ratio, crop, radius, overlap. No effects the design lacks.

If an image looks invisible or wrong, check the container first — an invented wrapper background is the usual cause, not the asset itself.

Tokens

Every colour/spacing/radius/type value resolves to a token.
New tokens follow the three-tier grammar and carry a comment naming their origin.
No literal reached the theme-binding layer or a Tier 2 token.
A value that had to be invented because the design has no token for it is flagged to the user for design review, not quietly added.

Read the full file on GitHub · 107 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

23d ago First seen · 107 lines · 105 tokens per session scan A a8beddc377b1

Subscribe to this mod's changes

qa-verify is a skill published in the GitHub repository textura-agency/ai-design-vault (25 stars, last pushed 2mo ago), licensed Unlicense. It adds 105 tokens to every session and 1,211 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to qa-verify, differing in 109 lines, and is treated as a copy.

Design and UX Testing

qa-verify next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
qa-verifytextura-agency/ai-design-vault	Skill	25	2mo ago	Unlicense	A	105	Claude Code
qa-test-plannerdavila7/claude-code-templates	Skill	33k	yesterday	MIT	A	34	Claude Code, Codex
design-qaXiaomiMiMo/MiMo-Code	Skill	14k	yesterday	MIT	A	68	Codex
ui-craft-checksOrkas-AI/Orkas	Skill	9.0k	today	MIT	A	5	Claude Code, Codex
healthtw93/Waza	Skill	7.5k	4d ago	MIT	A	40	Claude Code
hunttw93/Waza	Skill	7.5k	4d ago	MIT	A	33	Claude Code
critiqueplugin87/ux-ui-agent-skills	Skill	3.1k	10d ago	MIT	A	37	Claude Code

ai-design-vault: Skill for Claude Code