Baseline UI
A compact, opinionated baseline for spacing, typography, and interaction code.
The field guide
Loading the selection…
A closer look / 9 skills
Find AI skills for UI audits, accessibility fixes, and interface reviews. Choose a focused review for the code and user experience you need to improve.
A compact, opinionated baseline for spacing, typography, and interaction code.
Targeted repairs for semantics, keyboard access, focus, contrast, and forms.
Check titles, canonicals, social previews, structured data, and indexing directives.
Find layout thrashing, costly animated properties, and scroll-linked bottlenecks.
One design skill with named workflows, browser iteration, and edit hooks.
Prioritized React and Next.js guidance for data flow, bundles, and rendering.
A scan, diagnose, and fix workflow for an interface that already exists.
A strict review of timing, purpose, interruption, and animation implementation.
Fetch current interface guidelines and report review findings by file and line.
Choosing a skill
UI audit skills help an agent inspect an interface and explain what to change. Choose the scope before you run a review: a broad pass can surface inconsistencies, while a focused reviewer is easier to use when you already know the problem. Share the relevant files and the behavior you expect.
Start with a broad code review that reports findings by file and line. This skill fetches a live external rulebook, so the agent needs network access and the review criteria can change over time.
Read the Web Design Guidelines reviewNarrow the task to semantics, keyboard access, focus behavior, and contrast. This is a targeted repair workflow for an existing interface; its instructions do not provide certification or a complete accessibility conformance assessment.
Read the Fixing Accessibility reviewUse performance-oriented guidance when the issue concerns React or Next.js data flow, bundle size, or rendering. It helps prioritize code changes; visual art direction needs a different brief.
Read the React Best Practices reviewAsk for findings tied to specific code and user impact. After a repair, exercise the affected interaction and run the checks appropriate to your project. A source-based review identifies changes to investigate; measured performance and accessibility results require their own verification.