What is gluestack-ui-v4:validation?

A checklist for reviewing applications built with gluestack-ui version 4, a component library for React and React Native interfaces.

Use it during code review or validation of gluestack-ui v4 screens and components.

It helps catch incorrect component usage, styling choices, imports, provider setup, and other known implementation mistakes.

gluestack-ui-v4:validation — Skill for Claude Code and Codex by gluestack: A checklist for reviewing applications built with gluestack-ui ve

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/gluestack/agent-skills/validation

Any agent

npx skills add gluestack/agent-skills --skill validation

Clone the repo

git clone --depth 1 https://github.com/gluestack/agent-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/gluestack/agent-skills/validation.svg)](https://agentmods.dev/skills/gluestack/agent-skills/validation)

Your own site

<a href="https://agentmods.dev/skills/gluestack/agent-skills/validation"><img src="https://agentmods.dev/badge/skills/gluestack/agent-skills/validation.svg" alt="Measured on agentmods" height="20"></a>

Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 4,341 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00037	$0.04341
Opus 5	$0.00018	$0.02171
Sonnet 5	$0.00007	$0.00868
Haiku 4.5	$0.00004	$0.00434

Measured 3d ago against content hash 07e9df73e068, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

gluestack-ui-v4:validation scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/gluestack-ui-v4/validation/SKILL.md · 562 lines

How it starts

The opening of the file, as written. The whole thing — 562 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Gluestack UI v4 - Validation & Anti-Patterns

This sub-skill focuses on validating implementations, identifying anti-patterns, and ensuring code quality for gluestack-ui v4.

Validation Checklist

When reviewing code, check for:

Component Usage

Component usage verified against official v4 docs at https://v4.gluestack.io/ui/docs/components/${componentName}/
All React Native primitives replaced with Gluestack components
Components imported from local @/components/ui/ directory
GluestackUIProvider wraps the app

Component Props vs className

Component props used instead of className when available:
- VStack/HStack use space prop instead of gap-* className
- Button uses variant and size props instead of className
- Heading/Text use size prop instead of text-* className
- Heading/Text use bold prop instead of font-bold className
- Other component props used where applicable

Styling

CRITICAL: All colors use ONLY semantic tokens - NO exceptions:
- No typography-* tokens (use text-foreground, text-muted-foreground)
- No neutral-* tokens (use semantic equivalents)
- No gray-* or slate-* tokens (use semantic equivalents)
- No numbered colors: red-500, blue-600, green-400
- No arbitrary values: [#3b82f6], [#DC2626]
- No opacity utilities (use alpha values: /70, /90)
All spacing values use the standard scale (no arbitrary values)
No inline styles where className can be used
Dark mode support using dark: prefix (semantic tokens ensure compatibility)
Variants defined using tva when needed
className properly merged in custom components

Compound Components

Compound components used correctly:
- InputIcon always wrapped in InputSlot (CRITICAL)
- ButtonText used for all button text content
- FormControl sub-components used (FormControlLabel, FormControlError, etc.)
- Card sub-components used (CardHeader, CardBody, CardFooter)
- Checkbox sub-components used (CheckboxIndicator, CheckboxIcon, CheckboxLabel)
- All other component sub-components as per official docs

Read the full file on GitHub · 562 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

3d ago First seen · 562 lines · 37 tokens per session scan A 07e9df73e068

Subscribe to this mod's changes

gluestack-ui-v4:validation is a skill published in the GitHub repository gluestack/agent-skills (1 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 4,341 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Code review Frontend

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens