Accessibility
Accessibility testing and improvements
wcag-audit-perceivable-text-size
by Jkense
Convert between px, pt, em, rem units with accessibility context
jekyll-research-theme
by lalithaar
Create production-grade, accessible Jekyll themes for researchers conducting "research in public." Generates complete lab notebook-style themes with Tufte-inspired sidenotes, KaTeX math rendering, and WCAG 2.1 AA compliance. Use when building Jekyll themes for scientific journals, experiment logs, field notes, or research documentation sites. Supports collections for organizing experiments and field notes, responsive sidenote rendering (sidebar on desktop, inline on mobile), and full-width layout options.
check-forms
by leobrival
Analyze and validate forms on web pages. Use when users ask to check form accessibility, verify form labels, audit input fields, check form validation, or analyze form UX. Detects missing labels, invalid input types, accessibility issues, and validation problems.
wcag-audit-understandable-forms
by Jkense
Route form input and data collection accessibility requirements
temporal-brand
by jburns24
Applies Temporal's official brand colors, logo variants, and visual identity to any artifact. Use this skill whenever creating UI code, presentations, diagrams, or any content following Temporal brand guidelines. Also use it when the user asks about Temporal brand colors (#444CE7 UV purple, #141414 Space Black, #F8FAFC Off White), the Temporal logo, Temporal branding, dark/light mode theming, or visual style.
vector-design-best-practices
by anaghkanungo7
Expert guidance on creating, optimizing, and implementing SVG graphics with accessibility and performance in mind
wcag-audit-perceivable-layout-deep
by Jkense
Page structure and spatial organization accessibility design patterns
a11y-semantics-pass
by velcrafting
Improve semantics and accessibility coverage for UI changes (roles, labels, focus, keyboard, ARIA correctness).
ultracite
by tylergibbs1
Enforce strict type safety, accessibility standards, and code quality for TypeScript/JavaScript projects using Biome's formatter and linter. Use when writing, reviewing, or fixing TS/JS/TSX/JSX code, checking for a11y issues, linting errors, type safety problems, or when the user mentions code quality, formatting, accessibility, or best practices.
vercel-design-guidelines
by tylergibbs1
Check web interfaces against Vercel's design guidelines. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", "check my site against best practices", or "apply Vercel design guidelines".
wcag-audit-perceivable-color-blindness
by Jkense
Simulate how colors appear to users with different types of color blindness
frontend-design
by UholySmokes
Transform UI style requirements into production-ready frontend code with systematic design tokens, accessibility compliance, and creative execution. Use when building websites, web applications, React/Vue components, dashboards, landing pages, or any web UI requiring both design consistency and aesthetic quality.
ui-ux-guidelines
by tylergibbs1
Implementation details for accessible, performant interfaces. Use alongside vercel-design-guidelines for detailed technical guidance on interactions, animations, and forms.
shadcn/ui
by leonaaardob
Complete shadcn/ui documentation. Beautifully designed components built with Radix UI and Tailwind CSS. Copy-paste into your apps. Covers installation, components, theming, forms, charts, and framework integrations.
ux-ui-design
by josavicentevw
UX/UI Design skill for user research, wireframing, prototyping, visual design, interaction design, usability testing, accessibility, design systems, and responsive design. Use when designing user interfaces, conducting user research, creating design systems, evaluating usability, or when user mentions UX, UI, wireframes, prototypes, user flows, or accessibility.
wcag-audit-perceivable-color-contrast
by Jkense
Calculate WCAG contrast ratios for text and non-text elements
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.
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
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.
mariadb-best-practices
by jcastillotx
MariaDB database development standards. Triggers when working with MariaDB databases, Galera cluster, or MariaDB-specific features.
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."
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.