frontend-visual-qa vs io.github.yusufcemres/uisight
frontend-visual-qa is a plugin bundle for AI coding tools published by daymade. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.yusufcemres/uisight is an MCP server published by yusufcemres. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-11. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  frontend-visual-qa |  io.github.yusufcemres/uisight |
|---|---|---|
| Community marketplace daymade/claude-code-skills | Listed Version: 1.21.43 Forks (GitHub): 235 Stars (GitHub): 1 524 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.34.0 Downloads/month (npm): 646 Downloads/week (npm): 261 Forks (GitHub): 9 Stars (GitHub): 130 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.34.0 Downloads/month (npm): 646 Downloads/week (npm): 261 Forks (GitHub): 9 Stars (GitHub): 130 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | frontend-visual-qa | io.github.yusufcemres/uisight |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 1 524 (better) | 130 (worse) |
| Forks (GitHub) (differs) | 235 (better) | 9 (worse) |
| Last release (differs) | 2026-11-11 | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (uisight) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 0 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/daymade/claude-code-skills | github.com/sololabstr/uisight |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
frontend-visual-qa
Audits rendered UI and specific task/object-link handoffs; excludes ordinary source citations alone. Audits already-rendered UI and Markdown/Obsidian image layout — web app, deck/slide, dashboard, design-system, or Electron/native app — via real-browser/native-app journeys and a Playwright sweep. Use after UI implementation to find typography, overflow, responsive, routing, data-viz, browser-output, or native-shell defects, or to compare a render against a reference. Not for greenfield UI design (use ui-designer) or QA-program setup (use qa-expert).
io.github.yusufcemres/uisight
Your AI sees the screen but can't measure it — measured web UI findings, shared live sessions
How to run each
frontend-visual-qa As a Claude Code plugin
/plugin marketplace add daymade/claude-code-skills
/plugin install frontend-visual-qa@daymade-skillsio.github.yusufcemres/uisight As a local MCP server: npm package
claude mcp add --transport stdio uisight -- npx -y uisightCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of frontend-visual-qa publish no settings it asks for, so we do not compare settings.
What it can do: frontend-visual-qa · What it can do: io.github.yusufcemres/uisight · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.