Guidelines for writing consistent React components, choosing the right UI primitives, and applying modular styling.
Install
mkdir -p .claude/skills/react && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/627" && unzip -o skill.zip -d .claude/skills/react && rm skill.zipInstalls to .claude/skills/react
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
LobeHub React component conventions. Use when editing TSX UI, choosing base-ui vs @lobehub/ui vs antd, styling with antd-style, routing, desktop variants, layouts, or component state.Key capabilities
- →Develop React components using TSX
- →Select appropriate UI primitives from base-ui or antd
- →Implement styling with createStaticStyles
- →Manage routing with react-router-dom
- →Sync desktop variants for Electron
How it works
The skill enforces a component hierarchy that prioritizes headless base-ui primitives over higher-level wrappers, ensuring consistent styling and state management.
Inputs & outputs
When to use react
- →Create a new UI component
- →Implement component styling
- →Select appropriate UI primitives
- →Refactor component structure
About this skill
React Component Writing Guide
Styling
| Scenario | Approach |
|---|---|
| Files already on StyleX, and new SPA styles | stylex.create + @lobehub/ui/stylex/cssVar.stylex / @lobehub/ui/stylex/media.stylex. The SPA compiler is plugins/vite/stylex.ts (@stylexjs/unplugin, prefix lh). Do not copy those token modules into the app. |
| Existing styles not yet migrated | createStaticStyles + cssVar.* (zero-runtime, module-level) |
| Simple one-off | Inline style attribute |
Truly dynamic (JS color fns like readableColor/chroma) | createStyles + token — last resort |
StyleX
- New code may not import
createStaticStyles/createStyles/css/keyframes/createGlobalStyle/injectGlobalfrom@lobehub/ui(stylex-migration/no-emotion-styles). Files still on them are listed inscripts/stylexMigration/legacyFiles.json; after migrating one, runbun run stylex:migration --prune-legacy. Never add entries. - Migrate a whole file at once. StyleX longhand rules carry raised specificity (
.x:not(#\#)) and beat emotion classes on the same element, but StyleX shorthand rules do not, so a half-migrated element resolves by property. - Element that also forwards a caller's
className/style:{...sx([styles.root, active && styles.active], className, style)}from@/styles/sx. Spreadingstylex.propsnext toclassNamefails@stylexjs/no-conflicting-props. - Component that lets callers restyle it: take
xstyle?: StyleXStylesand pass it last in thesx/stylex.propsarray. A plainclassNamefrom outside cannot override StyleX rules. Passing a class to@lobehub/uicomponents (className,classNames) works, because lobe-ui CSS sits in@layer lobe-ui. - Values follow
@stylexjs/valid-styles: no multi-value shorthands (margin: '0 8px'→marginBlock/marginInline), and stringflex(flex: '1'). background,animation,borderandborder{Top,Right,Bottom,Left}shorthands compile to no class at all, whatever the value (border: 'none'included), without an error. Write longhands:backgroundColor(plusbackgroundImage: 'none'when replacing abackgroundshorthand),animationName/animationDuration/ …,borderWidth/borderStyle/borderColor.- Check a migration in dev with the DevDock snapshot helper: on the migrated page run
__lobeStyleSnapshot.capture('<name>', '<root selector>'), back up the migrated files with their relative paths into a fresh directory (BACKUP=$(mktemp -d) && rsync -R <paths> "$BACKUP/"), swap in the originals (git checkout HEAD -- <paths>), reload, run__lobeStyleSnapshot.compare('<name>'), then restore the migrated files (cp -R "$BACKUP"/. ./). Do not usegit stash: every checkout shares one stash stack, and apushwith nothing to save creates no entry, so the nextpopapplies an older one. Each pair reads[captured, current], here[migrated, original]. It lists elements and::before/::afterwhose tracked computed styles, box (relative to the root) or text differ; an empty list means those match, not that hover, focus or closed dialogs were checked, so open each state you migrated and compare it too. Keep the window size, scroll everything under the root back to the start, and move the pointer off the compared area. bun run stylex:migration --list <A|B|C|D>lists files by how hard they are to move: A flat, B self pseudo-classes, C descendant / ancestor coupling (usestylex.defaultMarker()+stylex.when.ancestor()orxstyle), D tag / third-party DOM selectors (scoped plain CSS).
Component Priority
src/components— project-specific reusable components@lobehub/ui/base-ui— headless primitives. If the component lives here, use it. Do NOT import the same-named root export.@lobehub/ui— higher-level / antd-wrapping components (only when no base-ui equivalent)- antd — only when neither base-ui nor
@lobehub/uiroot provides it - Custom implementation — true last resort
If unsure about available components, search existing code or check node_modules/@lobehub/ui/es/index.mjs and node_modules/@lobehub/ui/es/base-ui/.
@lobehub/ui/base-ui — always prefer for these
| Component | Import |
|---|---|
Alert (+ AlertProps) | import { Alert, type AlertProps } from '@lobehub/ui/base-ui'; |
Select (+ SelectProps, SelectOption) | import { Select } from '@lobehub/ui/base-ui'; |
Modal (imperative API) | import { createModal, confirmModal, useModalContext, type ModalInstance } from '@lobehub/ui/base-ui'; |
DropdownMenu | import { DropdownMenu } from '@lobehub/ui/base-ui'; |
ContextMenu | import { ContextMenu } from '@lobehub/ui/base-ui'; |
Popover | import { Popover } from '@lobehub/ui/base-ui'; |
ScrollArea | import { ScrollArea } from '@lobehub/ui/base-ui'; |
Switch | import { Switch } from '@lobehub/ui/base-ui'; |
Toast | import { Toast } from '@lobehub/ui/base-ui'; |
FloatingSheet | import { FloatingSheet } from '@lobehub/ui/base-ui'; |
Drawer | import { Drawer } from '@lobehub/ui/base-ui'; |
For Modal specifically, see the dedicated modal skill — use the imperative createModal({ content: … }) pattern over the legacy <Modal open … /> declarative pattern. base-ui has its own ModalHost already mounted in SPAGlobalProvider.
Common slip:
import { Select } from '@lobehub/ui'looks fine but it's the antd-backed Select. Use base-ui Select. Same forModal,DropdownMenu, etc.
@lobehub/ui root — use when base-ui has no equivalent
| Category | Components |
|---|---|
| General | ActionIcon, ActionIconGroup, Block, Button, Icon |
| Data Display | Avatar, Collapse, Empty, Highlighter, Markdown, Tag, Tooltip |
| Data Entry | CodeEditor, CopyButton, EditableText, Form, Input, InputPassword, SearchBar, TextArea |
| Layout | Center, DraggablePanel, Flexbox, Grid, Header, MaskShadow |
| Navigation | Burger, Menu, SideNav, Tabs |
State
Keep transient state in its smallest useful owner. Extract a custom hook when state transitions and handlers obscure rendering or form a reusable unit; do not extract solely because a component has a particular number of hooks.
Split a component only to establish a real state, reuse, render-update, or mountable-capability boundary. Do not split solely to make files smaller; when a file reaches the 1200-line limit in source-layout, find one of these boundaries rather than cutting at a line count. Decomposing a heavy domain feature into host-assembled atoms is owned by compose-atoms.
Popover Exits
An action inside popover content that leaves the popover must close it, or the popover stays over the destination (for example, a plan badge in the user panel navigating to /settings/plans).
- Navigation: a host whose content links or navigates keeps
openstate, callsuseCloseOnNavigate(open, () => setOpen(false))from@/hooks/useCloseOnNavigate, and passes the returned key to itsPopover. This covers links added later, including links from other files. The key matters when navigation hides the host in an<Activity>(the home sidebar): a hidden tree sets up no new effects, so the base-ui popup never finishes its exit animation and stays on screen until a remount removes it. - Modal handoff or a final pick: call
usePopoverContext().close()(or the host's setter) before ope
Content truncated.
When not to use it
- →Do not use next/link for SPA navigation
- →Avoid antd Spin component for loading
Prerequisites
Limitations
- →Requires manual sync of desktop variant files
- →Strict import hierarchy must be followed
How it compares
It mandates specific architectural patterns and sync rules for desktop variants that generic React guides do not address.
Compared to similar skills
react side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| react (this skill) | 34 | 4mo | No flags | Intermediate |
| zustand | 113 | 5mo | No flags | Intermediate |
| react-component-patterns | 3 | 3mo | No flags | Intermediate |
| zustand-5 | 8 | 9mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by lobehub
View all by lobehub →You might also like
zustand
lobehub
Zustand state management guide. Use when working with store code (src/store/**), implementing actions, managing state, or creating slices. Triggers on Zustand store development, state management questions, or action implementation.
react-component-patterns
HoangNguyen0403
Modern React component architecture and composition patterns.
zustand-5
prowler-cloud
Zustand 5 state management patterns. Trigger: When implementing client-side state with Zustand (stores, selectors, persist middleware, slices).
1k-state-management
OneKeyHQ
Jotai state management patterns — atoms, globalAtom, contextAtom, and persistence.
react-router-getting-started
ssrjkk
Getting Started for React-Router: initial setup and first steps
accessibility-compliance
wshobson
Implement WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns, and assistive technology support. Use when auditing accessibility, implementing ARIA patterns, building for screen readers, or ensuring inclusive user experiences.