building-frontend-components

Standardize accessible frontend component development with React, Vue, or Svelte.

1|Updated Oct 12, 2025
One-click install
npx skills add https://github.com/sunmin-oss/sunmin-oss --skill building-frontend-components-sunmin-oss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: building-frontend-components
Source: https://github.com/sunmin-oss/sunmin-oss/tree/main/.copilot/skills/building-frontend-components
Command: npx skills add https://github.com/sunmin-oss/sunmin-oss --skill building-frontend-components-sunmin-oss

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents common frontend pitfalls like accessibility violations, inconsistent styling, and technical debt by enforcing a rigorous pre-implementation checklist and standardized component patterns.

Core Features & Use Cases

  • Accessibility Enforcement: Ensures all components meet WCAG standards, including focus traps for modals and proper ARIA labeling for forms.
  • Design System Integration: Promotes the use of design tokens and semantic HTML to maintain visual and technical consistency across the codebase.
  • Use Case: When building a new login modal, this Skill guides you through the necessary focus management, keyboard interaction planning, and error state handling before a single line of code is written.

Quick Start

Use the building-frontend-components skill to plan the implementation of a new accessible dropdown menu component.

Frequently Asked Questions about building-frontend-components

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

FAQPage Schema
How do I build accessible React components that meet WCAG standards?

To build accessible React components that meet WCAG standards, enforce a pre-implementation checklist for semantic HTML structure, proper ARIA labeling, and focus management before writing code. This prevents common accessibility violations and technical debt.

What's the best way to manage focus traps in frontend modals?

The best way to manage focus traps in frontend modals is to standardize component patterns using a pre-implementation checklist. This ensures proper focus management, keyboard interaction planning, and consistent state handling across complex interactive elements.

Does this UI component workflow support Vue and Svelte?

Yes, this UI component workflow supports Vue and Svelte. It standardizes the development of accessible and maintainable frontend components across React, Vue, or Svelte while enforcing strict adherence to design systems and WCAG compliance.

How do I integrate design tokens into a web development workflow?

To integrate design tokens into a web development workflow, use standardized component patterns that promote semantic HTML and design system integration. This maintains visual and technical consistency across your codebase while handling complex interactive elements.

Why does my dropdown menu fail keyboard navigation tests?

Your dropdown menu fails keyboard navigation tests due to inconsistent state handling and lack of focus management. Planning keyboard interactions, semantic HTML structure, and ARIA labeling before implementation resolves these accessibility violations.

When do I need strict design system compliance for frontend components?

You need strict design system compliance for frontend components when building production-ready UI elements requiring consistent state handling, focus management, and WCAG accessibility. This prevents inconsistent styling and technical debt across complex interactive elements.