Skip to content

Commit b7f9ebd

Browse files
committed
docs(skills): objectui guides stop teaching the retired @object-ui/plugin-ai and vscode-extension
The sample package.json in guides/project-setup.md no longer installs @object-ui/plugin-ai (retired; 18.2.0 was its last release). The AI row of the plugin catalog in guides/page-builder.md lists plugin-chatbot alone. The README's package snapshot drops `ai` from the plugin list (18, not 19) and `vscode-extension` from the tooling line, the extension having left the workspace. evals/project-setup.json case 1 refuses an answer that installs the retired package; its own file pays the added bytes by dropping the workspace-only apps/console pointer from case 3's rubric, which rules/styling.md still teaches. Co-authored-by: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QSeKYmhU5KEj1nukYhp1Tg
1 parent 9f76037 commit b7f9ebd

5 files changed

Lines changed: 20 additions & 6 deletions

File tree

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
---
2+
"@objectstack/skills": patch
3+
---
4+
5+
Clause-②: no
6+
Metadata-protocol: none
7+
8+
objectui: the guides teach only what ships. `guides/project-setup.md`'s sample
9+
`package.json` no longer installs `@object-ui/plugin-ai` (retired; `18.2.0` was its
10+
last release), the AI row of `guides/page-builder.md`'s plugin catalog lists
11+
`plugin-chatbot` alone, and the README's package snapshot drops `plugin-ai` from the
12+
plugin list (18, not 19) and `vscode-extension` from the tooling line (the extension
13+
left the workspace). `evals/project-setup.json` case 1 (the full Vite + React setup)
14+
now fails an answer that installs the retired package.

‎skills/objectui/README.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -55,8 +55,8 @@ The published packages this skill covers. Nothing checks this list against the
5555
- **Parsing & runtime:** `@objectstack/sdui-parser`, `react-runtime`
5656
- **Integration:** `@object-ui/app-shell`, `providers`, `data-objectstack`
5757
- **Platform features:** `@object-ui/auth`, `permissions`, `i18n`, `mobile`, `collaboration`
58-
- **Plugins (19):** `plugin-{grid, list, detail, form, kanban, calendar, timeline, gantt, dashboard, report, charts, map, editor, markdown, view, tree, designer, ai, chatbot}`
59-
- **Tooling:** `@object-ui/cli`, `create-plugin`, `vscode-extension`
58+
- **Plugins (18):** `plugin-{grid, list, detail, form, kanban, calendar, timeline, gantt, dashboard, report, charts, map, editor, markdown, view, tree, designer, chatbot}`
59+
- **Tooling:** `@object-ui/cli`, `create-plugin`
6060

6161
## Reference
6262

‎skills/objectui/evals/project-setup.json‎

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,8 @@
1616
],
1717
"must_not_contain": [
1818
"create-react-app",
19-
"node_modules/@object-ui"
19+
"node_modules/@object-ui",
20+
"@object-ui/plugin-ai"
2021
]
2122
}
2223
},
@@ -40,7 +41,7 @@
4041
{
4142
"id": 3,
4243
"prompt": "How do I add the grid and kanban plugins to my existing ObjectUI project and make sure they're available in my schemas?",
43-
"expected_output": "Shows installing @object-ui/plugin-grid and @object-ui/plugin-kanban, the side-effect import at the app entry that registers each plugin's renderers in ComponentRegistry (without it SchemaRenderer resolves the node to 'Unknown component type'), and the schema type to use afterwards. On styling: the plugin packages publish no stylesheet of their own — only @object-ui/components and @object-ui/fields export a ./style.css — so there is no third sheet to import and nothing to point Tailwind at inside node_modules. Inside the ObjectUI workspace the app owns the Tailwind entry and adds one @source line per plugin package's src, the way apps/console/src/index.css does.",
44+
"expected_output": "Shows installing @object-ui/plugin-grid and @object-ui/plugin-kanban, the side-effect import at the app entry that registers each plugin's renderers in ComponentRegistry (without it SchemaRenderer resolves the node to 'Unknown component type'), and the schema type to use afterwards. On styling: the plugin packages publish no stylesheet of their own — only @object-ui/components and @object-ui/fields export a ./style.css — so there is no third sheet to import and nothing to point Tailwind at inside node_modules. Inside the ObjectUI workspace the app owns the Tailwind entry and adds one @source line per plugin package's src.",
4445
"files": [],
4546
"assertions": {
4647
"must_contain": [

‎skills/objectui/guides/page-builder.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -325,7 +325,7 @@ Pick plugins by domain — each registers its own `type` strings in the Componen
325325
| Visualization | `plugin-charts`, `plugin-map` |
326326
| Editors | `plugin-editor`, `plugin-markdown` |
327327
| Views & Design | `plugin-view`, `plugin-tree`, `plugin-designer` |
328-
| AI | `plugin-ai`, `plugin-chatbot` |
328+
| AI | `plugin-chatbot` |
329329

330330
For lazy loading, use `LazyPluginLoader` from `@object-ui/react` rather than top-level imports.
331331

‎skills/objectui/guides/project-setup.md‎

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,6 @@ Add plugins as needed (full plugin catalog):
7272
"@object-ui/plugin-view": "latest",
7373
"@object-ui/plugin-tree": "latest",
7474
"@object-ui/plugin-designer": "latest",
75-
"@object-ui/plugin-ai": "latest",
7675
"@object-ui/plugin-chatbot": "latest"
7776
}
7877
```

0 commit comments

Comments
 (0)