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:

/plugins install https://github.com/agustinusnathaniel/maestria/tree/release/kimi-code

That is the entire install. No npm install, no build step. The plugin is just a manifest and a directory of markdown files.

Kimi Code only looks for kimi.plugin.json at the archive root, so the CI workflow maintains a release/kimi-code branch where the manifest sits at the root. The plugin lives at packages/kimi-code/ in a monorepo; pushing a @maestria/kimi-code@v<version> tag triggers a git subtree split that updates the release branch. Re-installing picks up the latest version automatically. See ADR-KC-000 for the rationale.

Full Installation Guide →