base-ui

Consults official Base UI documentation before implementing or reviewing components.

Updated Dec 21, 2025
One-click install
npx skills add https://github.com/Angael/veles --skill base-ui-angael
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: base-ui
Source: https://github.com/Angael/veles/tree/main/.agents/skills/base-ui
Command: npx skills add https://github.com/Angael/veles --skill base-ui-angael

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When building or debugging UI with the Base UI library, relying on memory or outdated snippets leads to incorrect props, broken accessibility, and custom workarounds for behavior the library already handles. This Skill directs the AI to Base UI's official documentation as the source of truth before writing or reviewing component code. ## Core Features & Use Cases - Documentation-first workflow: Starts from the Base UI llms.txt documentation index and opens the relevant component or handbook page before answering. - Version-aware verification: Confirms APIs against the project's installed Base UI version when version differences may matter. - Library-native implementations: Prefers documented props and behavior over custom state, event handlers, timers, or accessibility logic. - Use Case: While implementing a Base UI Dialog, the Skill checks the official docs for the correct controlled-state props instead of inventing custom open/close handling. ## Quick Start Ask the AI to implement or review a Base UI component using the official Base UI documentation as the reference.

Frequently Asked Questions about base-ui

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

FAQPage Schema
How do I implement Base UI components correctly?

Start from the Base UI documentation index at base-ui.com/llms.txt, then open the relevant component or handbook page. Use the documented props and behavior rather than writing custom state, event handlers, or timers.

How do I debug a Base UI component that behaves unexpectedly?

Check the official Base UI documentation for the component's documented behavior first, since the library often handles state and accessibility natively. Custom overrides of documented behavior are a common source of bugs.

Does Base UI handle accessibility logic automatically?

Base UI components ship with built-in accessibility behavior documented in the official docs. Prefer the library's documented behavior over adding your own accessibility logic, which can conflict with the built-in handling.

How do I handle Base UI version differences in my project?

Confirm component APIs against the Base UI version installed in your project when version differences may matter. Documentation pages may reflect a newer release than the one your project depends on.

When should I write custom state logic for Base UI components?

Only after confirming the library does not already provide the behavior through documented props. The Skill's guidance is to prefer documented props and behavior over custom state, event handlers, or timers.