Project Structure

Soubi builds a portable plugin from ordinary files in one directory. Add only the capabilities the plugin needs.

Start with one file

An instructions file is enough to build a plugin:

my-plugin/
└── AGENTS.md

When plugin.config.ts is absent, Soubi uses the directory name as the plugin ID.

Add capabilities by path

A typical plugin grows into this layout:

my-plugin/
├── plugin.config.ts
├── AGENTS.md
├── skills/
│   └── review/
│       ├── SKILL.md
│       └── rubric.md
├── commands/
│   └── commit.ts
├── agents/
│   └── reviewer.ts
├── hooks/
│   └── pre-tool-use.ts
├── tools.ts
├── mcp.ts
└── assets/
    └── policy.json

Let filenames supply names

The filename or directory usually supplies the model-facing name. For example:

commands/release-notes.ts  →  release-notes
agents/security-reviewer.ts  →  security-reviewer
skills/diff-review/SKILL.md  →  diff-review

Set an explicit name only when the portable name should differ from the path.

TypeScript module rules

plugin.config.ts, commands, agents, hooks, tools.ts, and mcp.ts are loaded as modules. Default-export the relevant define* result. Soubi also accepts .tsx, .mts, .js, and .mjs.