Loading...
Loading...
Found 86 Skills
Sense accessibility barriers with gentle awareness. Listen to the forest, scan for obstacles, test the paths, guide toward inclusion, and protect all wanderers. Use when auditing accessibility, testing for a11y, or ensuring inclusive design.
UI testing with Playwright and Puppeteer -- browser automation, visual regression, screenshots, and accessibility audits.
Frontend PR checklist for React, Next.js, Vue.js, Tailwind CSS, and React Query (F1–F16). Use when user says "frontend review", "review my React/Vue PR", "check my UI code", working in a frontend repo, or when the diff contains .tsx/.vue/.css files. For the full review workflow, use pr-review.
Used when accessibility audits are required or when implementing WCAG 2.2 (including ARIA, keyboard accessibility, and screen reader support).
Comprehensive accessibility patterns for building, testing, and fixing accessible interfaces. Use when building UI components, forms, pages, or auditing code for accessibility issues.
Audits web UI quality across accessibility, interaction, forms, typography, navigation, layout, performance, motion, and microcopy. Use when reviewing or refining frontend UI before merge or release, or when the user asks for a UI, UX, or accessibility audit.
Checklist covering accuracy, style, accessibility, and localization requirements for documentation releases.
Design System Governance Workflow for auditing, refactoring, and syncing enterprise design systems, design tokens, Figma variables, and developer handoff outputs.
Audit a live page for accessibility issues and locate each violation precisely — optionally pass a URL (e.g. `accesslint:scan https://example.com/dashboard`), otherwise ask for one. Ensures a debuggable Chrome, runs the @accesslint/core engine via CDP, and returns a worklist of live-DOM WCAG violations grounded to each violation's DOM selector and source file:line. Locates; doesn't edit — output drives fixes by Claude. Use it for "is this page accessible", or to verify a UI change. For diffing against uncommitted changes or a branch, use the `diff` skill.
Review implementation quality — catch visual bugs, placeholder text, broken links, and spec drift that functional tests miss. Use this after tests pass to ensure the output looks right, not just works right.
Transform an existing website/app UI into a futuristic cyberpunk, neon, space, or digital-dark theme with user-adjustable colors. Use when asked to reskin the UI, dark theme, cyberpunk style, or make the interface futuristic. Don't use for building a UI from scratch, pure light/minimal themes, or backend/API changes.
Find and fix WCAG 2.2 accessibility issues. Two modes — report (sweep a codebase or page, produce a prioritized written report, no edits) and fix (audit→edit→verify loop on a target). Prefers direct-CDP live-DOM auditing; falls back to a browser-MCP composition or HTML-string audits.