Claude Code for SPLENT

Work at SPLENT speed. The splent Claude Code plugin teaches Claude Code how SPLENT is built — features, products, the SPL/UVL model, per-feature migrations, the feature contract — and gives it skills that drive the splent CLI for you.

Table of contents

The idea
What you get
Quick install
How it runs the CLI
Design principles
Source

The idea

The splent CLI already automates the mechanics: scaffolding, env merge, symlinks, migrations, derivation, releases. What it can’t do is the judgment — writing idiomatic feature code and tests, knowing which command to run in which order, and recovering when something breaks.

That seam is where Claude Code multiplies your speed:

The CLI does the mechanics. Claude Code adds the judgment, writes the code, orchestrates the commands, and verifies the result.

What you get

Four skills, installed as one plugin:

Skill	Invoke	What it does
feature	`/splent:feature <description>`	Author a feature end-to-end: scaffold → write models/services/routes/templates/hooks + tests → add to the SPL → install into the product → migrate → verify.
product	`/splent:product <what you want>`	Create, configure, derive, seed and run a product — or onboard an existing one. Picks the right path from the current state.
doctor	`/splent:doctor [symptom]`	Diagnose and fix: failing `derive`, UVL unsatisfiable, broken migrations, missing features, symlink/cache/env/Docker/session issues.
conventions	(automatic)	Always-on SPLENT knowledge. Claude consults it whenever you work in a SPLENT codebase, so generated code follows the real patterns.

You don’t have to type the slash commands — just describe what you want (“add a notes feature with title and body owned by the user”) and Claude picks the right skill automatically.

Quick install

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

No per-project configuration. See Installation for details and Skills reference for what each skill does.

How it runs the CLI

splent runs inside the splent_cli_container Docker container, with the workspace bind-mounted at /workspace. The skills detect this and call docker exec splent_cli_container splent … from the host (or splent … directly if you’re already inside the container). Files are edited on the host; the same files are mounted in the container. When unsure of a flag, the skills confirm it with --help at runtime, so they survive CLI version changes.

Design principles

The CLI is the source of truth. Skills drive splent commands and never hand-edit pyproject feature lists, the UVL model, or migration version tables.
Confirm before trusting. Skills check exact flags with --help, so they keep working as the CLI evolves.
Simplicity first. Sensible defaults, minimal questions, “it just works.”

Source

The plugin lives at github.com/diverso-lab/splent_claude (CC BY 4.0). Contributions welcome — add a skills/<name>/SKILL.md and bump the version in .claude-plugin/plugin.json.