[data-reveal]{opacity:1!important;transform:none!important}
AntelopeJS DMS
DocumentationInstall the plugin

Install the plugin

Add the AntelopeJS plugin to Claude Code or Codex, so your agent gets the AntelopeJS DMS skills, then connect it to the DMS MCP tools.

Your coding agent needs the antelopejs plugin to get the AntelopeJS DMS skills. The plugin comes from the AntelopeJS/agent-skills repository. It links the skills your installed packages ship into the project, and adds its own skills for pages, mockups and existing databases. The skill catalog lists them all.

The DMS AI assistant in the dashboard does not need the plugin. See In the DMS AI assistant.

Add the plugin

Run these commands once. The plugin installs in your user scope, so every project sees it.

Terminal bash
claude plugin marketplace add AntelopeJS/agent-skills
claude plugin install antelopejs@antelopejs

Inside a session, the same commands are /plugin marketplace add AntelopeJS/agent-skills and /plugin install antelopejs@antelopejs.

Restart the session, or run /reload-plugins. The plugin's hooks then sync the skills into .claude/skills/.

To install the plugin for one repository only, add --scope project to both commands. Claude Code then records it in that repository's .claude/settings.json.

Note

The sync also works without the plugin. npx -y github:AntelopeJS/agent-skills sync links the skills into both .claude/skills/ and .agents/skills/, where any agent that reads those folders finds them.

Connect the agent to the DMS tools

Start the project once in development:

Terminal bash
ajs project dev

@antelopejs/dms then adds a dms server to the project's .mcp.json for Claude Code and to .codex/config.toml for Codex. Approve the dms server in Claude Code, or trust the project in Codex. Your agent then has the builder, database, page and mockup tools that the DMS AI assistant uses. MCP server describes both entries and the tools.

Check that the skills are there

Run /antelopejs:skills in Claude Code, or $antelopejs:skills in Codex. It lists the synced skills and the package each one comes from.

If no DMS skill shows, the packages are not installed yet:

  1. Run pnpm install.
  2. Run ajs project dev once. The modules that antelope.config.ts declares arrive in .antelope/cache.
  3. Run /antelopejs:sync-skills.

In Claude Code, run /reload-skills when .claude/skills/ did not exist at the start of the session.

Projects created from a template

template-dms-demo and template-dms-adonis ship a .claude/settings.json that declares the marketplace and enables the plugin. Once you trust the folder, Claude Code offers to install the plugin. Accept it. The AGENTS.md of each template gives Codex the sync command.

To give every Claude Code contributor the same prompt in an existing project, commit this file:

.claude/settings.json json
{
  "extraKnownMarketplaces": {
    "antelopejs": {
      "source": { "source": "github", "repo": "AntelopeJS/agent-skills" }
    }
  },
  "enabledPlugins": {
    "antelopejs@antelopejs": true
  }
}

Update the plugin

The synced skills follow your packages, not the plugin. Upgrade @antelopejs/dms or a module, and the next sync points at the new version. To update the plugin's own skills:

Terminal bash
claude plugin marketplace update antelopejs
claude plugin update antelopejs@antelopejs

Remove the plugin

Terminal bash
claude plugin uninstall antelopejs@antelopejs
claude plugin marketplace remove antelopejs

If you installed it for one repository, add --scope project to uninstall, and remove the two keys from that repository's .claude/settings.json.

To remove the synced skills from a project, delete the entries that .claude/skills/.ajs-managed.json and .agents/skills/.ajs-managed.json list. Then delete those two files and the .gitignore next to each.

Next steps

Skill catalog

Every skill, and how the sync finds it.

Best practices

The rules the agent follows when it builds a page.