
Project Overview
- 1.6k installs
- 81.3k repo stars
- Updated August 5, 2026
- lobehub/lobe-chat
This is a copy of project-overview by lobehub - installs and ranking accrue to the original listing.
project-overview is a Claude Code skill that maps the LobeHub open-source monorepo architecture so developers can locate code layers, apps, packages, and business stubs when extending the AI Agent Workspace.
About
project-overview is a user-invocable-false onboarding skill from lobehub/lobe-chat for the LobeHub open-source monorepo (github.com/lobehub/lobehub, package @lobehub/lobeh). It provides a curated map of key locations across apps, packages, src/store, and route groups—not an exhaustive tree, since directories grow over time. Developers reach for project-overview when adding features, creating new agents, extending the workspace, or understanding business stub layers in the modern-design AI Agent Workspace formerly known as LobeChat. The skill directs contributors to run ls against real directories for current listings. Use it as the first stop before navigating the monorepo for frontend, backend, or agent changes.
- Curated map of key monorepo locations including packages, src/store, route groups, and business stubs
- Explains supported platforms: web, Electron desktop, and React Native mobile
- Complete tech stack reference covering Next.js 16, React 19, TypeScript, antd, and i18n
- Helps locate code layers and understand app/package/src layout for faster onboarding
- Non-exhaustive living reference that directs you to run ls on real directories for latest structure
Project Overview by the numbers
- 1,577 all-time installs (skills.sh)
- +84 installs in the week ending Aug 5, 2026 (Skillselion tracking)
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/lobehub/lobe-chat --skill project-overviewAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.6k |
|---|---|
| repo stars | ★ 81.3k |
| Security audit | 3 / 3 scanners passed |
| Last updated | August 5, 2026 |
| Repository | lobehub/lobe-chat ↗ |
Where is code organized in the LobeHub monorepo?
Instantly map the LobeHub monorepo architecture when adding features, creating new agents, or extending the workspace.
Who is it for?
Developers onboarding to the LobeHub/LobeChat monorepo who need to locate apps, packages, store modules, or agent extension points.
Skip if: Contributors working outside the LobeHub repository who do not need monorepo-specific layout guidance.
When should I use this skill?
The user asks about LobeHub project structure, monorepo layout, where to add agents, or how apps and packages are organized.
What you get
Monorepo architecture map, key directory listings, and layer orientation for apps, packages, store, and routes.
- Architecture orientation map
- Key directory index
- Layer navigation guidance
Files
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
│ └── server/ # Next.js-backed server: featureFlags, globalConfig, modules, routers, services, utils, workflows (`@/server/*` alias)
├── 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
├── store/ # ~30 zustand stores — `ls` for the full set
├── server/ # standalone-Hono server pieces only: agent-hono, workflows-hono (main backend lives in `apps/server`)
└── ... # components, hooks, layout, libs, locales, services, types, utilsArchitecture Map
| Layer | Location |
|---|---|
| UI Components | src/components, src/features |
| SPA Pages | src/routes/ |
| React Router | src/spa/router/ |
| Global Providers | src/layout |
| Zustand Stores | src/store |
| Client Services | src/services/ |
| REST API | src/app/(backend)/webapi |
| tRPC Routers | `apps/server/src/routers/{async\ |
| Server Services | apps/server/src/services (can access DB) |
| Server Modules | apps/server/src/modules (no DB access) |
| Feature Flags | apps/server/src/featureFlags |
| Global Config | apps/server/src/globalConfig |
| DB Schema | packages/database/src/schemas |
| DB Model | packages/database/src/models |
| DB Repository | packages/database/src/repositories |
| Third-party | src/libs (analytics, oidc, etc.) |
| Builtin Tools | packages/builtin-tool-*, packages/builtin-tools |
| Open-source stub | src/business/*, packages/business/* (this repo) |
Data Flow
React UI → Store Actions → Client Service → TRPC Lambda → Server Services → DB Model → PostgreSQLNote: Relationship to the Cloud Repo
This open-source repo is consumed by a separate, private cloud (SaaS) repo as a git submodule mounted at lobehub/. The cloud repo provides:
- `src/business/{client,server}` and *`packages/business/`** implementations
that override the stubs shipped here.
- Cloud-only routes (e.g.
(cloud)/,embed/), cloud-only stores (e.g.
subscription/), cloud-only TRPC routers (billing, budget, risk control, …), and Vercel cron routes under src/app/(backend)/cron/.
- File-resolution order in cloud:
@/store/x→ cloudsrc/store/xfirst, then
lobehub/packages/store/src/x, then lobehub/src/store/x. Cloud override wins.
When working in this repo alone, ignore the cloud layer — the stubs in src/business/ and packages/business/ are the source of truth here.
Related skills
FAQ
What repository does project-overview document?
project-overview documents the LobeHub open-source monorepo at github.com/lobehub/lobehub (package @lobehub/lobeh), the modern-design AI Agent Workspace previously known as LobeChat.
Is project-overview an exhaustive directory listing?
project-overview provides a curated map of key locations in apps, packages, src/store, and route groups. Directories grow over time, so the skill recommends running ls against real paths for the current set.
Is Project Overview safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.