skills.rest
lgerard314
lgerard314OFFICIAL
Explore all skills by this author →
GitHub

bad-oversize

Flag accessibility, correctness, and regression risks in React/Next.js component reviews.

Updated Aug 27, 2026
Search Tags:#accessibility#frontend#quality#review#regression#guardrails
One-click install
npx skills add https://github.com/lgerard314/global-plugin --skill bad-oversize
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bad-oversize
Source: https://github.com/lgerard314/global-plugin/tree/main/scripts/fixtures/bad-oversize
Command: npx skills add https://github.com/lgerard314/global-plugin --skill bad-oversize

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviewers often miss accessibility and regression risks when evaluating frontend components, leading to usability issues and costly fixes post-release.

Core Features & Use Cases

  • Checklist-based review: Ensures accessibility, correctness, and regression risk coverage across frontend components.
  • Consistency across codebase: Applies to React/Next.js component libraries and UI primitives to standardize quality gates.
  • Use Case: During a code review of a new Button, verify keyboard navigation, color contrast, and regression indicators.

Quick Start

Run a thorough frontend review of a component and use this skill to flag accessibility and regression risks.

Frequently Asked Questions about bad-oversize

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

FAQPage Schema
How do I check accessibility and regression risks during a React code review?▼

To check accessibility and regression risks during a React component review, apply a checklist-based guardrail that flags keyboard navigation, color contrast, and structural correctness issues across your UI primitives.

What frontend review checks should I run for Next.js UI components?▼

Frontend review checks for Next.js UI components should verify accessibility best practices, structural correctness, and regression risk indicators to standardize quality gates across your shared component libraries.

Can I use this to enforce accessibility guardrails in a shared component library?▼

Yes, you can use this to enforce accessibility guardrails in a shared component library by applying standardized review criteria to React and Next.js primitives to catch usability issues before release.

Why do reviewers miss accessibility issues in frontend components?▼

Reviewers miss accessibility issues in frontend components because they often lack standardized guardrails, leading to overlooked keyboard navigation and color contrast problems that cause costly post-release fixes.

Does this frontend review skill work with custom React UI primitives?▼

Yes, this frontend review skill works with custom React UI primitives by applying defined review criteria to flag accessibility best practices and regression risk indicators during component evaluations.

Related Skills

Explore More Software Engineering Skills→
videojsvideojs
888

aria

Audit React UI components for ARIA accessibility and keyboard navigation.

Official
Basic
PrasadTelasulaPrasadTelasula

component-testing

Test React components with React Testing Library and Playwright for frontend correctness.

Community
Intermediate
bacocobacoco
57

Architecture QA & Tech Stack Governance

Validate implementation plans against approved architecture and tech stack standards.

Community
Advanced
leboncoinleboncoin
92

check-accessibility

Automate WCAG 2.1 AA accessibility testing of Spark UI components with Playwright.

Official
Intermediate