VS Code extension for Lucid Architecture — bring the CLI into the command palette, navigate your Features/Jobs/Operations from a sidebar tree view, and jump to any unit inline from ->run() calls.

Works with both Micro and Monolith Lucid projects. Automatically activates when vendor/lucidarch/lucid is detected in the workspace.

Run any lucid make:* command directly from the command palette without leaving the editor. The extension collects arguments interactively — offering existing domains and services as quick picks — then opens the generated file automatically.

Cmd+Shift+P (or Ctrl+Shift+P) → type Lucid::

Generated files use the Lucid package's own stubs — template updates in the package are reflected automatically.

The Lucid Architecture panel in the Explorer sidebar shows your project structure at a glance:

• Micro — Features / Domains (with Jobs) / Operations
• Monolith — Services (with Features and Operations) / Domains (with Jobs)

Click any node to open the file. Right-click a Domain node to Make Job in this context (domain pre-filled), or right-click a Service node to Make Feature in this context.

The tree refreshes automatically when files are added or deleted.

Every ->run() call in a Feature or Operation file gets an inline → Go to ClassName link. Clicking it navigates directly to that Job or Operation file.

Handles all three call styles:

$this->run(FindProductJob::class);
$this->run(new FindProductJob($id));
$this->run('FindProductJob');

Every Job and Operation class declaration also shows a Used by N units link. Clicking it opens a quick-pick list of every Feature or Operation that calls ->run() with that class, each entry navigating to the exact line.

Ctrl+Click (or F12) on any class name inside a ->run() or ->serve() call jumps directly to that unit's file — no PHP language server required. Works with all call styles including multi-line instantiations:

$this->run(new AttachProductImagesJob(
    productId: $product->id,
    images: $request->file('images'),
));

Place the cursor on a Job or Operation class name and press Shift+F12 (or right-click → Find All References) to see every ->run() call site across the project listed in the References panel.

Hover over a class name inside ->run() or ->serve() for an inline summary — no navigation needed.

Jobs and Operations show the constructor signature (with visibility/readonly modifiers stripped for readability) and the handle() return type, plus a usage count:

FindProductJob
──────────────
FindProductJob(string $id, bool $withVariants = false)
handle(): Product
Used by 2 units: GetProductFeature, UpdateProductFeature

Features show the ordered sequence of ->run() calls — effectively an inline lucid feature:describe:

ListProductsFeature
───────────────────
1. ParseProductFiltersJob
2. GetProductsJob
3. TrackProductListingViewJob

Jobs and Operations that are not called by any Feature or Operation receive a hint diagnostic (dotted underline) on their class declaration. They also appear in the Problems panel (Cmd+Shift+M) under the Lucid source.

Run Lucid: Show Unused Units from the command palette for a full quick-pick list of every unreferenced unit, each clickable to navigate.

Diagnostics update automatically 5 seconds after any PHP file is saved. Disable entirely via the lucid.diagnostics.unusedUnits setting.

Type a prefix in any PHP file and press Tab:

Shows the detected project mode in the bottom-right corner:

⊞ Lucid: Micro    or    ⊞ Lucid: Monolith

• VS Code ^1.85.0
• A Laravel project with lucidarch/lucid installed via Composer (vendor/lucidarch/lucid must exist)

The make/delete/init commands require a working vendor/bin/lucid binary. The tree view and CodeLens work without it.

The extension mirrors the directory conventions from Finder.php exactly:

git clone https://github.com/lucidarch/vscode-lucid
cd vscode-lucid
npm install

# Open in VS Code and press F5 to launch the Extension Development Host
code .

Bug reports and pull requests are welcome at github.com/lucidarch/vscode-lucid.

MIT © Lucid Architecture