PanelUI

A React Native component library for Expo, styled with Tailwind CSS through Uniwind and animated on the UI thread with Reanimated. Pure TypeScript, no native modules, runs in Expo Go.

Run every CLI command with the project's own runner — npx panelui-cli@latest, pnpm dlx panelui-cli@latest or bunx panelui-cli@latest, matching its packageManager. Examples below use npx.

Is anything styled?

If the user says nothing is styled, className does nothing, the screen is blank, or Uniwind cannot find --color-background: go straight to setup.md. There is no error for this and it is a wrong path in metro.config.js almost every time. Do not start reading component code.

First, find out how this project consumes it

There are two ways in and they are both fully supported, so do not assume:

npx panelui-cli@latest mcp   # the MCP server, if the agent supports it

or, without MCP, read package.json and look for panelui.json:

If neither is there, the project has not installed it: npx create-panelui-app@latest for a new app, or setup.md for an existing one. Do not hand-write component source into a project that has not been set up — nothing will be styled, and the reason will not be obvious.

Principles

1. Look before you build. components.md lists every one of them, and there are more than a hundred. Search it before writing custom UI — a "custom" sheet, picker, chart or chat transcript is almost always one that exists.
2. Read the props from this skill, not from memory. Every component has a file at components/<slug>.md with its anatomy, every prop with its type and default, its variants and its parts, generated from the library's TypeScript. Read the one you are about to use. A remembered prop name usually is not right, and nothing here needs a network request.
3. Compose the parts. A settings screen is Frame + Frame.Panel + Frame.Row. A chat is MessageScroller + Message. recipes.md has those screens written out. Reach for a compound part before a View.
4. Never hardcode a colour. Every colour is a semantic token — bg-card, text-muted-foreground, border-border. A literal breaks all six themes at once.

Critical rules

Each links to a file with wrong/right pairs.

Styling → rules/styling.md

• Semantic tokens only. bg-card, not bg-neutral-900. No dark: overrides — the token already knows, and dark: does not resolve at all inside the named themes.
• gap-*, never space-y-*. React Native has no space-*.
• className is for layout, not for restyling a component's colours or type.
• cn() for conditional classes, not template-literal ternaries.
• Resolve a dynamic colour with useCSSVariable, never by reading a hex out of the theme.
• A new arbitrary value needs a restart. h-[330px] in a file a running dev server started before compiles to nothing — no error, no warning, the element silently loses the property.

Composition → rules/composition.md

• PanelUIProvider at the root, exactly one. Overlays render into its portal host; without it Dialog, BottomSheet, Popover, Select and Toast mount and never appear.
• Compound parts belong to their root. Card.Header inside Card, Select.Item inside Select.Content. Using one outside throws with the part's name.
• Overlays take open + onOpenChange, or run uncontrolled with defaultOpen. Do not conditionally render an overlay to close it — it has an exit animation to finish.
• A field is Field + Label + the control, not a View with a Text above it.

Animation → rules/animation.md

• Reanimated 4 only. Never React Native's core Animated — the two do not compose, and core Animated puts the work back on the JS thread, which is the thing this library is for.
• Shared values and useAnimatedStyle, not state in an animation loop.
• tv() at module scope, never inside render.

Native controls → rules/native.md

• "Native" means Liquid Glass on iOS. native alone is not enough — pass glass too.
• A native control ignores className and every token. The platform owns its look; spacing has to come from the container.
• Never host elements inside a labelled native button. It has no definite width, and the app dies in native code where a JS try cannot catch it.

The theme

Six themes in three families — Panel, Moon, Grass — each in light and dark. A family sets its own radius scale as well as its palette, so switching one changes the shape of the UI too. Switch at runtime with useThemeMode(); named themes have to be listed in extraThemes in metro.config.js first, and the dev server restarted. See theming.md.

Adding a component

npx panelui-cli@latest add bottom-sheet     # copies the source in
npx panelui-cli@latest list                 # everything available

Nothing to install when the project uses the package — import it and go. Full command reference in cli.md; the MCP server and its tools in mcp.md.

Which component

The full list, with a line on each and a link to its reference, is in components.md. The common cases:

Detailed references

• setup.md — installing it, and every reason nothing is styled
• components.md — every component, and a file each with its full API
• recipes.md — whole screens: settings, form, chat, filters, list, chart, search
• hooks.md — the hooks, utilities, theme API and primitives
• theming.md — tokens, the three families, radius, useCSSVariable
• cli.md — init, add, list, mcp, panelui.json, the registry
• mcp.md — the MCP server and its six tools
• rules/styling.md, rules/composition.md, rules/animation.md, rules/native.md

Everything above is in this folder. The documentation is also on the web, as markdown, if a page with every example is wanted: https://panelui.dev/llms.mdx/<group>/<slug>, indexed at https://panelui.dev/llms.txt.