ai-friendly-web-design-skill

왜 쓰나요

핵심 기능

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

라이브 데모

실제 사용 모습

ai-friendly-web-design-skill.replay ▶ 준비됨

0/0

설치

작성자 저장소 · Claude Skills 공식 문서

사용 사례

실전 활용법: 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

언제 쓸까: Your support chatbot or QA agent keeps missing the right button.

흐름

Feed Claude the component

Review this Checkout.tsx against ai-friendly-web-design principles. Flag severity.✓ 복사됨

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

Apply all critical + major fixes, keep visuals identical.✓ 복사됨

→ Patched component + a diff summary

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

함정

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

함께 쓰기: chrome-devtools

Build a new form with native controls and proper ARIA

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

언제 쓸까: A new form where you can't afford to block screen readers or agents.

흐름

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.✓ 복사됨

→ 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.✓ 복사됨

→ step param in URL, state restored on load

결과: 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

언제 쓸까: Your list page uses infinite scroll and agents never reach items below the fold.

흐름

Refactor to paginated route

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

→ Addressable pages, prev/next with ARIA

결과: A list an agent can walk deterministically.

함정

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

조합

다른 MCP와 조합해 10배 효율

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.✓ 복사됨

도구

이 MCP가 노출하는 것

도구	입력	언제 호출
review_component	component path/source	Any UI PR or audit
apply_principles	component + findings	After review
scaffold_agent_friendly	UI spec	Greenfield UI

비용 및 제한

운영 비용

API 쿼터: None
호출당 토큰: Moderate — component + review
금액: Free
팁: Run review at PR time, not every keystroke

보안

권한, 시크릿, 파급범위

자격 증명 저장: None

데이터 외부 송신: None

문제 해결

자주 발생하는 오류와 해결

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

대안