gluestack-ui-v4:variants

Define and manage custom variants for gluestack-ui v4 components.

1|Updated Mar 25, 2025
One-click install
npx skills add https://github.com/jeius/LactaLink --skill gluestack-ui-v4-variants-jeius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gluestack-ui-v4:variants
Source: https://github.com/jeius/LactaLink/tree/main/.agents/skills/gluestack-ui-v4/variants
Command: npx skills add https://github.com/jeius/LactaLink --skill gluestack-ui-v4-variants-jeius

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides teams to design and implement robust, reusable variants for Gluestack UI v4 components, reducing duplication and ensuring consistent behavior across projects.

Core Features & Use Cases

  • Workflow for assessing when to create a variant and deciding between base, extended, and custom variants.
  • Guidance on using tva for type-safe, composable variants across multiple dimensions (variant, size, state).
  • Examples for extending existing components, creating compound variants, and implementing parent-child variant relationships for cohesive design systems.
  • Best practices for semantic tokens, default variants, and testing across themes (including dark mode).

Quick Start

Define a simple variant using tva for a base component and apply it in your project.

Frequently Asked Questions about gluestack-ui-v4:variants

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

FAQPage Schema
How do I create type-safe variants for gluestack-ui v4 components?

Type-safe variants for gluestack-ui v4 are created using tva to define composable variant dimensions across base, extended, and custom components, ensuring consistency and reusability across your design system.

What is the best way to manage parent-child variant relationships in a design system?

Managing parent-child variant relationships involves defining cohesive compound variants using tva, allowing parent components to dictate nested child component states and styles for scalable design system architecture.

When should I use base variants versus extended variants in gluestack-ui?

Base variants should be used for core component styling, while extended variants are applied when adding specific dimensions like size or state, preventing duplication and maintaining consistent behavior across projects.

Does tva support semantic tokens and dark mode testing for tailwind variants?

Yes, tva supports semantic tokens and enables robust variant implementations that require testing across themes, including dark mode, to ensure type-safe and consistent behavior across different visual states.

How do I define multiple variant dimensions like size and state using tva?

Multiple variant dimensions are defined using tva by specifying composable configurations for size, state, and variant properties, ensuring type-safe validation and default fallbacks for your UI components.