gluestack-ui-v5:validation

Validates gluestack-ui v5 implementations against checklists and anti-patterns for Tailwind CSS v4 projects.

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/sombek/fitness-guidance-app --skill gluestack-ui-v5-validation-sombek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gluestack-ui-v5:validation
Source: https://github.com/sombek/fitness-guidance-app/tree/main/mobile/.agents/skills/gluestack-ui-v5/validation
Command: npx skills add https://github.com/sombek/fitness-guidance-app --skill gluestack-ui-v5-validation-sombek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing React Native code built with gluestack-ui v5 is error-prone because developers commonly mix React Native primitives with Gluestack components, use non-semantic color tokens that break dark mode, skip required compound sub-components, or misconfigure Tailwind v4 tooling. This Skill provides a structured validation checklist and anti-pattern catalog to catch these issues during code review. ## Core Features & Use Cases - Validation Checklist: Systematic checks covering component usage, semantic color tokens, compound components, icons, cross-platform compatibility, and performance. - Anti-Pattern Catalog: Side-by-side incorrect and correct code examples for common mistakes like missing ButtonText, unwrapped InputIcon, inline styles, and ScrollView-based long lists. - Tailwind v4 Migration Checks: Flags legacy patterns such as tailwind.config.js, @tailwind directives, and missing lightningcss pins specific to NativeWind v5. - Use Case: During a pull request review of a React Native screen, run through the checklist to confirm all colors use semantic tokens like text-foreground and bg-primary, all buttons include ButtonText, and long lists use FlatList instead of ScrollView. ## Quick Start Review my gluestack-ui v5 component code and identify any anti-patterns or violations of the semantic token and compound component rules.

Frequently Asked Questions about gluestack-ui-v5:validation

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

FAQPage Schema
How do I validate gluestack-ui v5 code during code review?

Use the validation checklist covering component usage, semantic color tokens, compound components, and performance. Verify components come from the local @/components/ui/ directory, all colors use semantic tokens like text-foreground, and sub-components such as ButtonText and InputSlot are present.

What color tokens are allowed in gluestack-ui v5 with Tailwind v4?

Only semantic tokens are allowed, such as text-foreground, bg-primary, bg-muted, and border-border. Prohibited tokens include typography-*, neutral-*, gray-*, slate-*, numbered colors like red-500, arbitrary hex values, and opacity utilities; use alpha values like /70 instead.

Why does my gluestack-ui Input icon not render correctly?

InputIcon must always be wrapped inside an InputSlot component. Placing InputIcon directly inside Input without InputSlot is a critical error that breaks rendering and styling.

Does gluestack-ui v5 still use tailwind.config.js?

No. Tailwind CSS v4 is CSS-first, so tailwind.config.js is ignored and should be deleted. Configuration moves to global.css using @theme inline, and NativeWind v5 requires postcss.config.js with the @tailwindcss/postcss plugin plus a pinned lightningcss version.

Should I use ScrollView or FlatList for long lists in React Native?

Use FlatList for long lists because it virtualizes rendering and only mounts visible items. ScrollView with map renders all items at once, causing poor performance and high memory usage on large datasets.