Agent skill

LobeHub Desktop Development Guide

by lobehub in lobehub/lobehub

Walks through adding features to the LobeHub Electron desktop app: controllers, IPC types, preload exposure, renderer services, store actions and tests.

Custom licenceAuto-check passedDevelopment

Install LobeHub Desktop Development Guide

skills CLI
$ npx skills add lobehub/lobehub --skill desktop -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install lobehub/lobehub desktop --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/lobehub/lobehub.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/desktop .claude/skills/desktop && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
desktop
GitHub stars
83k
Token cost
~505 tokens
SKILL.md length
100 words
Files
6 (incl. references)
Skills in repo
50
Repo updated
First seen
Licence
Custom licence

At a glance

Walks through adding features to the LobeHub Electron desktop app: controllers, IPC types, preload exposure, renderer services, store actions and tests.

  • Works in 5 steps: Create Controller → Define IPC Types → Create Renderer Service → …
  • Adding a feature to the LobeHub desktop app that needs a main-process controller
  • SKILL.md covers Architecture Overview, Adding New Desktop Features and Detailed Guides
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

The desktop app is built on Electron with a main and renderer split. The main process under apps/desktop/src/main handles app lifecycle, system APIs and window management, the renderer reuses web code from src, and preload scripts expose the main process to the renderer in a controlled way.

A new feature follows five steps. Create a controller class in the main controllers folder that extends ControllerModule and uses IpcMethod, then register it in registry.ts. Define the parameter and result types in the electron-client-ipc package, create a renderer service under src/services/electron that calls ensureElectronIpc, implement a store action in src/store, and add tests next to the controller.

Deeper reference notes sit in the references folder for feature implementation, the local tools workflow, menu configuration and window management, and they are the place to go for topics beyond the basic five-step path.

When your agent uses it

  • Adding a feature to the LobeHub desktop app that needs a main-process controller
  • Defining IPC types and renderer services for a new desktop capability
  • Changing window or menu behavior in the Electron app

Example prompts

  • “Add a desktop controller that exposes a file picker to the renderer through IPC.”
  • “Create the IPC types, renderer service and store action for a new tray setting.”
  • “Write tests for the new controller following the existing controller tests.”

Requirements

  • A checkout of the LobeHub repository

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Create Controller
  2. Define IPC Types
  3. Create Renderer Service
  4. Implement Store Action
  5. Add Tests

What it can do on your machine

Read from SKILL.md and the folder at commit 35d442e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

LobeHub Desktop Development Guide loads about 505 tokens when it runs, and up to ~3.6k if it reads all its reference files. Until then it costs about 28 tokens; SKILL.md has 100 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~28
When it runs · the whole SKILL.md, loaded when a task matches
~505
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 100 words (~505 tokens).

“LobeHub desktop is built on Electron with main-renderer architecture:”

— opening of SKILL.md by lobehub, Custom licence
name
desktop
disable-model-invocation
true

Read the full SKILL.md on GitHub

Files

SKILL.md and 5 other files (references) in .agents/skills/desktop of lobehub/lobehub.

  • SKILL.md
  • agents/openai.yaml
  • references/feature-implementation.md
  • references/local-tools.md
  • references/menu-config.md
  • references/window-management.md

Open the folder on GitHubat commit 35d442e

Compare with similar skills

LobeHub Desktop Development Guide next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

LobeHub Desktop Development Guide compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
LobeHub Desktop Development Guide this skilllobehub/lobehub83k—~505Automated safety check: PassCustom licence
Evolutionary Modular Architecturetech-leads-club/agent-skills7k—~3.7kAutomated safety check: PassCC-BY-4.0
Siteboon Backend Module Standardssiteboon/claudecodeui14k—~1.2kAutomated safety check: PassAGPL-3.0
Control Flow Diagramsslopus/happy24k—~654Automated safety check: PassMIT
sfdx-hardis Architecture Guidehardisgroupcom/sfdx-hardis402—~2.1kAutomated safety check: PassAGPL-3.0
Handsontable Core Developmenthandsontable/handsontable22k—~3.3kAutomated safety check: PassCustom licence

