Generates a formatted Excel accessibility audit report from Figma file comments with visual evidence screenshots. Parses structured audit comments containing WCAG criteria, error descriptions, and proposed solutions. Captures PNG evidence of each affected component and outputs a professional errores-accesibilidad.xlsx spreadsheet with hyperlinked evidence. Requires the figma-console MCP server connected to a Figma file via the Desktop Bridge plugin. Use this skill whenever the user wants to audit accessibility in Figma, extract errors from Figma comments, generate a WCAG report from a design file, capture evidence of accessibility violations, or create an Excel spreadsheet of accessibility issues found in Figma. Also trigger on "Figma audit", "Figma accessibility", "accessibility comments in Figma", "errores de accesibilidad", "export Figma comments to Excel", "WCAG audit report", "evidencias de accesibilidad", "informe de accesibilidad", "accessibility report from Figma", or any request involving Figma desig
Expert guidance for writing, configuring, and running tests with Rstest — the Rspack-powered. JavaScript/TypeScript testing framework with Jest-compatible APIs and native ESM/TypeScript support. Covers setup, configuration (rstest.config.ts), mocking (rs.mock, rstest.fn, rstest.spyOn), fake timers, snapshots, DOM testing (jsdom/happy-dom), Browser Mode (Playwright), React/Vue component testing, code coverage (istanbul), multi-project testing, in-source tests, and integration with Rsbuild/Rslib via official adapters (@rstest/adapter-rsbuild, @rstest/adapter-rslib). Use this skill whenever the user mentions "rstest", "@rstest/core", is writing or debugging tests in an Rspack/Rsbuild/Rslib project, migrating from Jest or Vitest to Rstest, or needs help with any testing workflow that involves the Rstack ecosystem. Also trigger when the user asks about mocking with rs.mock, configuring test environments, or setting up browser-based testing with @rstest/browser.
Expert knowledge base for building accessible UI components with awareness of real-world assistive technology (AT) support gaps. Goes beyond the WAI-ARIA spec to provide actual AT compatibility data from a11ysupport.io, known screen reader quirks, proven workarounds, and the critical gotchas that emerge when ARIA meets real users on real devices. Use this skill whenever the user is building, reviewing, fixing, or testing an interactive UI component for accessibility — especially when they need to know what actually works across screen readers, not just what the spec says should work. Trigger on mentions of "ARIA", "a11y", "accessibility", "screen reader", "keyboard navigation", "WAI-ARIA", "APG patterns", "AT support", "assistive technology", "aria-modal", "tooltip role", "combobox", "menu pattern", "switch role", or any question about whether an ARIA feature actually works in practice. Also trigger when the user mentions specific screen readers (JAWS, NVDA, VoiceOver, TalkBack, Narrator) or asks about cross-