Use for any design, UI, or UX work on Apple-platform products, including visual design, interaction design, layout, navigation, accessibility, design review, and implementation decisions that should align with Apple Human Interface Guidelines.
Run and operationalize VertaaUX UX, accessibility, and conversion audits across CLI, CI/CD, SDK, API, and MCP. Use when the user needs to audit a URL, investigate WCAG issues, set quality gates, compare audit runs, select an audit profile, or generate remediation plans from VertaaUX results.
Audit an existing digital product artifact or flow and return evidence-backed, severity-calibrated findings. Trigger on "audit this", "critique this screen", "review this flow", or "find UX issues" when inspectable evidence is available. Use dashboard-redesign for dashboard redesigns and design-system-review for…
Validates UI/UX designs with UXLoom — models user journeys as state machines and proves what screens are missing (unreachable states, dead ends, empty/loading/error coverage, WCAG contrast, touch targets, localization overflow) before code exists. Use when designing screens or user flows, validating AI-generated UI…
Read agent output aloud with the Text to Speech MCP server's speaktext tool — streamed as the agent works, batched once the turn is done, or reading a specific file or block of text on request. Use when the user asks to hear something read aloud, asks for a spoken demo or walkthrough, or works in a project configured…
Expert front-end web typography — apply this whenever you are styling text on the web or making type decisions in HTML/CSS/JSX/Tailwind. Use it to choose and pair fonts, build a type scale, set body copy and headings, tune fluid/responsive type with clamp(), fix line-height, rhythm, measure and heading wraps, improve…
Runs a WCAG 2.2 accessibility audit of a screenshot, URL, or HTML/JSX and reports findings by severity (P0 blocks use, P1 degrades use, P2 friction), each with a success-criterion citation. Use for "check accessibility", "run an a11y audit", "is this WCAG compliant", "is this accessible", or "audit contrast and…
Design execution engine. Holds the accessibility and craft standards as pass/fail gates, picks a page or composition shape before any visual rule so two briefs do not produce the same layout, and runs a computed ship check before delivery. Use this skill for ANY design or build task in any medium: poster, flyer…
Set up database / persistent-state discipline for a project with a DB. Authors a data-auditor agent (5 categories of integrity check), a migration-create skill, query-discipline rule (CLI > MCP DB tool for reads), and edit-time regen hook — all derived from the project's actual schema, migration framework, and…
Apply and audit WCAG 2.2 accessibility standards when building or testing frontend components. ALWAYS use this skill when: building any UI component, page, or layout (even if the user doesn't mention accessibility); running accessibility audits or tests; asked to "check a11y", "test accessibility", "audit WCAG…
A set of design and accessibility rules for Indian government websites, portals, and administrative panels, including required standards such as GIGW and WCAG.
Plans, designs, builds, validates, and prepares polished responsive websites and lightweight web apps from brief through hosting handoff. Use when creating or redesigning a landing page, portfolio, editorial site, knowledge hub, directory, dashboard, portal, tracker, internal tool, microsite, or small web app…
Build, audit, or convert websites with the U.S. Web Design System (USWDS) using the unofficial uswds-mcp server. Use when work involves USWDS components, patterns, templates, accessibility guidance, design tokens, utilities, @uswds/uswds, or federal website implementation.
Audit and correct accessibility problems in rendered web interfaces using the wcag-accessibility MCP tools. Use when an agent creates, changes, reviews, or verifies HTML/CSS/UI code; when asked about WCAG, contrast, labels, semantics, keyboard access, focus, screen readers, responsive accessibility, or accessibility…
Labels, errors, grouping, and autofill for mobile forms. Use this when building any screen that collects user input — login, signup, checkout, profile editing.
Use when controlling, setting up, developing, debugging, or extending the MacWright macOS desktop automation MCP server. Covers setup/doctor, permissions, visual fallback control, Accessibility API usage, mcporter calls, and reliability verification.
Build, render, lint, and audit LaTeX-first documents (CVs, papers, patents, FAQs, guides) through the Inclusio engine. Use when the user mentions LaTeX, tagged PDFs, PDF/UA-2, PDF/A-4f, WCAG accessibility, the European Accessibility Act (EAA), or asks about building/auditing documents in a repository that has a…
Observe and (with a grant) drive Chromium tabs via the pagouse CLI: snapshot the accessibility tree, click/fill by ref, navigate. Not a seat adapter. Trigger keywords: pagouse, browser tab, fill form, click the button on the page, snapshot page, AX tree.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: