Menu
Integrate one lore op into the FULL LoreGUI app coherently — binding →
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
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.
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.
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.
| name | integrate-endpoint |
| description | Integrate one lore op into the FULL LoreGUI app coherently — binding → |
The end-to-end procedure to add/expose one op so it lands coherently in the app.
CLAUDE.md, docs/DESIGN-SYSTEM.md,
docs/INFORMATION-ARCHITECTURE.md, docs/domains/<domain>.md.loregui-storage-expert /
loregui-auth-expert / loregui-vcs-domain-expert) for the correct op, args,
state machine, destructiveness, and gotchas.#[tauri::command], add a thin wrapper in
src-tauri/src/commands.rs (read the op's Args/Result; LoreApi::new(state.dir());
build Args from params; return Result) and register in lib.rs generate_handler!.
Add an api.ts wrapper only if a panel needs it.palette-entry skill: palette/manifest/<domain>/<op>.ts.loregui-frontend-engineer to the ux-designer spec).loregui-docs-writer for the op description, empty/error copy,
and a tutorial if the flow is multi-step.design-review skill (loregui-ux-designer). Fix findings.cargo check -p loregui, cargo fmt --all --check,
npm --prefix frontend run build, node frontend/scripts/palette-parity.mjs.The op is invokable from ⌘K with a generated form and sits in its correct panel/menu with help, themed, all states handled, design review passed, gates green.