- Home
- Skills
- UX & UI Design
- Artifact Design Review: Score, Fix & Approve Prototypes
Works with the AI Agents you already use
Artifact Design Review: Score, Fix & Approve Prototypes
Designers and developers often ship UI prototypes that look good but fail on usability, accessibility, or responsiveness.
Free
Artifact Design Review: Score, Fix & Approve Prototypes
Example session with this skill installed
Review this HTML signup form artifact for accessibility and mobile responsiveness. Is it ready to build?
- Read your context and instructions
- Compiled the artifact design review
I have rendered the signup form at 1440px and 390px. While the desktop layout is functional, the mobile view and accessibility contrast require immediate attention.
Design Review Audit
| Criteria | Score | Evidence |
|---|---|---|
| Goal fit | 5 | Primary signup task is central and clear within 2 seconds. |
| Hierarchy | 4 | Clear "Create Account" CTA, though secondary "Login" link is small. |
| Consistency | 4 | Consistent 8px spacing grid used throughout. |
| Content | 3 | Error messages are generic; needs specific field validation text. |
| States | 2 | Missing loading state for the submit button and success state. |
| Responsive | 2 | Horizontal scroll present at 390px; input fields overflow container. |
| Accessibility | 2 | Submit button contrast is 2.8:1 (fails WCAG AA); touch targets <44px. |
| Buildability | 5 | Uses standard HTML input types and CSS Flexbox. |
Findings
| # | Severity | Where | Problem | Fix |
|---|---|---|---|---|
| 1 | Blocker | Submit Button | Contrast ratio 2.8:1 is below AA (4.5:1). | Change background to #2563EB. |
| 2 | Blocker | Container | Horizontal scroll at 390px. | Set width: 100% and box-sizing: border-box. |
| 3 | Major | Input Fields | Height is 32px (below 44px min). | Increase padding/height to min 44px. |
| 4 | Major | Error State | Generic "Error" text for all fields. | Add unique IDs and specific aria-live labels. |
| 5 | Minor | Typography | Label font-size is 11px. | Increase to 14px for readability. |
Verdict: Needs another round.
The mobile overflow and contrast failures are critical blockers.
Next steps
- Apply Blocker and Major fixes to the HTML artifact.
- Define specific error messaging for the email validation field.
- Re-render to confirm touch target compliance.
Connects securely to your tools. The creator never sees your data.
About this skill
Designers and developers often ship UI prototypes that look good but fail on usability, accessibility, or responsiveness. This skill transforms vague feedback like "looks okay" into a prioritized list of technical fixes based on WCAG AA standards and usability heuristics.
What it does
- Multi-view rendering renders artifacts at both desktop (1440px) and mobile (390px) widths to verify responsive behavior.
- State validation inspects empty, loading, error, and populated states to ensure no interaction gaps.
- Heuristic scoring evaluates goal fit, hierarchy, consistency, and buildability on a 1-5 scale with documented evidence.
- Accessibility auditing checks for WCAG AA compliance, including color contrast ratios and minimum touch target sizes.
- Automated iteration applies prioritized fixes directly to the artifact code based on identified blockers.
How it works
- Input capture takes an HTML artifact, link, or screenshot and renders it across multiple breakpoints.
- Systematic evaluation scores the design across eight specific criteria from content clarity to technical buildability.
- Prioritized reporting generates a findings table categorizing issues by severity from Minor to Blocker.
- Iterative fixing applies the necessary code changes to resolve top-priority issues and re-renders the result.
Frameworks & tools
Works with HTML/CSS artifacts, Claude Canvas, and web prototypes. Uses Playwright or browser rendering for visual capture.
Why this beats prompting it yourself
Generic prompts often miss specific accessibility failures like small touch targets or insufficient contrast ratios. This skill enforces a structured scoring rubric and specific viewport testing that manual prompting usually skips.
Use cases
- Reviewing a new landing page component for mobile responsiveness.
- Auditing a dashboard prototype for WCAG AA accessibility compliance.
- Checking if a developer-built UI matches the original design tokens and hierarchy.
- Identifying missing edge cases like empty states or loading indicators in a flow.
Known limitations
Limited to 10 findings per round and 3 iteration rounds. Requires the artifact to be renderable via browser or Claude's internal tools.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for UX & UI Design.
Maximum 10 findings per review round. Limited to 3 automated iteration rounds before requiring explicit approval. Requires browser/Playwright access to render artifacts.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
This skill has been used 1 time.
Trust & safety
Security scan
Security scan passed 4 days ago
- Free with an Agensi account