菜单
Build a whole domain's UI surface coherently — its panel, nav entry, palette entries for every op, and help — per the information architecture. Use to bring a domain from palette-only to a first-class part of the app.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | add-domain-ui |
| description | Build a whole domain's UI surface coherently — its panel, nav entry, palette entries for every op, and help — per the information architecture. Use to bring a domain from palette-only to a first-class part of the app. |
Bring one domain (e.g. branch, storage, lock) to first-class coherence.
crates/lore-vm/src/ops/<domain>/). Spawn the
domain expert for behavior/state machines. Per the IA, classify each op:
panel-primary / row-menu / palette-only.loregui-ux-designer for the panel layout (reusing components),
the nav entry, every op's placement + copy, and the four states.#[tauri::command]; add the
missing ones (integrate-endpoint step 4).palette-entry skill)..section, cards, OpForm, OpResult).loregui-docs-writer: op descriptions, the panel's empty state, and a
tutorial for any multi-step flow (e.g. merge, server setup).design-review; then cargo check -p loregui,
cargo fmt --all --check, npm build, palette-parity (+ IA/help) all green.The domain has a navigable panel, every op is reachable (palette + its prescribed surface), help exists, it's themed and consistent with sibling domains, gates green, design review passed. This is the bar every domain must reach (Epic SBAI-4024).
The single entry point for getting an agent (or a person) productive with LoreGUI — the cross-platform desktop GUI + MCP toolkit for Epic's lore VCS. Use this to INSTALL or build LoreGUI, set up and register the lore-mcp server, configure a repo (connect to a server or host one), and then drive/manage lore. Point a new agent here and it can install, configure, and operate the whole stack. For the lore VCS mental model + per-op semantics, defer to the [[lore]] skill.
Drive and reason about Epic Games' lore VCS the way you would git or p4 — the mental model, the full command/op surface across 14 domains, git/p4→lore translation, common workflows, and how to execute ops (via the lore-mcp tools / lore-vm / the LoreGUI palette). Use whenever a task involves a lore repository, revisions, branches, staging, locks, fragments, or shared stores.
Run the LoreGUI coherence checklist over a UI diff — pass/fail with specific fixes. Use before merging any UI PR (the ux-designer's gate). Checks tokens, placement, copy, states, consistency, accessibility, help.
Integrate one lore op into the FULL LoreGUI app coherently — binding →
Add one op's command-palette manifest entry (the mechanical Phase-2 unit). Use when an op already has a registered Tauri command and just needs to be exposed in the palette. Formalizes frontend/src/palette/README.md.
Write a guided how-to / in-app help for a multi-step LoreGUI flow (onboarding, connect-to-server, merge, host setup, etc.). Use to satisfy the help gate for non-trivial flows. Produces step-by-step copy placed in-app and/or in website docs.