Lucent

The productivity OS for Unity: a keyboard-driven command palette for the Unity Editor.

Documentation · Version 1.1 · Editor-only, no runtime footprint

Overview

Lucent is a command palette for the Unity Editor, inspired by Raycast, Spotlight, and VS Code's Command Palette. One floating window gives you fuzzy search over Lucent commands, Unity menu items, project assets, and scene objects, plus multi-step interactive workflows, all driven from the keyboard.

Everything lives under Assets/Plugins/Lucent/Editor/ and compiles into a single editor assembly (Lucent.Editor.asmdef). Nothing ships in a build.

Requirements & installation

• Unity 2022.3 LTS or newer (developed against 2022.3.62f2)
• No external dependencies

Copy the Lucent folder into your project's Assets/Plugins/ directory. Unity compiles the editor assembly on the next refresh. There is no further setup.

Quick start

1. Open the palette with Double Shift, or via Tools → Lucent → Main Window.
2. Start typing. Lucent searches its own commands, Unity menu items, and context actions for whatever is selected.
3. Pick a result with ↑ / ↓ and press Enter to run it or start an interactive flow.

Keyboard reference

The palette window

Sections

Results are grouped into sections. With an empty query you get Recents or a welcome state; while searching you get Commands and Menu Items; with a Project or Hierarchy selection captured you also get Context and Files.

Search & ranking

Queries are matched against command keywords, display names, type labels, extra search terms, Unity menu paths, and asset paths. Matches are scored (exact beats prefix beats word-boundary beats substring) and weighted by how often and how recently you have used each result. Short fragments work better than full paths.

Interactive steps

Multi-step commands ask for one thing at a time: a name, a folder, a prefab, a scene, a component type, a field, a hierarchy object, or a clipboard entry. A breadcrumb shows where you are; Enter advances and Esc goes back a step.

Selection pill

When Lucent captures a Project or Hierarchy selection, a pill appears at the right of the search field. Click it to ping the target, or dismiss it to clear the context.

---

Settings

Open with Tools → Lucent → Settings. Changes auto-save.

• Hotkey → choose Double Shift or Modifier + Key (capture a combination such as Ctrl+Shift+P), then Save & Apply. Reset to Default returns to Double Shift.
• Menu path blacklist → hide noisy Unity menu paths by prefix, e.g. Window/Analysis/Profiler.
• Console tool → pick the console integration used by Clear Console and Search Console, or leave it empty for Unity's built-in behaviour.
• Prepare AI environment → installs CLAUDE.md, AGENTS.md, and the generate-lucent-command skill for Claude, Codex, and Antigravity.

Where state is stored

• Library/Lucent/State.json → recents, command usage counts, clipboard history.
• UserSettings/LucentSettings.json → hotkey binding, menu blacklist, console tool.

Commands themselves are never persisted; they are rediscovered by reflection on every editor load.

---

Extending Lucent

1. A Unity menu item

Lucent indexes Unity menu paths automatically, so a plain [MenuItem("Tools/My Studio/Rebuild Data")] method already shows up in search. No Lucent-specific registration.

2. A one-shot command

Add a class with a [LucentCommand] attribute and a non-empty keyword. It is discovered by reflection on the next compile.

using Lucent;

[LucentCommand("Rebuild Data", "rebuild-data",
    Category = "Tools",
    Icon     = LucentIcons.SETTINGS,
    Subtitle = "Regenerate the generated data assets")]
public class RebuildDataCommand : Command
{
    protected override void OnExecute()
    {
        DataBuilder.Rebuild();
    }
}

3. A multi-step command

Derive from CompositeCommand, return a list of StepCommands from BuildSteps(), and do the real work in OnComplete() once the last step confirms. Reuse the shipped steps (folder, name, prefab, scene, component type, field, hierarchy object, file, clipboard) rather than writing new UI.

4. Context filtering

Declare when a command should appear instead of checking inside OnExecute(): SelectionSourceFilter (Hierarchy / Project / None / All), FileTypeFilter, and SearchStateFilter. IsAvailable() is evaluated per frame against the current selection and query.

---

Command reference

Lucent ships with 130 built-in commands. Keywords are what you type in the palette.

Hierarchy 10

GameObject 1

Component 11

Transform 12

Prefab 8

ScriptableObject 1

Project 28

Selection 2

Clipboard 3

Prefs 4

Console 2

Editor 15

Settings 32

Lucent 1

---

Troubleshooting

The hotkey doesn't work

Check the saved shortcut in Hotkey Settings. Modifier combinations can be swallowed by Unity, the OS, or another editor tool. Double Shift conflicts least.

A command is missing

Commands appear only when their filters match the current search state, selection source, and file type. Component commands need a Hierarchy selection; project asset actions need a Project selection.

Results change after I select something

That's intended. Lucent captures context when it opens, and the selected GameObject, folder, prefab, scene, or asset determines which commands and context actions are relevant.