For example: โa dropdown where users search and pick their countryโ.
Paste a Storybook URL, an npm package, a repo, a Figma/Adobe XD file link, or the filename of a screenshot/mockup. The prompt will tell your agent to match your existing tokens and conventions instead of inventing new ones.
Use a deployed URL, package name, repo reference, a Figma/Adobe XD link, or a screenshot filename. Design-file and screenshot sources are a visual spec, not a rendered artifact โ they can't satisfy the release gate on their own, and a screenshot alone can't show hover/focus/disabled/error/loading states.
Stays in this browser tab only. Files under ~150KB are embedded in the copied prompt as both a Markdown image and a raw data-URI fallback. Some external agents strip rendered data images; if it does not appear, attach the original file directly. Larger files are referenced by filename only.
CSS custom properties, a token JSON blob, or plain name:value pairs โ carried into the prompt verbatim so the agent uses your values instead of inventing new ones.
A live site, a preview URL, localhost, or a repo path โ whatever you've got.
Used to check your components against their own source patterns, not just the standard.
Use a package name or repo reference for the design-system pattern check.
Optional: crawl this site instead of auditing one page
Choose whether the audit should follow same-origin links across a flow. The crawl stops at the page limit you set, up to 20 pages.
Handoff spec โ a file to send your developer (ticket, PR description, design review), not another prompt.
Paste the result into Claude Code, Codex, Copilot, or any agentic coding tool. If the accessibility MCP server is connected, the check prompts will call its audit tools directly. See the expert view for WCAG level, platform targets, provenance tiers, and crawl options.