Use when working with ELPS Lisp code, substrate phylum code, or .lisp files. Provides hover docs, go-to-definition, find-references, diagnostics, performance analysis, eval, test, and formatting for ELPS code with full substrate builtin awareness (cc:*, statedb:*, sidedb:*, crypto:*, router:*). Also provides the complete shirotester CLI for linting, debugging, REPL, and test execution.
Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
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.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
Use when working with ELPS Lisp code, substrate phylum code, or .lisp files. Provides hover docs, go-to-definition, find-references, diagnostics, performance analysis, eval, test, and formatting for ELPS code with full substrate builtin awareness (cc:*, statedb:*, sidedb:*, crypto:*, router:*). Also provides the complete shirotester CLI for linting, debugging, REPL, and test execution.
metadata
{"short-description":"ELPS/substrate development toolkit via shirotester MCP","author":"luthersystems"}
version
1.0.0
Substrate -- ELPS Development Toolkit
Luther Enterprise is Luther Systems' platform for building and operating regulated, auditable business processes. Substrate is the core runtime of Luther Enterprise -- an execution environment for business logic written in ELPS (a Lisp dialect). Business logic modules are called phyla (singular: phylum) -- packages of .lisp files that define endpoints and business rules.
shirotester is the development toolkit for substrate. It provides an MCP server, language server, semantic linter, performance analyzer, debugger, REPL, test runner, and documentation browser -- all with full awareness of substrate's built-in packages (cc:*, statedb:*, sidedb:*, crypto:*, router:*, etc.).
Syntax highlighting for ELPS with substrate-specific forms (defendpoint, route-success, route-failure)
Language server via shirotester lsp with full substrate builtin resolution
DAP debugger via shirotester debug with breakpoints, stepping, and statedb inspection
ELPS source formatting via shirotester fmt
Install: search "Substrate" in the VS Code marketplace or run ext install LutherSystems.substrate.
The MCP skill and VS Code extension are complementary -- the skill brings substrate intelligence to any AI coding tool, the extension brings it to VS Code.
MCP Server
shirotester includes an MCP server that runs locally via stdio. No API keys, authentication, or remote servers required -- everything runs on your machine.
If the MCP server is not connected
Before using substrate tools, check if the shirotester MCP tools (like hover, diagnostics) are available. If not, add the MCP server:
Evaluate an ELPS expression in a shiro environment
test
Run ELPS unit tests
doc
Browse runtime documentation for packages and symbols
format
Format ELPS source code
lint
Semantic linting with cross-file symbol resolution
workspace_symbols
Search for symbols across the workspace
document_symbols
List symbols in a specific file
describe_server
Describe the MCP server capabilities
Substrate & ELPS Concepts
What is a Phylum?
A phylum is a package of .lisp files that define business logic endpoints and rules. Phyla are written in ELPS and run inside the substrate execution environment, which provides built-in packages for state management, routing, cryptography, and external service integration.
Key ELPS Concepts
Packages: Code is organized into packages with (in-package 'my-service) and (use-package 'router)
Endpoints: Business logic entry points defined with (defendpoint "method-name" (params) ...)
Responses: Endpoints return results via (route-success result) or (route-failure error)
The MCP server exposes a subset of shirotester's capabilities. The full CLI includes additional tools, all available via npx @luthersystems/shirotester <command>:
Command
Description
mcp
MCP server over stdio (what this skill configures)
lint
Semantic linting with cross-file symbol resolution and substrate builtins
analyze
Call-graph performance analysis with text, JSON, SARIF, or Mermaid output
debug
DAP debugger with breakpoints, stepping, and statedb inspection
repl
Interactive ELPS REPL with full substrate builtins
lsp
Language Server Protocol server (stdio or TCP)
fmt
Format ELPS source files
unit-tests
Run *_test.lisp unit tests in a shiro environment
functional-tests
Run YAML-defined RPC test scenarios
doc
Runtime documentation browser for all packages and symbols
