Project Overview
Orient yourself in the LobeHub monorepo so you can find apps, packages, and layers before changing chat or agent features.
Overview
Project Overview is an agent skill for the Build phase that maps LobeHub’s open-source monorepo layout, stack, and key directories for onboarding and code navigation.
Install
npx skills add https://github.com/lobehub/lobe-chat --skill project-overviewWhat is this skill?
- Curated map of key repo locations (apps/desktop, packages/, src/) with guidance to ls live trees for completeness
- Documents full stack: Next.js 16, React 19, SPA routing via react-router-dom, TypeScript, @lobehub/ui, antd-style
- Clarifies platform split: web, Electron desktop in-repo, React Native mobile in a separate launched repo
- Identifies open-source root package @lobehub/lobehub and LobeHub (formerly LobeChat) positioning
- Marked user-invocable: false—intended as background context the agent loads when navigating the codebase
- Documents Next.js 16 + React 19 as the core framework pairing
- Covers three platform surfaces: web, in-repo Electron desktop, and external React Native mobile
Adoption & trust: 859 installs on skills.sh; 78.4k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are contributing to LobeHub but cannot quickly tell which app, package, or src layer owns the feature you need to change.
Who is it for?
Solo builders or agents first cloning LobeHub who need a fast architectural map before editing chat, agent, or desktop code.
Skip if: Teams that already maintain an internal wiki for this repo or tasks that only need API docs without repository structure.
When should I use this skill?
Locating code layers, understanding apps/packages/src layout, business stubs, project structure, or onboarding to the LobeHub repository.
What do I get? / Deliverables
You get a stable mental model of the monorepo, tech stack table, and where to look next before opening specific modules.
- Accurate mental map of apps, packages, and src responsibilities
- Stack and platform context for the next implementation step
Recommended Skills
Journey fit
New contributors need a canonical map of the open-source workspace during active product work, which is a Build-phase documentation task. The skill is an architecture and onboarding guide—not runtime code—so it belongs on the docs shelf under Build.
How it compares
Use as a repo atlas inside the agent, not as a substitute for package-level READMEs or live directory listings.
Common Questions / FAQ
Who is project-overview for?
Contributors and agent sessions working in the LobeHub open-source monorepo who need to find layers, apps, packages, or business stubs without manual tree spelunking.
When should I use project-overview?
During Build and docs work when locating code layers, understanding apps/packages/src layout, onboarding to the repository, or answering structure questions before implementation.
Is project-overview safe to install?
It is read-only documentation context with no shell or network requirements; review the Security Audits panel on this Prism page before enabling any skill from the repo.
SKILL.md
READMESKILL.md - Project Overview
# LobeHub Project Overview > The directory listings below are a **curated map of key locations**, not an > exhaustive tree. `packages/`, `src/store/`, route groups etc. grow over time — > run `ls` against the real directory for the current set. ## Project Description Open-source, modern-design AI Agent Workspace: **LobeHub** (previously LobeChat). This repo is the **open-source root** (`github.com/lobehub/lobehub`, package `@lobehub/lobehub`). **Supported platforms:** - Web desktop/mobile - Desktop (Electron) — `apps/desktop` - Mobile app (React Native) — **separate repo, already launched** (not in this monorepo) **Logo emoji:** 🤯 ## Complete Tech Stack | Category | Technology | | ------------- | ------------------------------------------ | | Framework | Next.js 16 + React 19 | | Routing | SPA inside Next.js with `react-router-dom` | | Language | TypeScript | | UI Components | `@lobehub/ui`, antd | | CSS-in-JS | antd-style | | Icons | lucide-react, `@ant-design/icons` | | i18n | react-i18next | | State | zustand | | URL Params | nuqs | | Data Fetching | SWR | | React Hooks | aHooks | | Date/Time | dayjs | | Utilities | es-toolkit | | API | TRPC (type-safe) | | Database | Neon PostgreSQL + Drizzle ORM | | Testing | Vitest | > Exact versions live in the root `package.json` — check there, not here. ## Monorepo Layout Flat layout — `apps/`, `packages/`, and `src/` all sit at the repo root. No git submodules. ``` (repo root) ├── apps/ │ ├── cli/ # LobeHub CLI │ ├── desktop/ # Electron desktop app │ └── device-gateway/ # Device gateway service ├── docs/ # changelog, development, self-hosting, usage ├── locales/ # en-US, zh-CN, ... ├── packages/ # ~80 @lobechat/* workspace packages — `ls` for the full set. Key ones: │ ├── agent-runtime/ # Agent runtime core │ ├── agent-signal/ # Agent Signal pipeline │ ├── agent-tracing/ # Tracing / snapshots │ ├── builtin-tool-*/ # Per-tool packages (calculator, web-browsing, claude-code, ...) │ ├── builtin-tools/ # Central registries that compose builtin-tool-* │ ├── context-engine/ │ ├── database/ # src/{models,schemas,repositories} │ ├── model-bank/ # Model definitions & provider cards │ ├── model-runtime/ # src/{core,providers} │ ├── business/ # Open-source stubs (config, const, model-bank, model-runtime) — overridden by cloud │ ├── types/ │ └── utils/ └── src/ ├── app/ │ ├── (backend)/ # api, f, market, middleware, oidc, trpc, webapi │ ├── spa/ # SPA HTML template service │ └── [variants]/(auth)/ # Auth pages (SSR required) ├── routes/ # SPA page segments (thin — delegate to features/) │ └── (main)/ (mobile)/ (desktop)/ (popup)/ onboarding/ share/ ├── spa/ # SPA entries + router config │ ├── entry.{web,mobile,desktop,popup}.tsx │ └── router/ ├── business/ # Open-source stubs (client/server) — cloud repo provides real impls ├── features/ # Domain business components