In the DMS AI assistant
How the DMS AI assistant loads the skills of every loaded module and shows DMS blocks in the chat before it builds them.
@antelopejs/dms-assistant adds an AI workspace to the dashboard for owners. A chat panel docks next to the page, and a coding agent runs in a local sidecar. The agent reads the loaded modules, edits the project and shows its work as it goes. The assistant is a development tool. With NODE_ENV=production, the module starts no sidecar, and the sidecar exits if you start it yourself.
Skills load without a plugin
When the assistant starts, it collects the skills that antelopeJs.skills declares in three places: every module the project loads, the dependencies of those modules, and the project's own dependencies, devDependencies included. The project's devDependencies bring the framework skills of @antelopejs/core. The assistant hands every skill to the agent as <module>:<skill>, for example dms:dms-auth or dms:dms-project. Install a module, and the assistant has its skill on the next start.
When two skills share a name, the assistant uses one copy. In the assistant's settings, Use machine-local skills adds the skills in ~/.claude/skills on your machine. Teammates and other environments do not get them.
The agent shows blocks before it builds them
When a choice is visual, such as how a block will look or whether a DMS block fits better than a custom one, the agent shows the options before it asks. It calls its PreviewBlocks tool with a tree of DMS blocks. The call can add your mockup as a reference image and more views as variants:
{
"title": "KPI row",
"description": "Your mockup's figures as DMS KPI cards.",
"tree": {
"type": "Grid",
"children": [
{
"type": "GridRow",
"children": [
{ "type": "KpiCard", "options": { "title": "Revenue", "staticValue": 48200, "valueFormat": "currency", "currencyCode": "EUR" } },
{ "type": "KpiCard", "options": { "title": "Orders", "staticValue": 1284 } }
]
}
]
},
"reference": { "attachmentId": "mockup.png", "caption": "Your design" }
}
The conversation shows an attachment card with an icon, the title and a thumbnail. A click on the card opens a modal. The modal renders the real blocks with your dashboard's theme next to the reference image, with a tab for each variant. A view can hold a sketch instead of a tree. A sketch is static HTML and CSS of the custom block the agent proposes, labelled as not a DMS block. You compare both before anyone writes code. The agent then asks its question with its AskUser tool, and you answer with a button.
The modal renders the blocks with DmsBlockPreview, the same component as the block preview page. When the dashboard does not provide that component, the attachment shows the tree as JSON.
The chat walkthrough shows the attachment and both kinds of view in the running module. It uses a labelled demonstration conversation, not a response from a model.