Menu
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.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
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.
Integrate one lore op into the FULL LoreGUI app coherently — binding →
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 | palette-entry |
| description | 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. |
src-tauri/src/lib.rs
generate_handler!. If none exists, this isn't a pure palette-entry task — use
integrate-endpoint to add the command first.src-tauri/src/commands.rs to get the exact
parameter names + types.frontend/src/palette/manifest/<domain>/<op>.ts:
import type { OpManifest } from "../../types";
const manifest: OpManifest = {
id: "<domain>.<op>", domain: "<domain>", op: "<op>",
label: "<Domain>: <Op>", // verb-led, Title Case
description: "<one plain sentence: what it does + effect>",
command: "<registered_command_name>",
args: [ /* one FieldSpec per command param */ ],
resultKind: "void" | "text" | "json", // by the command's return type
keywords: ["<search terms>"],
// surface?: "panel" | "menu" | "palette" // per docs/INFORMATION-ARCHITECTURE.md
};
export default manifest;
FieldSpec.name = the camelCase command param (Tauri maps to snake_case).kind: text|number|boolean|enum|string-list; enum needs options.required where the op needs a non-empty value.description is mandatory (help gate).npm --prefix frontend run build and
node frontend/scripts/palette-parity.mjs (OK).Reference entries: manifest/{repository/status,file/stage,revision/commit}.ts
and manifest/service/{start,stop}.ts.