Accessibility
Accessibility testing and improvements
accessibility
by microsoft
Primary accessibility skill for VS Code. REQUIRED for new feature and contribution work, and also applies to updates of existing UI. Covers accessibility help dialogs, accessible views, verbosity settings, signals, ARIA announcements, keyboard navigation, and ARIA labels/roles.
typescript-review
by metabase
Review TypeScript and JavaScript code changes for compliance with Metabase coding standards, style violations, and code quality issues. Use when reviewing pull requests or diffs containing TypeScript/JavaScript code.
deep-review
by coder
Sub-agent powered code reviews spanning correctness, tests, consistency, and fit
peekaboo
by openclaw
"Capture and automate macOS UI with the Peekaboo CLI."
generate-frontend-forms
by getsentry
Guide for creating forms using Sentry's new form system. Use when implementing forms, form fields, validation, or auto-save functionality.
react-component-documentation
by getsentry
Create or update component documentation in Sentry's MDX stories format. Use when asked to "document a component", "add stories", "write component docs", "create an mdx file", "add a stories.mdx", or document a design system component. Generates structured MDX with live demos, accessibility guidance, and auto-generated API docs from TypeScript types.
accessibility
by elastic
Accessibility guidance for Kibana. Use this skill when working with or reviewing EUI components, resolving a11y-related (@elastic/eui) ESLint issues, and ensuring proper use of ARIA attributes, focus management, keyboard interactions, and accessible naming conventions.
realsig-codegen
by dotnet
Debug and fix --realsig+ (RealInternalSignature) codegen bugs in IlxGen — MethodAccessException / FieldAccessException / TypeAccessException at runtime, IL private vs assembly visibility, closure and TLR-lift placement (cloc / NestedTypeRefForCompLoc / effectiveCloc / moduleCloc). Use when a program compiles cleanly but crashes only under --realsig+, when IL accessibility differs between realsig modes, or when reasoning about where compiler-synthesized closures/state-machines/quotation helpers are nested.
building-components
by vercel
Guide for building modern, accessible, and composable UI components. Use when building new components, implementing accessibility, creating composable APIs, setting up design tokens, publishing to npm/registry, or writing component documentation.
run-device-tests
by dotnet
"Build and run .NET MAUI device tests locally with category filtering. Supports iOS, MacCatalyst, Android on macOS; Android, Windows on Windows. Use TestFilter to run specific test categories."
web-design-guidelines
by vercel
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
sd-diagram
by platypeeps
Use when the user wants an evidence-backed technical diagram. Prefer Archify when available; support explicit Mermaid requests and tool-neutral briefs.
sd-learn
by platypeeps
Use when the user wants an adaptive, mastery-oriented learning path from a stated capability goal, diagnosed baseline, constraints, and observable evidence.
ux-audit
by eytanbab
Audit a website, mobile application, design mockup, or web UI from a UX/UI standpoint and generate a severity-ranked, actionable report written at the level of a senior design lead. Use this skill whenever asked to review a UI, audit UX/UI friction, critique a design or flow, verify accessibility (WCAG), give feedback on forms, dashboards, and interactive screens, check for dark patterns, or explain why a UI "feels off", looks unprofessional, or needs polish. Works for web and native mobile (React Native, Flutter, SwiftUI, Jetpack Compose). Builds grounded personas from repository inspection and lightweight confirmation, persists context in .ux-audit/context.json, tracks issue resolutions across runs, and gives each finding calibrated severity, confidence, effort, and priority with a concrete fix and acceptance criteria. Supports Source-Only, Interactive (Playwright + axe-core), and Design Review modes. Do not use for backend API performance tuning, database schema optimization, or infrastructure/CI-CD audits.
react-testing
by gagandeepgill
React component testing with React Testing Library, Vitest/Jest, MSW for network mocking, accessibility assertions with axe, and the decision boundary between component tests and Playwright/Cypress end-to-end runs. Use when writing or fixing tests for React components, hooks, or pages.
product-audit
by tin-computer
Exercise every mapped feature of a product as a user with a Tin-owned identity, run cross-cutting quality checks, and write one dated audit report with ranked findings.
accessibility-testing
by proffesor-for-testing
"WCAG 2.2 compliance testing, screen reader validation, and inclusive design verification. Use when ensuring legal compliance (ADA, Section 508), testing for disabilities, or building accessible applications for 1 billion disabled users globally."
code-review
by adobe
Review code for AEM Edge Delivery Services projects. Use at the end of development (before PR) for self-review, or to review pull requests. Validates code quality, performance, accessibility, and adherence to EDS best practices.
ln-114-frontend-docs-creator
by levnikolaevich
Creates design_guidelines.md for frontend projects. L3 Worker invoked CONDITIONALLY when hasFrontend detected.
web-design-guidelines
by vercel-labs
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
front-end-checklist
by fabricioctelles
This skill should be used when a developer or team needs to review, validate, or audit front-end code before launching a website or HTML page to production. Triggers on requests such as "run the front-end checklist", "validate my front-end", "check my site before launch", or when the user asks for a structured review of HTML, CSS, JavaScript, accessibility, performance, security, or design quality.
scenario-godot-ui
by scenario-labs
"Use when building or fixing game UI in Godot 4.7: main menu, settings screen, HUD (health bar, ammo, minimap frame), Control layout, containers, anchors, themes in code, 'UI scales wrong on phones', 'text too small on 4K', notch or safe area, stretch mode and aspect, gamepad or keyboard menu navigation, focus lost, input rebinding screen, localization (CSV, PO, tr_n plurals, Arabic RTL, CJK fonts, pseudolocalization), screen reader accessibility, UI scale slider, or clicks not reaching the game."
senior-frontend
by ComposioHQ
Frontend development skill for React, Next.js, TypeScript, and Tailwind CSS applications. Use when building React components, optimizing Next.js performance, analyzing bundle sizes, scaffolding frontend projects, implementing accessibility, or reviewing frontend code quality.
ponytail
by diegosouzapw
"External agent skill (MIT, github.com/DietrichGebert/ponytail). Forces the laziest solution that actually works: question whether the task needs to exist at all (YAGNI), reuse what is already in the codebase, reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Climb the ladder on every coding task — writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Supports intensity levels: lite, full (default), ultra. Never cut validation, error handling, security, or accessibility."