react 是做什麼的？
LobeHub React 組件約定。用於編輯 TSX UI、選擇 base-ui 與 @lobehub/ui 與 antd、使用 antd-style 進行樣式設計、路由、桌面變體、佈局或組件狀態。
LobeHub React 組件約定。用於編輯 TSX UI、選擇 base-ui 與 @lobehub/ui 與 antd、使用 antd-style 進行樣式設計、路由、桌面變體、佈局或組件狀態。
此技能定義了 LobeHub 專案中 React 組件的開發約定，涵蓋從 UI 框架選擇到樣式設計、路由、佈局及狀態管理的完整流程。它為開發者提供了清晰的指引，幫助在 base-ui、@lobehub/ui 和 antd 等不同 UI 庫之間做出選擇，並推薦使用 antd-style 進行樣式開發。技能同時規範了路由配置與桌面變體的處理方式，以及常見的佈局模式和組件狀態管理慣例。讓團隊能遵循一致的開發標準，提高程式碼的可維護性與協作效率。
npx skills add https://github.com/lobehub/lobe-chat/tree/main/skills/reactLobeHub React 組件約定。用於編輯 TSX UI、選擇 base-ui 與 @lobehub/ui 與 antd、使用 antd-style 進行樣式設計、路由、桌面變體、佈局或組件狀態。
This repo contains 4 individual skills — each has its own dedicated page.
LobeHub Drizzle ORM schema and query style. Use for pgTable schemas, indexes, joins, inferred types, db.select/db.query, schema fields, foreign keys, junction tables, or postgres query patterns.
LobeHub i18n with react-i18next. Use for user-facing strings, locale keys, namespaces, useTranslation, t(), interpolation, zh-CN/en-US previews, hardcoded UI copy, or pnpm i18n.
LobeHub TypeScript style and type-safety guide. Use when editing TS/TSX/MTS, fixing types, choosing interface vs type, avoiding any/object, import type, async flow, or ts-expect-error.
LobeHub Zustand store conventions. Use when editing src/store, store slices, public/internal actions, dispatch actions, flattenActions, optimistic updates, selectors, maps, or class action migration.
ElevenLabs text-to-speech with mac-style say UX.
Oracle CLI second-model review/debug/refactor/design with selected files, dry-run token checks, API or browser engine.
Capture and automate macOS UI with the Peekaboo CLI.
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".