Skip to content

Engineering Workflows for Kimi Code

Install one plugin. Get 8 specialized skills, swarm-aware orchestration, and global rules - all from a declarative manifest, no build step.
  1. Plugin loads - Kimi Code parses kimi.plugin.json from the installed location and discovers skills/
  2. Orchestrator auto-loads - sessionStart.skill: "orchestrator" injects the full methodology and delegation rules into every session start
  3. Global rules load - rules/AGENTS.md is auto-loaded by Kimi Code from ~/.kimi-code/AGENTS.md (one-time copy)
  4. Safety enforced - Optional [[hooks]] and [[permission.rules]] blocks in config.toml enforce persona boundaries at the tool layer

In a Kimi Code session:

Terminal window
npx maestria install kimi-code

The CLI pulls @maestria/kimi-code from npm and extracts it into ~/.kimi-code/plugins/managed/maestria, then copies the global rules to ~/.kimi-code/AGENTS.md.

The plugin is distributed via npm as a tarball. The CLI (npx maestria) downloads the package, extracts the plugin manifest and skills to the correct location, and sets up the global rules. No git operations, no release branches, no subtree splits - just a standard npm package.

Full Installation Guide →