Accessibility
Accessibility testing and improvements
ui-ux-pro-max
by qdleader
"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."
seo-pro-max
by aycanozarpaci
Production-grade SEO implementation skill. Analyzes the existing project first, asks the user the right questions, and then implements every chosen SEO surface (meta tags, Open Graph, Twitter Cards, canonical, robots, sitemap, schema.org/JSON-LD, favicons, llms.txt, admin-panel wiring, database schema) exactly as the user decided. The skill is an EXECUTOR, not a decision-maker.
visual-keywords
by nweii
"Generate keyword-rich strings for visual references to optimize for fuzzy search and recall. Focuses on searchability and keyword matching rather than prose or alt text."
dogfood
by Russ534
"Exploratory QA of web apps: find bugs, evidence, reports."
web-design-guidelines
by mrmps
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".
angular-developer
by SeuPut0705
Generates Angular code and provides architectural guidance. Trigger when creating projects, components, or services, or for best practices on reactivity (signals, linkedSignal, resource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, or CLI tooling.
accessibility
by SeuPut0705
Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels, accessibility traits and hints, focus management, contrast, target size, and screen-reader support. Use when building or auditing UI for accessibility compliance, keyboard navigation, or screen-reader support.
validate-site-playwright
by boi6765
Render-validate the built Copilot Workshops site in a real browser using the Playwright MCP server. Use as an optional deeper QA pass — after the static checks in build-and-verify-docs — to confirm pages actually render. Trigger when asked to "validate the built site", "check the pages render", "do a browser/visual QA pass", or before opening a PR that changes rendered output.
motion-graphic
by SviluppoItaliaDigitale
Video divulgativi di protezione civile fatti interamente in codice (motion graphic) per social, sito e media, in più formati (9:16 Reel/TikTok/Storie/WhatsApp, 4:5 feed, 1:1, 16:9 YouTube/sito/TV). Usala ogni volta che l'utente chiede un video, un Reel, una clip, un'animazione, una "puntata" o un "motion graphic" illustrativo o divulgativo, anche senza nominare la skill.
ecc
by SeuPut0705
"Index of ECC language, framework and tool skills, read on demand: Go, Rust, Python, Django, FastAPI, Java, Spring Boot, Quarkus, Kotlin, Android, Swift, Flutter, C++, .NET, Laravel, Rails, Perl, React, Next.js, Vue, Angular, NestJS, databases, Docker, Kubernetes, security and LLM apps. Read it before writing, testing or reviewing code in one of these."
frontend-patterns
by SeuPut0705
Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices. Use when building or reviewing React or Next.js components, state, or render performance.
frontend-a11y
by SeuPut0705
Accessibility patterns for React and Next.js — semantic HTML, ARIA attributes, form labeling, keyboard navigation, focus management, and screen reader support. Use when building or reviewing forms, modals, dropdowns, tooltips, or tabs, fixing a11y lint or code-review findings, or wiring up keyboard navigation and focus management.
flutter-dart-code-review
by SeuPut0705
Library-agnostic Flutter/Dart code review checklist covering widget best practices, state management patterns (BLoC, Riverpod, Provider, GetX, MobX, Signals), Dart idioms, performance, accessibility, security, and clean architecture. Use when reviewing Flutter or Dart code, whatever state management library the project uses.
ios-feature
by RunLumi
Implement or materially change a LinePaycheck native iOS feature. Use for SwiftUI screens, app state, navigation, adapters, StoreKit, persistence, OCR, export, or other iOS product work.
android-design-guidelines
by dirnbauer
Material Design 3 and Android platform guidelines. Use when building Android apps with Jetpack Compose or XML layouts, implementing Material You, navigation, or accessibility. Triggers on tasks involving Android UI, Compose components, dynamic color, or Material Design compliance.
ios-design-guidelines
by dirnbauer
Apple Human Interface Guidelines for iPhone. Use when building, reviewing, or refactoring SwiftUI/UIKit interfaces for iOS. Triggers on tasks involving iPhone UI, iOS components, accessibility, Dynamic Type, Dark Mode, or HIG compliance.
kanpeki
by fellipeutaka
"Use Kanpeki component library in React projects. Activate when user wants to add, use, customize, or compose accessible UI components from Kanpeki (@kanpeki/*). Covers installation, component patterns, forms, theming, and dark mode with React Aria Components + Tailwind CSS 4.1 + CVA."
web-design-guidelines
by jarrodwatts
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".
macos-accessibility
by martinholovsky
"Expert in macOS Accessibility APIs (AXUIElement) for desktop automation. Specializes in secure automation of macOS applications with proper TCC permissions, element discovery, and system interaction. HIGH-RISK skill requiring strict security controls."
Accessibility & WCAG Compliance Skill
by martinholovsky
Build interfaces that include everyone.
linux-at-spi2
by martinholovsky
"Expert in AT-SPI2 (Assistive Technology Service Provider Interface) for Linux desktop automation. Specializes in accessible automation of GTK/Qt applications via D-Bus accessibility interface. HIGH-RISK skill requiring security controls for system-wide access."
by diegosouzapw
LinkedIn integration for reading feed, profiles, connections, search results, and messages using browser automation
wicked-garden-draft
by mikeparcewski
The quality floor for DOCUMENT deliverables drafted from a repo — brochures, one-pagers, flyers, pages, decks, memos — design guidance plus one self-check run before "done". Three floors: (1) READABLE — every text/background pair ≥ 4.5:1 (WCAG AA; 3:1 for large text) on COMPOSITED colours, print text ≥ 7pt; (2) SIZED TO THE BRIEF — the RENDERED page count honours the brief's page budget (wrappers are not pages); (3) GROUNDED — every number, URL and claim cites a repo path, mocks visibly labelled, no placeholder ships. Use when: "draft a brochure / one-pager / flyer / product page / deck / memo about <repo>", "print-ready A4 / Letter", "make it two pages", "is this brochure readable / grounded", before declaring a wicked-interactive draft/edit/revision done, or as the skill a governed drafting run (wicked-crew interactive-*) follows. NOT for code documentation (the engineering documentarian) or a running app's accessibility audit (the product a11y action / the qe a11y engineer).
wicked-garden-qe-a11y-test-engineer
by mikeparcewski
Accessibility specialist — axe-core + pa11y, WCAG 2.1 AA / 2.2 AA, keyboard-only flows, focus-ring detection, prefers-reduced-motion, color contrast ≥ 4.5:1. Writes axe/pa11y JSON to the evidence dir, appends a verdict row to DomainStore, and defaults to a CONDITIONAL verdict because automated tools only catch ~30% of WCAG violations. Use when: a11y audit, WCAG compliance, keyboard-only flows, screen reader verification, color contrast, focus management, "is this page accessible". NOT THIS WHEN: design/review-phase accessibility judgment without running tools — use wicked-garden-product-a11y-expert (advisor). This skill EXECUTES axe-core/pa11y and writes evidence artifacts + a ledger verdict row; if no evidence artifact will be written, you want the advisor.