the integrations

Claude Code

{"id":"claude-code","kind":"client","name":"Claude Code","title":"Nika for Claude Code · plugin, skills, MCP server","repo":"https://github.com/supernovae-st/nika-plugins","license":"MIT","what":"One plugin install hands the agent the whole kit: 4 skills, 3 subagents, 6 slash commands, the read-only MCP oracle and the seatbelt hooks.","how":"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. The reason is that an install once sat three releases behind, silently, with a fresh clone right next to it.","install":[{"text":"Add the marketplace","code":"claude plugin marketplace add supernovae-st/nika-plugins"},{"text":"Install the kit","code":"claude plugin install nika@nika"},{"text":"Update, both rungs","code":"claude plugin marketplace update nika && claude plugin update nika@nika"}],"also":{"text":"Editing the files in VS Code too? The extension draws the DAG the agent writes.","href":"/integrations/vscode","label":"the editor extension"},"doors":[{"label":"the oracle, one room per tool","href":"/how/oracle/nika_check"},{"label":"the skeletons it scaffolds from","href":"/workflows/skeletons"},{"label":"the proof it can verify","href":"/how/proof"}],"kit":{"skills":["nika-authoring","nika-debugging","nika-operating","nika-migration"],"subagents":["nika-author","nika-debugger","nika-migrator"],"commands":["/nika:check","/nika:explain","/nika:new","/nika:trace","/nika:permits","/nika:doctor"],"mcpTools":["nika_check","nika_inspect","nika_explain","nika_schema","nika_examples","nika_template","nika_canon","nika_catalog","nika_tools"]}}

null

One plugin install hands the agent the whole kit: 4 skills, 3 subagents, 6 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. The reason is that 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-plugins
2Install the kit claude plugin install nika@nika
3Update, both rungs claude plugin marketplace update nika && claude plugin update nika@nika

Out of sync · the binary moved and the kit stayed behind? nika doctor names the lagging kit and prints the exact per-client fix.

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 · 6 commands · 9 oracle tools

the 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
/nika:doctor

the oracle tools · read-only, one room each

cross-references

the rooms it touches

where it lives

the source

Start local: install. The whole language lives in the map. Read the spec →