Similar skills

  • Evolutionary Modular Architecture

    tech-leads-club/agent-skills

    Guides design of modular-monolith platforms with DDD, flat-by-aggregate modules, anti-corruption layers, outbox events and resilience, plus an architecture document with SVG diagrams.

    7k GitHub stars~3.7k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Enforces this repository's TypeScript backend module architecture under server/: feature folders, barrel exports, and where shared types and utilities belong.

    14k GitHub stars~1.2k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Traces how an action moves through your code and draws it as a compact ASCII tree: functions called, payload types, state changes and components that re-render.

    24k GitHub stars~654 tokensUpdated today
    DevelopmentAuto-check passed
  • sfdx-hardis Architecture Guide

    hardisgroupcom/sfdx-hardis

    Explains how the sfdx-hardis Salesforce CLI plugin is built: its TypeScript and Oclif stack, command layout, agent-mode flag and provider classes for git, notifications and AI.

    402 GitHub stars~2.1k tokensUpdated today
    DevelopmentAuto-check passed
  • Handsontable Core Development

    handsontable/handsontable

    Routes any change to the handsontable core package to the right specialist skill, by task type such as plugin, editor, renderer or validator, after a mandatory architecture review.

    22k GitHub stars~3.3k tokensUpdated today
    DevelopmentAuto-check passed
  • Walkontable Engine Development

    handsontable/handsontable

    Rules for changing Handsontable's Walkontable rendering engine: the TableView boundary, dependency injection through wire.ts and DOM geometry reads via GeometryReader.

    22k GitHub stars~3.1k tokensUpdated today
    DevelopmentAuto-check passed

More from lobehub/lobehub

All 50 skills in this repo
  • Builds single-file interactive HTML prototypes rendered with the real LobeHub UI components and written as production-style React, so they can later be split into files.

    83k GitHub stars~1.6k tokensUpdated today
    Auto-check passed
  • Verifies a delivery end to end by driving the real product on a CLI, web, desktop or iOS Simulator surface, capturing evidence and publishing a round with the lh CLI.

    83k GitHub stars~9.7k tokensUpdated today
    Auto-check passed
  • Git Worktree Cleanup

    lobehub/lobehub

    Audits stale Git worktrees and branches with a bundled script, classifies each one, and deletes only after you approve the exact candidates.

    83k GitHub stars~2.8k tokensUpdated today
    Auto-check passed
  • Maintains LobeHub's model-backed alint rule set: writing rules, removing false positives against real code, deciding warn versus error and tracking token cost.

    83k GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Guides building LobeHub builtin agent tools, from the manifest and execution runtime to executors, chat UI renders and registry wiring.

    83k GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • Explains how LobeHub client code fetches data through services, SWR store hooks and cache keys, and when to avoid useEffect fetching or duplicated state.

    83k GitHub stars~1.7k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about LobeHub Desktop Development Guide

What does LobeHub Desktop Development Guide do?

Walks through adding features to the LobeHub Electron desktop app: controllers, IPC types, preload exposure, renderer services, store actions and tests. The desktop app is built on Electron with a main and renderer split. The main process under apps/desktop/src/main handles app lifecycle, system APIs and window management, the renderer reuses web code from src, and preload scripts expose the main process to the renderer in a controlled way.

When should I use LobeHub Desktop Development Guide?

LobeHub Desktop Development Guide fits situations like: adding a feature to the LobeHub desktop app that needs a main-process controller; defining IPC types and renderer services for a new desktop capability; changing window or menu behavior in the Electron app.

How do I install LobeHub Desktop Development Guide in Claude Code?

Run `npx skills add lobehub/lobehub --skill desktop -a claude-code`. Or copy the skill folder (.agents/skills/desktop in lobehub/lobehub) into .claude/skills/desktop in your project. Claude Code loads it when a task matches its description.

How do I install LobeHub Desktop Development Guide in Codex?

Run `npx skills add lobehub/lobehub --skill desktop -a codex`. Or copy the skill folder (.agents/skills/desktop in lobehub/lobehub) into .agents/skills/desktop in your project. Codex loads it when a task matches its description.

Can I use LobeHub Desktop Development Guide in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add lobehub/lobehub --skill desktop -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/desktop, .gemini/skills/desktop, .github/skills/desktop and .opencode/skills/desktop in your project.

What does LobeHub Desktop Development Guide need to run?

SKILL.md names no scripts, command-line tools or credentials: LobeHub Desktop Development Guide is instructions for the agent only. Our summary lists: A checkout of the LobeHub repository.

Does LobeHub Desktop Development Guide access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is LobeHub Desktop Development Guide safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does LobeHub Desktop Development Guide use?

LobeHub Desktop Development Guide has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does LobeHub Desktop Development Guide use?

About 505 tokens (SKILL.md is roughly 2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.1k tokens, read only when the agent opens those files.

What are the alternatives to LobeHub Desktop Development Guide?

Skills that share tags, products or a category with LobeHub Desktop Development Guide: Evolutionary Modular Architecture (tech-leads-club/agent-skills, 7k stars), Siteboon Backend Module Standards (siteboon/claudecodeui, 14k stars), Control Flow Diagrams (slopus/happy, 24k stars) and sfdx-hardis Architecture Guide (hardisgroupcom/sfdx-hardis, 402 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains LobeHub Desktop Development Guide?

lobehub (a GitHub organization) maintains it in lobehub/lobehub, which has 83,074 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 9, 2026.

Source: lobehub/lobehub on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.