{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/design.ui-critique/",
    "json": "https://www.anchorterminal.com/niches/design.ui-critique/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/design.ui-critique/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/design.ui-critique/index.min.md"
  },
  "markdown": "No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 0 | 2 | 12 | 8 | 3 |\n\n## What counts as done\n\nA list of findings, each with a rule id, severity, location (file and line, or selector) and suggested fix, from a run that can be read-only, with an exit status that separates findings from a failed scan.\n\nHow agents ask for it: review this page's design; does this look AI-generated; check contrast and spacing; audit our UI for anti-patterns\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **Impeccable (Renaissance Geek, Inc.)**: detect --json over files, folders or URLs returns findings with rule id, severity, file and line, exiting 0 clean, 2 findings, 1 unscannable. Findings carry a rule description, not a fix; the read-only critique path (acc-34) is merged but unreleased, and acc-15 notes missed patterns.\n- **UX Pilot MCP server (UX Pilot)**: review runs UX, persona and accessibility reviews on a screen, raw HTML or a live URL, without applying fixes unless apply is true. Findings' rule ids, severities and locations aren't specified, and reviews cost credits.\n\n- not this job: ArtCraft (Storyteller): No interface audit.\n- not this job: Figma API + MCP (Figma, Inc.): No tool audits a built interface for rule-based findings; the server reads and writes Figma files.\n- not this job: Framelink MCP for Figma (Framelink (Graham Lipsman)): No audit or rule findings; the tools fetch design data.\n- not this job: Framer Server API (Framer B.V.): MCP can review SEO, headings and alt text, but there are no rule ids, severities or exit status for design findings.\n- not this job: Kite (Kite): No audit or rule findings tool.\n- not this job: Magic Patterns (North Park Labs, Inc.): No audit or rule findings.\n- not this job: Melius (Melius AI, Inc.): No interface audit.\n- not this job: Miro API + MCP (RealtimeBoard Inc. dba Miro): No interface audit.\n- not this job: pen.dev (High Agency, Inc.): No audit tool.\n- not this job: Penpot API + MCP (Kaleidos Subsidiary SL): Audits design files, not a built interface.\n- not this job: Presentations.AI MCP server (Presentations.AI): No interface audit.\n- not this job: Sketch (Sketch B.V.): Audits Sketch documents, not a built interface.\n- not this job: Subframe (Atomic Design Inc): No audit of a built interface.\n- not this job: UXKIN (UXKIN (no legal entity named)): The no-ui-slop skill guides the agent's own UI work; there is no audit with rule ids or exit status.\n- not this job: Zeplin (Zeplin, Inc.): No interface audit.\n\n## What stops agents finishing\n\n- flow requires writes to the repo or questions to a person\n- telemetry on by default where policy forbids it\n\n## Around it\n\nBefore: code.implement-ui. After: code.edit.\n\n## Where this comes from\n\nWeight 8 of 100 in Design workspaces \u0026 canvases: 3 of 42 accounts (Impeccable) plus vendor pages for UX Pilot and Penpot's audit use case\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/design.ui-critique.json, or the MCP tool get_use_case with id design.ui-critique. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Critique and audit a built interface for design quality",
        "url": ""
      }
    ],
    "description": "Critique and audit a built interface for design quality: 0 companies fully do it, 2 with a limit, 12 carry the tag. Every listing in Design workspaces \u0026 canvases with the reason and a source.",
    "facts": null,
    "h1": "Critique and audit a built interface for design quality",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/design.ui-critique/",
    "published": "",
    "section": "agents",
    "title": "Critique and audit a built interface for design quality | Anchor…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/design.ui-critique/"
  },
  "tokens": {
    "markdown": 1000,
    "slim": 230
  },
  "version": 1
}
