Audience: Developer
When you ship a plugin pack, operators install it from the Store and configure settings under Plugins. Authors may only see side effects (checkout methods, titles, tools).
A plugin can also supply what the assistant looks at for its own kind of design and how the result is checked, how its content is found, and how its errors are fixed — in prose on the ability declaration. See Make a plugin usable by the assistant.
| Plugin | Usable by the assistant | Pack notes |
|---|---|---|
| Password Auth | No | Dataset-backed client auth |
| PayPal | No | Payment provider credentials schema |
| Cash on delivery | No | Payment method, no settings |
| Table shipping | No | Shipping rate table JSON |
| Coupon stack | No | Promo pipeline + Coupons dataset |
| Mock Exchange | No | Exchange method, no settings |
| Strip Exif | Yes | Tool pack — declare an assistant ability |
| Document Title | No | Site title formatting |
App pack layout and bind/unbind: App package. Platform host behavior: Contributor → Plugin host.