Accessibility
Accessibility testing and improvements
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.
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.
audit
by educlopez
"Technical UI audit — a11y, performance, responsive. Produces a prioritized findings table. Invoke when the user asks for audit on their UI, or mentions 'audit' alongside design / UI / frontend work."
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
platform-conformance
by srobroek
Checks a surface against its platform's own design guidelines. Triggers on does this follow HIG or Material or platform conventions.
accessibility-wcag-patterns
by Hack23
WCAG 2.1 AA compliance, ARIA attributes, keyboard navigation, screen reader optimization for accessible political data platforms
agentic-ui-qa
by HomenShum
Universal QA + dogfooding protocol for agentic application UIs (worked profiles included for NodeBench AI, NodeRoom Live, NodeSlide/parity-studio; template for any app). Use when asked to QA, dogfood, verify, regression-test, or "revamp the agent UI" of ANY app — it drives the UI end to end as personas, verifies every claim with artifacts, scores the app against the Agentic UI Bar, and runs the bounded fix-revamp loop. Agent- and model-agnostic — a literal floor any small model can execute, an additive ceiling that scales with stronger models.
angular
by yldgio
Angular component architecture, RxJS patterns, change detection, and module organization
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."
web-ui-best-practices
by heykvnzhao
Opinionated constraints for building better user interfaces. Triggers on building or reviewing web components, pages, forms, modals, animations, or any frontend UI work. Covers accessibility, focus states, touch interactions, and performance.
ui-ux-design
by htooayelwinict
Design and implement UI/UX changes using existing components and Tailwind tokens; ensure accessibility. EXCLUSIVE to ui-ux-designer agent.
ui-ux
by Dsantiagomj
UI/UX design principles for beautiful, accessible, user-centered interfaces. Trigger: When designing components, when implementing UI, when reviewing visual design, when suggesting design improvements, when validating user experience, when choosing design patterns.
수리 — 펫나 자동 개선형 개발자 (상시 개선 엔진)
by crossx362-commits
대기로 승격시켜준다.
a11y
by politician
Expert web accessibility auditing + remediation for French RGAA 4.1.2 and WCAG 2.1.---
accessibility-wcag
by slurpyb
Enforce WCAG 2.2 accessibility standards. Use when creating UI components, reviewing frontend code, or when accessibility issues are detected. Covers semantic HTML, ARIA, keyboard navigation, and color contrast.
ui-ux-pro-max
by yuanxiao0115
"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples."
navigation-patterns
by moderndegree
Navigation patterns, breadcrumbs, tabs, sidebars, and user flows. Use when building navigation, menus, or site architecture.
brand-guidelines
by TheWatcher01
Applies consistent brand colors, typography, and visual identity to any output (documents, slides, web pages, components). Use when brand colors, style guidelines, visual formatting, or company design standards need to be applied.
a11y-checklist
by AGilbertDev
WCAG 2.2 AA checklist for Nuxt pages and Vue components, covering keyboard, focus, ARIA, contrast, media, forms, and structure. Use when a page or interactive component ships, or when keyboard or screen-reader behaviour is broken.
Laurence — WCAG 2.2 Reference
by LaurenceRLewis
Reference this skill for ANY accessibility-related question, task, or code — no exceptions. Triggers include: WCAG questions ("does X pass WCAG?", "which success criterion applies?", "what level is this?"), accessibility audits of code or designs, building or reviewing accessible components, explaining what a WCAG 2.2 success criterion means or requires, checking conformance levels (A, AA, AAA), and any mention of a11y, ARIA, screen readers, keyboard navigation, colour contrast, focus management, or assistive technology. Also triggers for code tasks involving HTML, CSS, React, Vue, or any frontend component where accessibility compliance should be verified. Non-negotiable: if accessibility is relevant to the task, consult this skill first.