update plugins docs + skill
Alessandro committed
Mar 11, 2026 at 13:19 UTC
b56ac7ddffea32a58775c58976e09c48f6485b4e
3 files changed
+26
docs/agents/AGENTS.plugins.md
+8
@@ -82,6 +82,14 @@ Place *.js files in extensions/webui/<extension_point>/ and export a default asy
82
83
Core JS hooks can also expose runtime UI surfaces when static HTML breakpoints are not a fit. For example, `confirm_dialog_after_render` runs after the shared confirm dialog is built and receives the rendered dialog/body/footer nodes plus any caller-provided `extensionContext`.
84
85
+### User Feedback: Notifications, Not Inline Errors
86
+Plugin UI must use the **A0 notification system** for errors, success, and warnings. Do not render dedicated error/success boxes (e.g. a red block bound to `store.error`). Use the notification store so toasts and notification history stay consistent across the app.
87
+
88
+- **Frontend (Alpine/store)**: Import `toastFrontendError`, `toastFrontendSuccess`, `toastFrontendWarning`, `toastFrontendInfo` from `/components/notifications/notification-store.js`, or call `$store.notificationStore.frontendError(message, title)` etc.
89
+- **Backend (Python)**: Use `AgentNotification.error(...)`, `AgentNotification.success(...)` from `helpers.notification`.
90
+
91
+See [Notifications](../developer/notifications.md) for the full API.
92
+
93
---
94
95
## 4. Plugin Settings
docs/developer/plugins.md
+9
@@ -220,6 +220,15 @@ Submission rules:
220
221
A built-in **Plugin Marketplace** (always-active plugin) will allow users to browse the Plugin Index and install or update community plugins directly from the Agent Zero UI without leaving the application. This section will be updated once the marketplace plugin is released.
222
223
+## User Feedback in Plugin UI (Notifications)
224
+
225
+Plugin UIs must use the **A0 notification system** for user feedback. Do not show errors or success via inline elements (e.g. a red box bound to `store.error`).
226
+
227
+- **Frontend**: Use `toastFrontendError(message, title)`, `toastFrontendSuccess(message, title)`, etc. from `/components/notifications/notification-store.js`, or `$store.notificationStore.frontendError(...)` in templates.
228
+- **Backend**: Use `AgentNotification.error(...)`, `AgentNotification.success(...)` from `helpers.notification`.
229
+
230
+This keeps toasts and notification history consistent. See [Notifications](notifications.md) for the full API.
231
+
232
## See Also
233
234
- `docs/agents/AGENTS.plugins.md` for full architecture details
skills/a0-create-plugin/SKILL.md
+9
@@ -80,6 +80,15 @@ Import it in the HTML <head>:
80
</head>
81
```
82
83
+### 3. User Feedback: A0 Notifications Only
84
+Do **not** show errors or success via inline boxes (e.g. a red `<div>` bound to `store.error`). Use the project notification system so toasts and history stay consistent.
85
+
86
+- **Errors**: `toastFrontendError(message, "My Plugin")` (or `$store.notificationStore.frontendError(...)`)
87
+- **Success**: `toastFrontendSuccess(message, "My Plugin")`
88
+- **Warnings/Info**: `toastFrontendWarning`, `toastFrontendInfo` from `/components/notifications/notification-store.js`
89
+
90
+Import and call from your store; do not render a dedicated error/success block in the template. See [Notifications](/a0/docs/developer/notifications.md) for the full API.
91
+
92
---
93
94
## Plugin Settings