brand-perf-a11y-check

Audit brand web pages for performance and WCAG accessibility compliance.

Updated Aug 16, 2025
One-click install
npx skills add https://github.com/Tomy74-vsc/cliprace --skill brand-perf-a11y-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brand-perf-a11y-check
Source: https://github.com/Tomy74-vsc/cliprace/tree/main/.cursor/skills/brand-perf-a11y-check
Command: npx skills add https://github.com/Tomy74-vsc/cliprace --skill brand-perf-a11y-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps ensure that brand-facing pages and components meet essential performance and accessibility standards, preventing regressions and improving user experience.

Core Features & Use Cases

  • Performance Auditing: Checks for data fetching waterfalls, efficient Promise.all usage, and layout stability.
  • Accessibility Validation: Verifies focus management, ARIA attributes, keyboard navigation, and reduced motion support.
  • Library Scoping: Ensures heavy client-side libraries like framer-motion and lenis are used judiciously and code-split.
  • Use Case: After refactoring the checkout flow, use this skill to confirm that it loads quickly, is fully navigable via keyboard, and respects user preferences for reduced motion.

Quick Start

Run the brand-perf-a11y-check skill on the new user onboarding wizard.

Frequently Asked Questions about brand-perf-a11y-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit my web page for WCAG compliance and layout stability?

To audit web page accessibility and performance, validate keyboard navigation, ARIA attributes, focus management, and check for layout shifts. This ensures critical user journeys meet WCAG-aware baselines and maintain visual stability without unexpected layout shifts.

What is a data fetching waterfall and how do I check for it in my components?

A data fetching waterfall occurs when promises resolve sequentially instead of concurrently. You can check for this by auditing your components to ensure efficient Promise.all usage, verifying that critical data fetching operations execute in parallel to prevent performance bottlenecks.

Can I use this accessibility checklist to validate keyboard navigation and screen reader support?

Yes, this accessibility checklist validates focus management, ARIA attributes, keyboard navigation, and screen reader support. It checks brand-facing web components against WCAG compliance baselines to ensure critical user journeys are fully navigable without a mouse.

How do I ensure heavy animation libraries like framer-motion are code-split properly?

To ensure animation libraries are code-split properly, audit your client-side dependencies to verify judicious usage. This checks that heavy libraries like framer-motion and lenis are loaded efficiently and respects user preferences for reduced motion across brand-facing pages.

What's the best way to prevent performance regressions after refactoring a checkout flow?

The best way to prevent performance regressions is to run a focused audit on the refactored flow. This validates data fetching efficiency, checks for layout stability, and ensures no-waterfall baselines are met, confirming the checkout loads quickly and remains stable.

Does this performance audit check for reduced motion support on brand pages?

Yes, this performance audit explicitly checks for reduced motion support. It validates that brand-facing web pages and components respect user preferences by ensuring animation libraries are used judiciously and do not trigger unnecessary motion for sensitive users.