Web Interface Guidelines Reviewer
vercel-labs/openreview
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…
Use before declaring any design work complete, fixed, or ready — requires running verification and confirming output before making any success claims.
Install Verification Before Shipping
$ npx skills add Owl-Listener/designpowers --skill verification-before-shipping -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/designpowers verification-before-shipping --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/verification-before-shipping .claude/skills/verification-before-shipping && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "verification-before-shipping" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/verification-before-shipping into .claude/skills/verification-before-shipping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verification-before-shipping", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Owl-Listener/designpowers/tree/main/skills/verification-before-shippingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Owl-Listener/designpowers --skill verification-before-shipping -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/designpowers verification-before-shipping --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/verification-before-shipping .agents/skills/verification-before-shipping && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "verification-before-shipping" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/verification-before-shipping into .agents/skills/verification-before-shipping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verification-before-shipping", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/designpowers --skill verification-before-shipping -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/designpowers verification-before-shipping --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/verification-before-shipping .cursor/skills/verification-before-shipping && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "verification-before-shipping" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/verification-before-shipping into .cursor/skills/verification-before-shipping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verification-before-shipping", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Owl-Listener/designpowers.git --path skills/verification-before-shipping--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Owl-Listener/designpowers --skill verification-before-shipping -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/designpowers verification-before-shipping --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/verification-before-shipping .gemini/skills/verification-before-shipping && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "verification-before-shipping" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/verification-before-shipping into .gemini/skills/verification-before-shipping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verification-before-shipping", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Owl-Listener/designpowers verification-before-shippingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Owl-Listener/designpowers --skill verification-before-shipping -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/verification-before-shipping .github/skills/verification-before-shipping && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "verification-before-shipping" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/verification-before-shipping into .github/skills/verification-before-shipping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verification-before-shipping", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/designpowers --skill verification-before-shipping -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Owl-Listener/designpowers verification-before-shipping --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designpowers.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/verification-before-shipping .opencode/skills/verification-before-shipping && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "verification-before-shipping" agent skill from https://github.com/Owl-Listener/designpowers/tree/main/skills/verification-before-shipping into .opencode/skills/verification-before-shipping/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verification-before-shipping", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
verification-before-shipping- GitHub stars
- 251
- Token cost
- ~1.1k tokens
- SKILL.md length
- 448 words
- Files
- 1
- Skills in repo
- 33
- Repo updated
- First seen
- Licence
- MIT
At a glance
Use before declaring any design work complete, fixed, or ready — requires running verification and confirming output before making any success claims.
- Works in 7 steps: Check Against the Plan → Check Against the Brief → Accessibility Verification → …
- Tasks that involve Accessibility
- SKILL.md covers The Rule, When to Use, Process and Integration, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Verification Before Shipping is an agent skill from Owl-Listener/designpowers. Use before declaring any design work complete, fixed, or ready — requires running verification and confirming output before making any success claims. Evidence before assertions, always
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design, covering Accessibility. The repository describes itself as: An agent design team you control: 10 agents that run an inclusive design process while you direct. The licence is MIT.
When your agent uses it
- Tasks that involve Accessibility
Example prompts
- “/verification-before-shipping”
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit cb00757. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Verification Before Shipping loads about 1.1k tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 448 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Owl-Listener/designpowers at commit cb00757, republished under its MIT licence (© Owl-Listener). 448 words, ~1,061 tokens.
Download SKILL.mdSave it as
.claude/skills/verification-before-shipping/SKILL.md (or your agent's skills folder).- name
- verification-before-shipping
- description
- Use before declaring any design work complete, fixed, or ready — requires running verification and confirming output before making any success claims. Evidence before assertions, always
Verification Before Shipping
Do not say it is done until you have proof. This skill prevents the most common failure mode in design work — declaring completion based on intent rather than evidence.
The Rule
NEVER claim work is complete, fixed, passing, or ready without running verification and confirming the output. "I believe this works" is not verification. "I ran these checks and here are the results" is.
When to Use
- Before declaring a design task complete
- Before moving from one phase to the next
- Before handoff to engineering
- Before creating a PR or committing design artefacts
- Any time you are about to say "done"
Process
Step 1: Check Against the Plan
If a design plan exists:
- Every task in the plan is marked complete
- Every verification criterion in the plan has been met
- No tasks were skipped or deferred without explicit user approval
Step 2: Check Against the Brief
Reference the design brief:
- The stated problem is addressed
- All identified personas are served
- Success criteria are met or measurable
- Nothing in "out of scope" crept into scope (and vice versa)
Step 3: Accessibility Verification
Run — do not guess:
If code exists:
- Automated accessibility scan (axe-core, Lighthouse, or equivalent) — report results
- Keyboard navigation test — report results
- Screen reader test (at minimum, check heading structure and form labels)
- Zoom to 200% — report results
- Check prefers-reduced-motion behaviour — report results
If design artefacts only:
- Contrast ratios verified with a tool (not by eye)
- Touch targets measured (not estimated)
- Heading hierarchy documented
- All states designed (not just the happy path)
Show full SKILL.md (193 more words)Show less
Step 4: Content Verification
- All placeholder text has been replaced with real content
- Error messages are written (not "TODO")
- Alt text is present for all images
- Labels are specific and descriptive
Step 5: Cross-Reference Personas
For each persona from the inclusive-personas phase:
- Could [Persona 1] complete the primary task? How?
- Could [Persona 2] complete the primary task? How?
- Could [Edge Case Persona] complete the primary task? What barriers remain?
Step 6: Check Design Debt
Before declaring the project shippable, review the Design Debt Register in design-state.md:
- All Critical and Major items are Resolved (not just Open or Escalated)
- Any Escalated items have been addressed or consciously Accepted by the user
- Open Minor items have been reviewed — the user knows what debt ships with this release
- Accessibility debt items have explicit user acknowledgement if Accepted
Step 7: Report
Present verification results to the user:
## Verification Report: [Feature/Task]
**Date:** [YYYY-MM-DD]
### Plan Completion
[All tasks complete / X tasks remaining]
### Brief Alignment
[Aligned / Gaps identified]
### Accessibility Results
- Automated scan: [Pass/Fail — specific issues]
- Keyboard: [Pass/Fail — specific issues]
- Screen reader: [Pass/Fail — specific issues]
- Zoom: [Pass/Fail — specific issues]
- Motion: [Pass/Fail — specific issues]
### Content Status
[Complete / Gaps identified]
### Persona Walkthrough
[Summary of persona-by-persona evaluation]
### Design Debt Status
- Open items shipping with this release: [count]
- Escalated items: [count] — [resolved/accepted]
- Accessibility debt accepted: [count] — [summary]
- Oldest unresolved: [DD-XXX] from [date]
### Verdict
[Ready to ship / Issues to resolve first]Integration
- Called by: Before any completion claim
- Follows:
designpowers-critique,design-handoff - Blocks: Completion claims, PR creation, merge decisions
The Iron Law
If you cannot produce evidence that the design works for the identified personas — including those at the margins of the ability spectrum — it is not done. Go back and verify.
© Owl-Listener, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/verification-before-shipping of Owl-Listener/designpowers.
Open the folder on GitHubat commit cb00757
Compare with similar skills
Verification Before Shipping next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Verification Before Shipping this skillOwl-Listener/designpowers | 251 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Web Interface Guidelines Reviewervercel-labs/openreview | 1.7k | 97 repos | ~308 | Automated safety check: Pass | None | |
| Accessibility Reviewmarkmead/hyperui | 12k | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Web Animation DesignbaptisteArno/typebot.io | 11k | 2 repos | ~2.7k | Automated safety check: Pass | Custom licence | |
| Accessibility Fixeribelick/ui-skills | 9.6k | 4 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Wcag Audit PatternsvmDeshpande/ai-agent-automation | 178 | 11 repos | ~610 | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Accessibility Review
markmead/hyperui
Run a WCAG 2.1 AA accessibility audit on a design or page. An agent skill from markmead/hyperui.
Web Animation Design
baptisteArno/typebot.io
Guides easing, timing and animation choices for UI motion, based on a web animation course, and reviews existing animations in a before-and-after table.
Accessibility Fixer
ibelick/ui-skills
Audits and fixes HTML accessibility problems such as ARIA labels, keyboard navigation, focus management, contrast and form errors with minimal changes.
Wcag Audit Patterns
vmDeshpande/ai-agent-automation
Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance.
Baseline UI
ibelick/ui-skills
Applies a fixed set of UI rules for stack, components, interaction, animation, typography and layout, or reviews a file against them with concrete fixes.
More from Owl-Listener/designpowers
All 33 skills in this repoAdaptive Interfaces
Owl-Listener/designpowers
A skill your agent uses when designing for user preferences — motion sensitivity, contrast needs, colour schemes, text sizing, information density, or any interface behaviour that should adapt to…
Design Debate
Owl-Listener/designpowers
A skill your agent uses when a design direction is uncertain, when the team could go multiple ways, or when the user wants to see competing approaches argued before committing — orchestrates…
Design Debt Tracker
Owl-Listener/designpowers
A skill your agent uses when critique or review produces deferred findings, when checking accumulated design compromises, or when deciding what to address in the next iteration.
Design Discovery
Owl-Listener/designpowers
You MUST use this before any creative or design work — building features, creating components, designing interfaces, modifying user-facing behaviour.
Design Handoff
Owl-Listener/designpowers
A skill your agent uses when design work is complete and needs to be communicated to engineering — creates specifications, documents rationale, accessibility requirements, and interaction details in…
Design Review
Owl-Listener/designpowers
A skill your agent uses when the user wants to evaluate something that ALREADY EXISTS rather than build something new — "review this", "audit this screen", "what's wrong with this page", "is this…
Related
Categories
Questions about Verification Before Shipping
What does Verification Before Shipping do?
Use before declaring any design work complete, fixed, or ready — requires running verification and confirming output before making any success claims. Verification Before Shipping is an agent skill from Owl-Listener/designpowers. Use before declaring any design work complete, fixed, or ready — requires running verification and confirming output before making any success claims.
When should I use Verification Before Shipping?
Verification Before Shipping fits situations like: tasks that involve Accessibility.
How do I install Verification Before Shipping in Claude Code?
Run `npx skills add Owl-Listener/designpowers --skill verification-before-shipping -a claude-code`. Or copy the skill folder (skills/verification-before-shipping in Owl-Listener/designpowers) into .claude/skills/verification-before-shipping in your project. Claude Code loads it when a task matches its description.
How do I install Verification Before Shipping in Codex?
Run `npx skills add Owl-Listener/designpowers --skill verification-before-shipping -a codex`. Or copy the skill folder (skills/verification-before-shipping in Owl-Listener/designpowers) into .agents/skills/verification-before-shipping in your project. Codex loads it when a task matches its description.
Can I use Verification Before Shipping in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Owl-Listener/designpowers --skill verification-before-shipping -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verification-before-shipping, .gemini/skills/verification-before-shipping, .github/skills/verification-before-shipping and .opencode/skills/verification-before-shipping in your project.
What does Verification Before Shipping need to run?
SKILL.md names no scripts, command-line tools or credentials: Verification Before Shipping is instructions for the agent only.
Does Verification Before Shipping access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Verification Before Shipping safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Verification Before Shipping use?
Verification Before Shipping is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Verification Before Shipping use?
About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Verification Before Shipping?
Skills that share tags, products or a category with Verification Before Shipping: Web Interface Guidelines Reviewer (vercel-labs/openreview, 1.7k stars), Accessibility Review (markmead/hyperui, 12k stars), Web Animation Design (baptisteArno/typebot.io, 11k stars) and Accessibility Fixer (ibelick/ui-skills, 9.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Verification Before Shipping?
Owl-Listener (a GitHub user) maintains it in Owl-Listener/designpowers, which has 251 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on June 23, 2026.
Source: Owl-Listener/designpowers on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.