gea-ui-components

You can build accessible Tailwind UI components rapidly by importing pre-built widgets and primitives, which combine Tailwind styling with Zag.js state machines to ensure ARIA-compliant behavior and predictable interactions across browsers.

Zag.js state machines handle accessibility by powering behavior-rich widgets like Dialog, Tabs, and Toast, providing ready-to-use accessible primitives that ensure ARIA-compliant interactions and consistent state management across browsers.

The best way to add consistent design tokens to a Gea web application is using pre-built Tailwind-styled UI components, which provide ready-made primitives and predictable interactions to ensure cohesive theming throughout your app.

You do not need external dependencies to use these Tailwind-styled widgets, but you need a Skill's SKILL.md frontmatter with name and description, plus optional scripts, references, or assets directories to customize and extend behavior.

You can customize and extend the behavior of pre-built Gea UI components by utilizing optional scripts, references, and assets directories specified within the Skill's SKILL.md frontmatter configuration.

You should avoid using pre-built UI primitives when your web application requires highly custom interactions that fall outside standard ARIA-compliant behavior patterns, or when you need unique design tokens incompatible with Tailwind-based styling.