Menü
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.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
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.
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.
| name | design-review |
| description | 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. |
Review a diff (default: git diff main...HEAD) against the checklist. Read
docs/DESIGN-SYSTEM.md + docs/INFORMATION-ARCHITECTURE.md first. For each item:
PASS, or FAIL with file:line + the concrete fix.
--surface-* or the
legacy aliases. Renders correctly in both light and dark themes.description is one plain sentence;
matches lore terminology; jargon has a tooltip.--surface-error-*, real message, retry), success all handled.OpForm/
OpResult/existing panels; one primary action per view.button/label[htmlFor]/role=dialog; keyboard-
reachable; visible focus; meaning not by color alone.palette-parity (+ IA/help) green; build green.DESIGN REVIEW: PASS or FAIL + a numbered list of fixes (file:line, what, why).
Be specific and actionable; do not approve incoherent or unthemed UI.