LobeHub

Multi-dimensional code review. Use when the user asks to review, evaluate, or audit a PR, diff, branch, or pasted change — including informal review asks like "look at this change for problems" — via light mode: inline review against the dimension quick checklists. Not for explain-only questions about what a change does or why. Deep mode runs only on explicit invocation (/deep-review): independent dimension coverage, adversarial verification, and global duplicate consolidation before reporting.

Security · lobehub/lobehub

Agentic end-to-end testing for any project: backend verification via the project CLI, frontend verification via agent-browser (web), and desktop verification via CDP (Electron). Drives the real surface, captures visually confirmed evidence, and publishes a structured report to the LobeHub verify platform. Triggers on 'cli test', 'test with cli', 'verify with cli', 'backend test with cli', 'local test', 'test in electron', 'test desktop', 'manual test', 'test report', or any local end-to-end verification task.

Testing & QA · lobehub/lobehub

Bot-channel end-to-end verification for LobeHub — drives the real native chat apps (Discord / Slack / Telegram / WeChat / Lark / QQ / iMessage) via osascript or the iMessage bridge, on macOS. Extends the generic agent-testing skill for bot surfaces. Triggers on 'test bot', 'bot test', 'test in discord', 'test in telegram', 'test in slack', 'test in wechat', 'test in weixin', 'test in lark', 'test in feishu', 'test in qq'.

Testing & QA · lobehub/lobehub

Self-evidence for delivery verification in any repository, with or without LOBE_OPERATION_ID or a preconfigured verify plan. Discover an existing plan when present; otherwise author checks and publish a standalone acceptance. Pick the proving surface (CLI / web / desktop / iOS Simulator), capture real evidence, and submit it with the lh CLI. Triggers on 'verify the task', 'collect evidence', 'prove it works', 'upload evidence', 'verify plan', 'requiredEvidence', or any run that must self-certify its delivery. Missing LobeHub environment IDs never make this skill inapplicable.

Workflow & Productivity · lobehub/lobehub

Backfill and maintain model-bank metadata (knowledgeCutoff, family, generation). Use when adding models, fixing cutoff/family data, running a metadata sweep across aiModels providers, or researching official knowledge cutoffs.

Data & Analytics · lobehub/lobehub

Produce an interactive single-file HTML design prototype using the REAL LobeHub design system (@lobehub/ui + antd + antd-style tokens) with production-style React — no build step, opens directly in a browser. Use when asked for a design prototype / interactive mockup / 交互原型 / 出个原型 / 设计稿 HTML for a page or flow, or to explore a redesign before committing to implementation.

Frontend · lobehub/lobehub

Audit a page / surface against the Designing Interfaces pattern language + the ux skill checklists, then land findings. Three layers — static (code), visual (screenshots), dynamic (automated user journey + perf). Use to run a repeatable, standards-based UX review of one screen.

Security · lobehub/lobehub

Build LobeHub builtin tool packages. Use when adding agent-callable tools, manifests, executors, runtimes, inspectors, renders, placeholders, streaming, interventions, portals, or tool registries.

AI & Agents · lobehub/lobehub

LobeHub CLI (@lobehub/cli) development guide — commands, subcommands, architecture.

Other · lobehub/lobehub

Version release workflow — release process and GitHub Release notes (not docs/changelog pages).

Documentation · lobehub/lobehub

LobeHub product design values / principles / checklists. Use whenever the work touches user-interface features or implementation — designing or building any user-facing flow — to get better UX results.

Design & Presentation · lobehub/lobehub

Turn a vague product ask ("this page feels wrong", "we need a team view") into a grounded, shippable design by establishing business semantics and the user task before proposing a surface. Use when scoping a new surface, redesigning an existing one, or deciding what a feature should be. Not for auditing a built screen (ux-audit) or choosing visual details (ux).

Security · lobehub/lobehub