Accessibility
Accessibility testing and improvements
happy-dom-tests
by iulspop
Generates React component render tests using happy-dom and Testing Library with the "given/should" prose format. Use when writing tests for display components, hooks, user interactions, or accessibility checks.
recharts
by ansanabria
Build composable, responsive React charts with Recharts library. Use when creating data visualizations including line charts, area charts, bar charts, pie charts, scatter plots, and composed charts. Handles chart customization, responsive sizing, tooltips, legends, axes configuration, performance optimization, and accessibility.
wcag-audit-operable-target-size
by Jkense
Validate touch target sizes meet 44x44px minimum requirement
component-library
by pluginagentmarketplace
Build production-grade, accessible, and tested component libraries with Storybook, Chromatic, and design tokens
accessibility
by PABERTHIER
Audit or improve accessibility of Keola's Nuxt pages, components and interactions across FR/EN/JA; use for accessibility implementation and review, not copy-only edits.
life-os-browser-proof
by Planton361
Project-local Life OS browser proof skill. Use when Codex must prove UI, forms, buttons, navigation, prepared states, persistence, reload stability, accessibility-relevant interaction, or user-visible behavior in a local browser or Playwright-compatible flow without requiring MCP installation.
a11y-best-practices
by moderndegree
Comprehensive accessibility patterns for building, testing, and fixing accessible interfaces. Use when building UI components, forms, pages, or auditing code for accessibility issues.
phone-harness
by sparkedoficial-stack
"Control the user's phone - an iPhone through the Mac's iPhone Mirroring window, an Android over adb, a rented cloud Android, or a cloud iPhone over HTTPS: open apps, tap, type, swipe, read the screen."
mariadb-best-practices
by jcastillotx
MariaDB database development standards. Triggers when working with MariaDB databases, Galera cluster, or MariaDB-specific features.
data-visualization
by moderndegree
Chart selection, data viz accessibility, and dashboard patterns. Use when building charts, graphs, or data dashboards.
ink
by modersetech
Use this skill whenever the user wants to build a CLI (command-line interface) tool or terminal UI using React/JSX. Triggers include: "build a CLI", "terminal UI", "interactive command-line app", "CLI tool with components", or any mention of the Ink library. Also trigger when the user wants to render dynamic styled output in the terminal, handle keyboard input in a CLI, or build a multi-component terminal layout. Use this skill even if the user just mentions "React for the terminal" or wants to add interactivity (spinners, prompts, menus, progress bars) to a Node.js CLI.
gsp-accessibility-audit
by mutav-finance
Full WCAG accessibility audit — design screens, codebase, or generate compliance statement
frontend-studio
by potatoman03
Build tasteful, modern, production-grade frontends with distinctive design. Use when building websites, landing pages, dashboards, SaaS UIs, e-commerce pages, portfolios, or any web interface. Extends Anthropic's frontend-design skill with a design decision framework, shadcn/ui defaults, rams.ai accessibility enforcement, and a technique library that produces clean, unique output — never AI slop. Activate for: "build me a website", "create a landing page", "design a dashboard", "make a UI for...", or any frontend request.
figma-d3-react-ts
by CoRLab-Tech
D3.js data visualization in React/Next.js components with PIXEL-PERFECT Figma matching. Use when building interactive charts, graphs, network diagrams, geographic maps, or any custom data visualization with D3.js inside React components. Covers pixel-perfect Figma extraction workflow, iterative visual validation via Playwright, two integration approaches (useRef+useEffect imperative vs declarative React rendering), responsive sizing, TypeScript typing, SSR/Next.js compatibility, accessibility, and performance. Triggers on: 'create a chart', 'add a D3 visualization', 'build a graph component', 'data visualization', 'interactive chart', 'force-directed graph', 'bar chart', 'line chart', 'heatmap', 'scatter plot', 'pie chart', 'chord diagram'.
design-system-guardian
by agebold
Strictly enforces the local design system, accessibility (WCAG 2.2 AA), and world-class design craft for any web or responsive UI work. Use this skill whenever the user asks to build, edit, style, refactor, or review ANY frontend component, page, layout, form, or markup — even casual requests like "make this look nicer", "add a button", "build a card", "fix this CSS", or "create a settings page". Trigger on any mention of HTML, CSS, JSX/TSX, Tailwind, components, styling, layouts, responsive design, accessibility, or visual polish. Do NOT skip this skill just because the request seems small — every UI change must pass through the design system rules.
ui-visual-review
by magfrump
Review and fix visual/layout issues in UI code — cross-resolution compatibility, scrollability, overflow handling, sizing, affordance, focus order, and 3D viewport rendering. Triggers on ANY visible UI element, not just CSS: TSX/JSX, Vue, Svelte, Tailwind, CSS-in-JS, Unity/C# UI components (Button, Toggle, Selectable subclasses), SwiftUI views, native mobile layouts, and 3D rendering surfaces (three.js, react-three-fiber, Babylon, model-viewer, Unity WebGL, Unreal Pixel Streaming, .glb/.gltf). Validates recommendations against accessibility standards (WCAG 2.2), NNGroup usability research, and platform UI guidance. Use this skill when the user reports visual elements that are cut off, overlapping, invisible at certain resolutions, or otherwise broken across screen sizes. Also trigger on any of: "fix the layout", "make this responsive", "review the UI", "check visual elements", "audit the CSS", "review the layout", "check the UI", "fix the styling", "responsive design review", "is this responsive", "does this work on mobile", "layout review", or when a diff touches any file containing rendered UI — including TSX/JSX, CSS, SCSS, Tailwind class strings, Unity C# UI scripts, or 3D scene setup. Produces concrete code fixes plus a structured report of findings. NOTE: This skill can be invoked standalone or by a code-review orchestrator. If a code-fact-check report is provided, use it as your foundation for understanding what the code actually does and do not re-verify documented behavior.
component-advisor
by epci971
Passive detection of EPCI component creation opportunities. Identifies repetitive patterns that could become skills, commands or subagents. Use when: workflow analysis, recurring pattern detection. Not for: active component creation (use /epci:create).
wcag-audit
by waseemkhan00777
Automated WCAG 2.1 AA accessibility audit using Puppeteer and axe-core across all application routes.
swiftui-expert-skill
by prateek
Use when writing, reviewing, or refactoring SwiftUI code for iOS or macOS, including state management and @Observable data flow, view composition and invalidation/performance, lists and ForEach identity, environment usage, localization, animations, Liquid Glass adoption, migrating soft-deprecated APIs, or Instruments .trace capture/analysis for hangs, hitches, CPU hotspots, or
angular
by yldgio
Angular component architecture, RxJS patterns, change detection, and module organization
minecraft-spell-production
by Gustavaopere
Use when a Minecraft spell or magical ability needs end-to-end production or review across mechanics, casting, animation, models, VFX, audio, feedback, accessibility, synchronization, lifecycle, and performance.
motion-patterns
by SeuPut0705
Production-ready animation patterns for React / Next.js — button, modal, toast, stagger, page transitions, exit animations, scroll, and layout — built on motion-foundations tokens and springs. Use when animating a specific UI element in React or Next.js — button, modal, toast, stagger, page transition, or scroll.
show-and-tell
by wan-huiyan
Turn dense technical findings, an analysis, a code/research session outcome, or a jargon-heavy document into a beautiful, genuinely PLAIN-ENGLISH self-contained HTML explainer that a non-technical or busy stakeholder can actually understand — built on a single everyday metaphor carried through the whole piece, with the REAL numbers shown honestly beside each plain claim, an "engineer's note" layer so technical readers aren't shortchanged, an honesty/limits box, and an arcade/pixel aesthetic that opens straight from file:// (no build, no server). Use this WHENEVER the user wants to explain technical work in plain English, make a pretty/shareable report, one-pager, or recap, summarize an investigation/session "so my boss/team/client can understand it," translate jargon results for a lay audience, or asks for an explainer/writeup/"make this readable" of findings — even if they don't say "HTML." Also use to turn an existing analysis doc or markdown report into a friendly visual explainer. Prefer this over a plain markdown summary when the audience is non-expert or the user says "pretty," "plain English," "for my boss," "easy to understand," or "report."
audit-website-pro
by ferdiboxman
Comprehensive website audit with real data — performance, security, SEO, accessibility, and broken links. Powered by x402 micropayments. Use when the user wants a FULL site health check with actual Lighthouse scores, security header analysis, SSL verification, accessibility violations, and broken link detection. Unlike basic audit skills that give checklists, this calls APIs and returns evidence-based reports. Triggers on "website audit," "site health," "is my site secure," "check my website," "performance audit," "accessibility check," "security audit," "broken links," "full site review," or "website health check."