frontend-ui-engineering

Construct accessible React user interfaces with design system tokens.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/fsolla/teqo --skill frontend-ui-engineering-fsolla
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: frontend-ui-engineering
Source: https://github.com/fsolla/teqo/tree/main/.agents/skills/frontend-ui-engineering
Command: npx skills add https://github.com/fsolla/teqo --skill frontend-ui-engineering-fsolla

SYSTEM DOCUMENTATION & REQUIREMENTS

πŸ’‘ This Skill includes references (resource) components.

What problem does it solve?

This skill eliminates the gap between AI-generated code and production-ready interfaces by enforcing design system adherence, accessibility standards, and professional component architecture.

Core Features & Use Cases

  • Component Architecture: Implements modular, composable UI patterns that prioritize maintainability and separation of concerns.
  • Accessibility & UX: Ensures full WCAG 2.1 AA compliance, including keyboard navigation, focus management, and semantic HTML.
  • Design System Enforcement: Prevents generic AI aesthetics by mandating the use of project-specific design tokens, spacing scales, and typography hierarchies.

Quick Start

Use the frontend-ui-engineering skill to build a new accessible task list component that follows the project design system and includes proper loading and empty states.

Frequently Asked Questions about frontend-ui-engineering

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

FAQPage Schema
How do I build accessible React components that meet WCAG 2.1 AA standards?β–Ό

To build accessible React components meeting WCAG 2.1 AA standards, you enforce semantic HTML structure, implement robust keyboard navigation, and apply strict focus management to ensure full usability for production interfaces.

What's the best way to enforce a design system in frontend UI engineering?β–Ό

Enforcing a design system in frontend UI engineering requires mandating the use of project-specific design tokens, spacing scales, and typography hierarchies to prevent generic AI aesthetics and maintain consistent visual hierarchy.

How do I structure modular React components for production environments?β–Ό

Structuring modular React components for production environments involves implementing composable UI patterns that prioritize maintainability and separation of concerns to refine existing UI elements effectively.

Can I use this approach to create responsive layouts with proper loading and empty states?β–Ό

Yes, you can construct responsive layouts with proper loading and empty states by applying modern React patterns to build accessible task list components that satisfy strict production environment requirements.

Why does AI-generated frontend code often fail in production applications?β–Ό

AI-generated frontend code often fails in production because it lacks strict design system adherence, misses WCAG 2.1 AA accessibility standards, and ignores professional component architecture needed for maintainable interfaces.

Do I need specific dependencies to implement responsive UIs with design system tokens?β–Ό

No specific dependencies are required to implement responsive UIs with design system tokens, as the approach focuses on applying modern React patterns and modular architecture directly to your existing project setup.