Port an existing plugin

Already have a plugin or rules folder for one harness? Port it once into a portable definePlugin and compile it to Claude Code, Codex, Gemini CLI, Copilot, Cursor, Windsurf, Pi, and OpenCode. You keep your files on disk; the generated plugin definition points at them.

The fast path: ap-sdk port

npx ap-sdk port ./my-plugin            # writes ./my-plugin/plugin.ts
npx ap-sdk port ./my-plugin --dry-run  # preview it first

port detects the source layout, reads manifests, instruction files, SKILL.md skills, commands, agents, hooks, and companion directories, then writes a portable plugin.ts that loads files with readTextFrom, readBodyFrom, and readDir.

npx ap-sdk check plugin.ts
npx ap-sdk build plugin.ts

Review any generated TODO comments. Unmapped native hook events are flagged in code so you can choose the right portable event.

Source layouts

Keep your files on disk

import { definePlugin, readDir, readTextFrom } from "@jalco/ap-sdk";

const read = readTextFrom(import.meta.url);

export default definePlugin({
  id: "alp-river",
  description: "Multi-step agent refinement pipeline.",
  instructions: read("./CLAUDE.md"),
  files: readDir("./hooks", import.meta.url, "hooks"),
});

A harness with no native form for a feature drops just that piece with a warning, never a broken file.