Cursor

Soubi emits the current Cursor marketplace plugin layout. Standard component directories are auto-discovered, while manifest overrides can point Cursor at custom hook or MCP paths when an existing marketplace package requires them.

Native output

.cursor-plugin/plugin.json
rules/<plugin-id>.mdc
skills/<name>/SKILL.md
commands/<name>.md
agents/<name>.md
hooks/hooks.json
mcp.json

Portable tools are added through a generated MCP stdio server registered in mcp.json.

Translation details

• Instructions become an always-applied Cursor rule.
• Skills, commands, and subagents retain their Markdown bodies and frontmatter.
• Supported lifecycle and tool events are translated to Cursor's version 1 hook format.
• ${PLUGIN_ROOT} in hook and MCP commands becomes ${CURSOR_PLUGIN_ROOT}.
• Plugin and component assets retain their repository-relative paths.

Use harnessDefaults.cursor.manifest only for marketplace-specific metadata or non-default component paths. harnessDefaults.cursor.mcpPath can select an MCP filename used by an existing package.

Build this target

pnpm soubi build ./my-plugin --harness cursor

Run soubi check when using hooks because support is resolved per event and handler type.