Home

plugin-kit

A typed toolkit for Claude Code plugins:

• Hook scripts: one typed class per hook event (parse() and emitOutput()), styled output, and a testing kit.
• Widgets: meters, clocks, counters, lists and tags, validated with errors a model can act on, and drawn the same way in hook output and in mods.
• The plugin-kit plugin: gives every mod a $.kit, so mods that draw widgets look and behave the same and follow the user's settings.
• Mods: run hook logic written for scripts in a mod, unchanged.
• Status lines: a ready-made one configured in JSON, or built in code from widgets bound to sources.
• Testing: record real payloads, replay them against scripts and mods, and test mods with ready-made helpers.

The npm package is @aeriondyseti/plugin-kit (formerly @aeriondyseti/hook-kit); the plugin is plugin-kit@aeriondyseti-plugins.

Which part do you need?

You're writing	Use	Read
A hook script: a command hook in settings.json or a plugin's hooks.json	the npm package	Getting Started, Hook Scripts
Types for hook input and output	the npm package (scripts) or Claude Code's own types (mods)	Hook Typings
Styled text a hook shows the user	OutputBuilder	Styled Output
State to show: health, progress, clues, conditions	widgets	Widgets
A mod that draws widgets	$.kit or a vendored copy	Widgets in Mods, The plugin-kit Plugin
Hook logic in a mod, or moved from a script	the adapter	Hooks in Mods
A status line	plugin-kit statusline, or /statusline in code	Status Line
Tests for any of the above	/testing, recorded fixtures, claude plugin test helpers	Testing, Fixtures

Starting, checking, type-checking in CI and releasing a plugin: Tooling. Every command is on the CLI page.

Working on plugin-kit itself? See Contributing.