Installation

Table of contents

• Requirements
• Install
• Verify
• Update
• Uninstall
• How it works under the hood

Requirements

• Claude Code installed and signed in.
• A SPLENT workspace — a folder containing splent_cli, splent_framework, splent_catalog and your products (see Getting started).
• The SPLENT CLI container running (make cli / make setup from splent_cli). The skills call splent through docker exec splent_cli_container splent ….

Install

From inside Claude Code, add the marketplace and install the plugin:

/plugin marketplace add diverso-lab/splent_claude
/plugin install splent@diverso-lab

That’s it — no per-project configuration. The plugin works in any SPLENT workspace.

Newly installed plugins activate in the next Claude Code session. Restart Claude Code (or start a new session) for the skills to become available.

Verify

/plugin                       # opens the plugin manager UI

Or from a terminal:

claude plugin details splent

You should see four skills — feature, product, doctor, conventions — under the splent@diverso-lab plugin.

Update

/plugin marketplace update diverso-lab
/plugin install splent@diverso-lab

Uninstall

/plugin uninstall splent@diverso-lab

How it works under the hood

• The plugin ships skills (skills/<name>/SKILL.md), not new binaries. They guide Claude through SPLENT workflows and drive the existing splent CLI.
• Because a plugin cannot inject a global CLAUDE.md, the framework conventions are shipped as the model-invocable conventions skill, which Claude consults automatically whenever you work in a SPLENT codebase.
• Token cost is tiny: only the skill descriptions are always-on (~900 tokens); each skill’s full instructions load only when it fires.