project-overview

Map LobeHub monorepo layers to directory locations for codebase discovery.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/kingheu0818-sketch/lobehub_yu --skill project-overview-kingheu0818-sketch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-overview
Source: https://github.com/kingheu0818-sketch/lobehub_yu/tree/main/.agents/skills/project-overview
Command: npx skills add https://github.com/kingheu0818-sketch/lobehub_yu --skill project-overview-kingheu0818-sketch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the guesswork of navigating a large monorepo by giving you an organized, architecture-level map of where key components live and how the major layers connect.

Core Features & Use Cases

  • Monorepo Architecture Guidance: Explains the split between the open-source lobehub/ submodule and the cloud override layer, including where overrides typically occur.
  • Tech Stack & Layer Mapping: Summarizes the primary framework, state management, data fetching, API layer (tRPC), and database stack, then links each layer to its directory locations.
  • Practical Codebase Discovery: Helps you find the right places for UI components, routes, state stores, services, routers, DB schemas/models, and built-in tools when answering “where is X implemented?” questions.

Use case example: When you need to understand how a UI action reaches the backend and persists to the database, use this Skill to locate the relevant store, client service, tRPC router, server service, DB model, and schema directories.

Quick Start

Ask: “Give me a guided tour of the LobeHub monorepo and tell me where I should look to trace the path from a React UI action to the database.”

Frequently Asked Questions about project-overview

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I navigate a large monorepo and locate key architectural layers?

Navigating a large monorepo requires a structured architecture map that links layers like UI, routing, stores, services, and database schemas to their exact directory locations. This provides deterministic codebase discovery and removes guesswork.

How do I trace a React UI action through a tRPC router to the database schema?

Tracing a UI action to the database involves locating the state store, client service, tRPC router, server service, and DB model directories. A layer-mapping guide connects these components to show the complete data flow path.

What is the best way to understand submodule core and cloud override separation in a codebase?

Understanding submodule core and cloud override separation involves mapping the open-source submodule structure against the cloud override layer. This clarifies where architectural overrides typically occur and how the base codebase remains isolated.

Can I find where Zustand stores and database schemas are implemented in a TypeScript monorepo?

Yes, you can find Zustand stores and database schemas by applying a tech stack overview to the directory structure. This maps the specific state management and database layers to their respective folder locations for quick implementation discovery.

What tech stack overview do I need to map directory layers for codebase navigation?

A comprehensive tech stack overview mapping frameworks, state management, data fetching, API layers, and database stacks is needed. This links each architectural layer to its directory location, enabling accurate and deterministic project navigation.

Why does exploring directories in a monorepo feel disorganized without an architecture map?

Exploring directories without an architecture map feels disorganized because the connections between major layers like UI, services, and DB models are hidden. An organized, architecture-level map reveals where key components live and how they connect.