react

lobehub/lobe-chat · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/lobehub/lobe-chat --skill react
0 commentsdiscussion
summary

If unsure about component usage, search existing code in this project. Most components extend antd with additional props.

skill.md

React Component Writing Guide

  • Use antd-style for complex styles; for simple cases, use inline style attribute
  • Use Flexbox and Center from @lobehub/ui for layouts (see references/layout-kit.md)
  • Component priority: src/components > @lobehub/ui/base-ui > @lobehub/ui > custom implementation
    • Always prefer @lobehub/ui/base-ui primitives (Select, Modal, DropdownMenu, Popover, Switch, ScrollArea…) over antd equivalents
    • Fall back to @lobehub/ui higher-level components when base-ui has no match
    • Only implement a custom component as a last resort — never reach for antd directly
  • Use selectors to access zustand store data

@lobehub/ui Components

If unsure about component usage, search existing code in this project. Most components extend antd with additional props.

Reference: node_modules/@lobehub/ui/es/index.mjs for all available components.

Common Components:

  • General: ActionIcon, ActionIconGroup, Block, Button, Icon
  • Data Display: Avatar, Collapse, Empty, Highlighter, Markdown, Tag, Tooltip
  • Data Entry: CodeEditor, CopyButton, EditableText, Form, FormModal, Input, SearchBar, Select
  • Feedback: Alert, Drawer, Modal
  • Layout: Center, DraggablePanel, Flexbox, Grid, Header, MaskShadow
  • Navigation: Burger, Dropdown, Menu, SideNav, Tabs

Routing Architecture

Hybrid routing: Next.js App Router (static pages) + React Router DOM (main SPA).

Route Type Use Case Implementation
Next.js App Router Auth pages (login, signup, oauth) src/app/[variants]/(auth)/
React Router DOM Main SPA (chat, settings) desktopRouter.config.tsx + desktopRouter.config.desktop.tsx (must match)

Key Files

  • Entry: src/spa/entry.web.tsx (web), src/spa/entry.mobile.tsx, src/spa/entry.desktop.tsx
  • Desktop router (pair — always edit both when changing routes): src/spa/router/desktopRouter.config.tsx (dynamic imports) and src/spa/router/desktopRouter.config.desktop.tsx (sync imports). Drift can cause unregistered routes / blank screen.
  • Mobile router: src/spa/router/mobileRouter.config.tsx
  • Router utilities: src/utils/router.tsx

.desktop.{ts,tsx} File Sync Rule

CRITICAL: Some files have a .desktop.ts(x) variant that Electron uses instead of the base file. When editing a base file, always check if a .desktop counterpart exists and update it in sync. Drift causes blank pages or missing features in Electron.

Known pairs that must stay in sync:

Base file (web, dynamic imports) Desktop file (Electron, sync imports)
src/spa/router/desktopRouter.config.tsx src/spa/router/desktopRouter.config.desktop.tsx
src/routes/(main)/settings/features/componentMap.ts src/routes/(main)/settings/features/componentMap.desktop.ts

How to check: After editing any .ts / .tsx file, run Glob for <filename>.desktop.{ts,tsx} in the same directory. If a match exists, update it with the equivalent sync-import change.

Router Utilities

import { dynamicElement, redirectElement, ErrorBoundary } from '@/utils/router';

element: dynamicElement(() => import('./chat'), 'Desktop > Chat');
element: redirectElement('/settings/profile');
errorElement: <ErrorBoundary resetPath="/chat" />;

Navigation

Important: For SPA pages, use Link from react-router-dom, NOT next/link.

// ❌ Wrong
import Link from 'next/link';
<Link href="/">Home</Link>;

// ✅ Correct
import { Link } from 'react-router-dom';
<Link to="/">Home</Link>;

// In components
import { useNavigate } from 'react-router-dom';
const navigate = useNavigate();
navigate('/chat');

// From stores
const navigate = useGlobalStore.getState().navigate;
navigate?.('/settings');
how to use react

How to use react on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add react
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/lobehub/lobe-chat --skill react

The skills CLI fetches react from GitHub repository lobehub/lobe-chat and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/react

Reload or restart Cursor to activate react. Access the skill through slash commands (e.g., /react) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.864 reviews
  • Valentina Chawla· Dec 24, 2024

    Registry listing for react matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Jin Desai· Dec 20, 2024

    Keeps context tight: react is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Olivia Chen· Dec 20, 2024

    Useful defaults in react — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Aditi Smith· Dec 16, 2024

    We added react from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Ganesh Mohane· Dec 4, 2024

    Registry listing for react matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Ren Agarwal· Nov 11, 2024

    I recommend react for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Valentina Lopez· Nov 7, 2024

    react fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Valentina Haddad· Oct 26, 2024

    react is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Mateo Choi· Oct 2, 2024

    react reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Piyush G· Sep 21, 2024

    Solid pick for teams standardizing on skills: react is focused, and the summary matches what you get after install.

showing 1-10 of 64

1 / 7