Project Overview
Onboard to the LobeHub open-source monorepo quickly so you can find apps, packages, routes, and business stubs before changing agent workspace features.
Overview
project-overview is an agent skill most often used in Build (also Validate, Operate) that maps LobeHub’s open-source monorepo layout and tech stack for onboarding and code navigation.
Install
npx skills add https://github.com/lobehub/lobehub --skill project-overviewWhat is this skill?
- Curated map of LobeHub monorepo layers: apps, packages, and key src areas with guidance to `ls` for live trees
- Documents stack: Next.js 16, React 19, SPA routing via react-router-dom, TypeScript, antd / @lobehub/ui
- Clarifies platform split: web, Electron desktop in-repo, React Native mobile in a separate launched repo
- Points to open-source root package `@lobehub/lobehub` and branding context (formerly LobeChat)
- Explicit note that listings are not exhaustive—onboarding expects verifying directories on disk
Adoption & trust: 1.3k installs on skills.sh; 78.4k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You opened the LobeHub repo and cannot tell which app, package, or src layer owns the feature you need to change.
Who is it for?
Contributors or solo builders cloning LobeHub for customization, forks, or agent-workspace experiments.
Skip if: Teams that need step-by-step feature implementation, deployment, or API design without any repo checkout.
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 know the platform split, core stack, and where to list directories next so agent-assisted edits target the right module.
- Correct target directory or package identified for the requested change
- Stack and platform context for follow-up implementation tasks
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
First meaningful touchpoint is Build when you clone the repo and need a map before coding. The skill is an architecture and directory orientation doc, not a feature implementation or deploy runbook.
Where it fits
Decide whether your fork should touch web, desktop, or shared packages before committing to a build plan.
Find the correct package for a new agent UI surface instead of searching the whole tree blindly.
Place a react-router-dom route change in the SPA layer inside Next after reading the stack table.
Trace which app build corresponds to a bug report on desktop versus web.
How it compares
Architecture map for one monorepo—not a generic Next.js starter or a substitute for package README deep dives.
Common Questions / FAQ
Who is project-overview for?
Developers onboarding to LobeHub who need a structured map of apps, packages, and stack choices before making changes.
When should I use project-overview?
At Validate when scoping a fork or integration; during Build when locating routes and packages; at Operate when tracing where production-facing code lives in the open-source tree.
Is project-overview safe to install?
Check the Security Audits panel on this page; the skill is read-only orientation text with user-invocable false and no executable permissions.
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