ui-library-usage-auditor

Audit shadcn/ui component usage for accessibility and design-system conformance.

6|Updated Nov 11, 2025
One-click install
npx skills add https://github.com/hopeoverture/worldbuilding-app-skills --skill ui-library-usage-auditor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ui-library-usage-auditor
Source: https://github.com/hopeoverture/worldbuilding-app-skills/tree/main/skills/ui-components/ui-library-usage-auditor
Command: npx skills add https://github.com/hopeoverture/worldbuilding-app-skills --skill ui-library-usage-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Audits shadcn/ui usage for accessibility, consistency, and design-system compliance across the codebase.

Core Features & Use Cases

  • Accessibility auditing for ARIA and labels
  • Consistency checks for component usage
  • Recommendations for component extraction
  • Layout and responsiveness review

Quick Start

Run an audit across the codebase to identify issues and suggested improvements.

Frequently Asked Questions about ui-library-usage-auditor

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

FAQPage Schema
How do I audit shadcn/ui components for accessibility issues?

Accessibility auditing for shadcn/ui identifies ARIA gaps, missing labels, and improper semantics across your codebase. Run the audit to detect components missing required attributes, incorrect role assignments, and keyboard navigation problems that violate accessibility standards.

Can I check if my shadcn/ui usage is consistent across the codebase?

Consistency checks for shadcn/ui usage reveal duplicate component patterns, divergent styling approaches, and non-standard implementations. The audit flags inconsistent patterns to help standardize component usage and reduce maintenance overhead.

What does a shadcn/ui design system compliance audit check?

Design system compliance auditing verifies that shadcn/ui components conform to your organization's patterns and guidelines. It identifies deviations, improper component combinations, and opportunities for component extraction to strengthen design system adherence.

How do I identify responsive and layout issues in shadcn/ui components?

Layout and responsiveness review evaluates how shadcn/ui components adapt across screen sizes and breakpoints. The audit surfaces components with problematic spacing, alignment, or breakpoint behavior that need refactoring.

When should I run a shadcn/ui audit during development?

Run audits during UI code reviews, before major refactors, and when adding new components to catch accessibility and consistency problems early. Regular auditing prevents design debt and ensures ongoing compliance with accessibility and design system standards.

What's the difference between a shadcn/ui audit and manual code review?

An automated audit systematically scans all component usage against accessibility, consistency, and design system criteria in a single pass. Manual review is slower and prone to missing patterns, while auditing provides comprehensive coverage and specific, actionable recommendations.