the integrations
Claude Code
One plugin install hands the agent the whole kit: 4 skills, 3 subagents, 5 slash commands, the read-only MCP oracle and the seatbelt hooks. Source, license and claims live in the repo — this room is its projection, never its replacement.
- clientthe kindplug it into your tool
- MITthe licenseread it in the repo
- 3install stepsthe ritual below
- 1of 14prev / next walk them
how it works
The agent authors a plain-text workflow it can `nika check` before a token is spent and `nika trace verify` after. The oracle answers read-only (check · inspect · explain · schema · examples · template · canon · catalog · tools); the subagents author, debug and migrate; `/nika:check` is one keystroke. Updating is TWO rungs by design — refresh the marketplace clone, then move the install — because an install once sat three releases behind, silently, with a fresh clone right next to it.
get set up
- 1Add the marketplace
claude plugin marketplace add supernovae-st/nika-agents - 2Install the kit
claude plugin install nika@nika - 3Update, both rungs
claude plugin marketplace update nika && claude plugin update nika@nika
Editing the files in VS Code too? The extension draws the DAG the agent writes. the editor extension →
what lands in the agent
4 skills · 3 subagents · 5 commands · 9 oracle toolsthe skills · when to reach for nika
- nika-authoring
- nika-debugging
- nika-operating
- nika-migration
the subagents · author, debug, migrate
- nika-author
- nika-debugger
- nika-migrator
the commands · one keystroke each
- /nika:check
- /nika:explain
- /nika:new
- /nika:trace
- /nika:permits
the oracle tools · read-only, one room each
cross-references
the rooms it touches
where it lives
Start local: install. The whole language lives in the map. Read the spec →