Agent skill

UI Testing

by alinaqi in alinaqi/maggy

Visual testing - catch invisible buttons, broken layouts, contrast

MITAuto-check passedFrontend & Design

Install UI Testing

skills CLI
$ npx skills add alinaqi/maggy --skill ui-testing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install alinaqi/maggy ui-testing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/alinaqi/maggy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ui-testing .claude/skills/ui-testing && rm -rf skills-src

Use ~/.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/

Facts

Skill name
ui-testing
GitHub stars
707
Token cost
~1.1k tokens
SKILL.md length
107 words
Files
1
Skills in repo
71
Repo updated
First seen
Licence
MIT

At a glance

Visual testing - catch invisible buttons, broken layouts, contrast

  • Tasks that involve Visual regression testing
  • SKILL.md covers Purpose, Pre-Flight Checklist, Quick Contrast Check and Common Fixes, plus 2 more sections
  • Calls npm

What it does

UI Testing is an agent skill from alinaqi/maggy. Visual testing - catch invisible buttons, broken layouts, contrast

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 Visual regression testing. The repository describes itself as: What started as an opinionated Claude Code setup kit is now an autonomous AI engineering command center. The licence is MIT.

When your agent uses it

  • Tasks that involve Visual regression testing

Example prompts

  • “/ui-testing”

Requirements

  • Node.js

What it can do on your machine

Read from SKILL.md and the folder at commit 72a456e. 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

    Shell commands in SKILL.md call:

    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • webaim.org
    • coolors.co

    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

UI Testing loads about 1.1k tokens when it runs. Until then it costs about 19 tokens; SKILL.md has 107 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~19
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

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 alinaqi/maggy at commit 72a456e, republished under its MIT licence (© alinaqi). 107 words, ~1,090 tokens.

