ai-friendly-web-design-skill

Why use it

Key features

14 design principles optimized for agent navigation + accessibility
Stable data-testid / data-ai-action locator conventions
No hover-only interactions, no iframes/Shadow DOM barriers
Explicit loading states to avoid race conditions
Auto-activated during UI build / review — flags issues with severity

Live Demo

What it looks like in practice

ai-friendly-web-design-skill.replay ▶ ready

0/0

Install

Author repository · Claude Skills documentation

Use Cases

Real-world ways to use ai-friendly-web-design-skill

Audit an existing component for agent-readiness

👤 Web devs shipping to customers who'll hit the page with agents ⏱ ~30 min beginner

When to use: Your support chatbot or QA agent keeps missing the right button.

Flow

Feed Claude the component

Review this Checkout.tsx against ai-friendly-web-design principles. Flag severity.✓ Copied

→ Ranked list: critical (hover-only submit) -> minor (missing aria-live)
Apply the fixes

Apply all critical + major fixes, keep visuals identical.✓ Copied

→ Patched component + a diff summary

Outcome: A component that's still pretty for humans and reachable for agents.

Pitfalls

Adding data-testid everywhere without convention — Follow the skill's naming convention (data-testid='<area>-<action>') or they drift

Combine with: chrome-devtools

Build a new form with native controls and proper ARIA

👤 Frontend devs building high-stakes forms (checkout, onboarding) ⏱ ~45 min intermediate

When to use: A new form where you can't afford to block screen readers or agents.

Flow

Scaffold from principles

Build a billing address form using ai-friendly-web-design. Native input types, labels, aria-describedby for errors, explicit loading on submit.✓ Copied

→ Form with HTML native types (email, tel), no custom combobox hacks
Add deep-linking + URL state

Make the form step reflect in the URL so agents can open step 2 directly.✓ Copied

→ step param in URL, state restored on load

Outcome: A form both assistive tech and agents navigate cleanly.

Replace infinite scroll with predictable pagination

👤 Product engineers where agents fail to get past page 1 ⏱ ~30 min intermediate

When to use: Your list page uses infinite scroll and agents never reach items below the fold.

Flow

Refactor to paginated route

Replace the infinite-scroll list with URL-based pagination (?page=N). Keep scroll behavior feel.✓ Copied

→ Addressable pages, prev/next with ARIA

Outcome: A list an agent can walk deterministically.

Pitfalls

Breaking SEO by removing the old scroll entirely — Keep scroll load within each page — just make the page boundary explicit

Combinations

Pair with other MCPs for X10 leverage

ai-friendly-web-design-skill + chrome-devtools

Test the component live and confirm agent locators work

Load the patched component in devtools, verify data-testid values and aria attributes render.✓ Copied

Tools

What this MCP exposes

Tool	Inputs	When to call
review_component	component path/source	Any UI PR or audit
apply_principles	component + findings	After review
scaffold_agent_friendly	UI spec	Greenfield UI

Cost & Limits

What this costs to run

API quota: None
Tokens per call: Moderate — component + review
Monetary: Free
Tip: Run review at PR time, not every keystroke

Security

Permissions, secrets, blast radius

Credential storage: None

Data egress: None

Troubleshooting

Common errors and fixes

Review says no issues but agents still miss buttons

Run with Chrome DevTools snapshot; shadow DOM may hide from the static review

data-testid names clash with existing tests

Provide your naming convention to the skill before it auto-names

Alternatives