Download SKILL.mdSave it as .claude/skills/ui-testing/SKILL.md (or your agent's skills folder).
name
ui-testing
description
Visual testing - catch invisible buttons, broken layouts, contrast
when-to-use
When writing visual or accessibility tests for UI components
user-invocable
false
paths
**/*.test.tsx, **/*.spec.tsx, **/*.stories.*
effort
medium

UI Verification Skill

Load with: ui-web.md or ui-mobile.md

Purpose

Quick verification that generated UI meets accessibility standards. Run these checks after creating any new UI components.


Pre-Flight Checklist

Before Shipping ANY UI:
markdown
## Visibility Check
- [ ] All buttons have visible background OR border
- [ ] No text is same color as its background
- [ ] All text meets 4.5:1 contrast ratio
- [ ] Ghost/text buttons have visible borders

## Touch/Click Targets
- [ ] All buttons are minimum 44px height
- [ ] Icon buttons are minimum 44x44px
- [ ] Adequate spacing between clickable elements

## States
- [ ] Hover states visible (web)
- [ ] Pressed states visible (mobile)
- [ ] Focus rings on keyboard navigation
- [ ] Disabled states visually distinct (opacity 0.5)
- [ ] Loading states show indicators

## Dark Mode (if applicable)
- [ ] Text readable on dark backgrounds
- [ ] Borders visible in dark mode
- [ ] No gray-400 text on dark backgrounds

## Responsive (web)
- [ ] No horizontal scroll on mobile (320px)
- [ ] Content readable at all breakpoints
- [ ] Touch targets adequate on mobile

Quick Contrast Check

Use Browser DevTools
1. Right-click element → Inspect
2. In Styles panel, click on color value
3. Look for contrast ratio display
4. Must show ✓ for AA compliance (4.5:1 for text)
Online Tools
Tailwind Safe Combinations
LIGHT MODE (on white bg):
✓ text-gray-900  (#111827) = 16:1
✓ text-gray-800  (#1F2937) = 12:1
✓ text-gray-700  (#374151) = 9:1
✓ text-gray-600  (#4B5563) = 6:1
✗ text-gray-500  (#6B7280) = 4.6:1 (barely)
✗ text-gray-400  (#9CA3AF) = 2.6:1 (FAILS)

DARK MODE (on gray-900 bg):
✓ text-white     (#FFFFFF) = 16:1
✓ text-gray-100  (#F3F4F6) = 13:1
✓ text-gray-200  (#E5E7EB) = 11:1
✓ text-gray-300  (#D1D5DB) = 8:1
✗ text-gray-400  (#9CA3AF) = 5:1 (barely)
✗ text-gray-500  (#6B7280) = 3:1 (FAILS)

Common Fixes

Invisible Button
tsx
// PROBLEM: No visible boundary
<button className="text-gray-500">Click</button>

// FIX: Add background OR border
<button className="bg-gray-100 text-gray-900 px-4 py-3 rounded-lg">
  Click
</button>
// OR
<button className="border border-gray-300 text-gray-700 px-4 py-3 rounded-lg">
  Click
</button>
Low Contrast Text
tsx
// PROBLEM: Light gray on white
<p className="text-gray-400">Secondary text</p>

// FIX: Use darker gray
<p className="text-gray-600">Secondary text</p>
Missing Focus State
tsx
// PROBLEM: Focus removed without replacement
<button className="outline-none">Submit</button>

// FIX: Add visible focus ring
<button className="outline-none focus-visible:ring-2 focus-visible:ring-blue-500 focus-visible:ring-offset-2">
  Submit
</button>
Small Touch Target
tsx
// PROBLEM: Too small for fingers
<button className="p-1 text-sm">×</button>

// FIX: Minimum 44px
<button className="w-11 h-11 flex items-center justify-center">×</button>
Dark Mode Broken
tsx
// PROBLEM: Same colors in both modes
<p className="text-gray-400">Text</p>

// FIX: Adjust for dark mode
<p className="text-gray-600 dark:text-gray-300">Text</p>

Automated Checks (Optional)

ESLint Plugin
bash
npm install -D eslint-plugin-jsx-a11y
json
// .eslintrc
{
  "extends": ["plugin:jsx-a11y/recommended"]
}
Playwright Quick Test
typescript
// e2e/accessibility.spec.ts
import { test, expect } from '@playwright/test';
import AxeBuilder from '@axe-core/playwright';

test('no accessibility violations', async ({ page }) => {
  await page.goto('/');
  const results = await new AxeBuilder({ page }).analyze();
  expect(results.violations).toEqual([]);
});

When to Use Full Testing

Add comprehensive visual testing (Playwright screenshots, Storybook) when:

  • Building a component library
  • Multiple developers on UI
  • Frequent UI changes
  • Design system enforcement needed

For solo projects or MVPs, the checklist above is sufficient.

© alinaqi, 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/ui-testing of alinaqi/maggy.

Open the folder on GitHubat commit 72a456e

Compare with similar skills

UI Testing 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.

UI Testing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
UI Testing this skillalinaqi/maggy707—~1.1kAutomated safety check: PassMIT
Vrtmarigold-ui/marigold146—~787Automated safety check: PassMIT
Visual Acceptance Reviewhuiliyi37/Tianshu-harness1.1k—~601Automated safety check: PassApache-2.0
Component CSS Modules MigrationClickHouse/click-ui135—~7.7kAutomated safety check: PassApache-2.0
Control UIcursor/plugins10k2 repos~1.2kAutomated safety check: PassNone
Generate Snapshot Testsgetsentry/sentry46k—~3.3kAutomated safety check: PassCustom licence

Similar skills

  • Vrt

    marigold-ui/marigold

    DST — Trigger the Visual-Regression-Tests (Chromatic) GitHub Actions workflow on the current or a given branch.

    146 GitHub stars~787 tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • Visual Acceptance Review

    huiliyi37/Tianshu-harness

    Chinese-language final-check method for UI visual changes before delivery, using multi-theme screenshot matrices, pixel-level evidence and a CSS cascade checklist.

    1.1k GitHub stars~601 tokensUpdated today
    Frontend & DesignAuto-check passed
  • Migrate a click-ui component from styled-components to CSS Modules with byte-for-byte visual regression coverage.

    135 GitHub stars~7.7k tokensUpdated today
    Frontend & DesignAuto-check passed
  • Control UI

    cursor/plugins

    Official

    Build or adapt a local browser/CDP harness to drive and inspect a web, IDE, or Electron UI.

    10k GitHub starsUsed in 2 repos~1.2k tokens
    Frontend & DesignAuto-check passed
  • Generate Snapshot Tests

    getsentry/sentry

    Official

    Generate snapshot test files for Sentry frontend React components.

    46k GitHub stars~3.3k tokensUpdated today
    Frontend & DesignAuto-check passed
  • MiniMax M3 Multimodal Input

    madebyaris/advance-minimax-m3-cursor-rules

    Teaches an agent on MiniMax M3 to ground visual claims in attached images, screenshots, mockups and clips, and to re-read results after a visual change.

    126 GitHub stars~1.6k tokensUpdated 3 mo ago
    Frontend & DesignAuto-check passed

More from alinaqi/maggy

All 71 skills in this repo
  • AI Models

    alinaqi/maggy

    Latest AI models reference - Claude, OpenAI, Gemini, Eleven Labs, Replicate

    707 GitHub starsUsed in 1 repo~4.1k tokens
    Auto-check passed
  • Azure Cosmosdb

    alinaqi/maggy

    Azure Cosmos DB partition keys, consistency levels, change feed, SDK patterns

    707 GitHub starsUsed in 1 repo~4.5k tokens
    Auto-check passed
  • LLM Patterns

    alinaqi/maggy

    AI-first application patterns, LLM testing, prompt management

    707 GitHub starsUsed in 1 repo~2.1k tokens
    Auto-check passed
  • Woocommerce

    alinaqi/maggy

    WooCommerce REST API - products, orders, customers, webhooks

    707 GitHub starsUsed in 1 repo~4.4k tokens
    Auto-check: notes
  • Aeo Optimization

    alinaqi/maggy

    AI Engine Optimization - semantic triples, page templates, content clusters for AI citations

    707 GitHub stars~3.7k tokensUpdated 14 days ago
    Auto-check passed
  • Agent Teams

    alinaqi/maggy

    Claude Code Agent Teams - default team-based development with strict TDD pipeline enforcement

    707 GitHub stars~5k tokensUpdated 14 days ago
    Auto-check: notes

Questions about UI Testing

What does UI Testing do?

Visual testing - catch invisible buttons, broken layouts, contrast. UI Testing is an agent skill from alinaqi/maggy.

When should I use UI Testing?

UI Testing fits situations like: tasks that involve Visual regression testing.

How do I install UI Testing in Claude Code?

Run `npx skills add alinaqi/maggy --skill ui-testing -a claude-code`. Or copy the skill folder (skills/ui-testing in alinaqi/maggy) into .claude/skills/ui-testing in your project. Claude Code loads it when a task matches its description.

How do I install UI Testing in Codex?

Run `npx skills add alinaqi/maggy --skill ui-testing -a codex`. Or copy the skill folder (skills/ui-testing in alinaqi/maggy) into .agents/skills/ui-testing in your project. Codex loads it when a task matches its description.

Can I use UI Testing 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 alinaqi/maggy --skill ui-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ui-testing, .gemini/skills/ui-testing, .github/skills/ui-testing and .opencode/skills/ui-testing in your project.

What does UI Testing need to run?

Going by SKILL.md and its folder, UI Testing needs the command-line tools its instructions call (npm). Our summary lists: Node.js.

Does UI Testing access the network?

SKILL.md names 2 domains. As links in the text: webaim.org and coolors.co. This is read from the text; nothing was executed.

Is UI Testing 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 UI Testing use?

UI Testing 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 UI Testing use?

About 1.1k tokens (SKILL.md is roughly 4.4k 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 UI Testing?

Skills that share tags, products or a category with UI Testing: Vrt (marigold-ui/marigold, 146 stars), Visual Acceptance Review (huiliyi37/Tianshu-harness, 1.1k stars), Component CSS Modules Migration (ClickHouse/click-ui, 135 stars) and Control UI (cursor/plugins, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains UI Testing?

alinaqi (a GitHub user) maintains it in alinaqi/maggy, which has 707 GitHub stars. The repository holds 71 skills in this directory. The repository was last updated on September 24, 2026.

Source: alinaqi/maggy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.