@nocobase/app-skills 0.1.0-beta.66 → 0.1.0-beta.67

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@nocobase/app-skills",
3
- "version": "0.1.0-beta.66",
3
+ "version": "0.1.0-beta.67",
4
4
  "description": "Agent Skills for developing applications and plugins, upgrading and deploying NocoBase applications.",
5
5
  "license": "Apache-2.0",
6
6
  "repository": {
@@ -351,7 +351,7 @@ From the repository root, pass `--workspace-root .`: the command selects `app-te
351
351
  - For hooks, run the affected App build or dev startup and verify the expected artifact or behavior at the selected stage.
352
352
  - Build the target App and run `node dist/cli/index.js <topic> --help` to confirm that `commands` are present and `devCommands` are absent in the deployment.
353
353
 
354
- Current implementation and maintained examples, in the `nocobase/nocobase` repository on the `v3-develop` branch:
354
+ Current implementation and maintained examples, in the `nocobase/nocobase` repository on the `v3` branch:
355
355
 
356
356
  - CLI plugin types (`packages/app/app-cli/src/plugins/types.ts`)
357
357
  - CLI plugin validation (`packages/app/app-cli/src/plugins/define.ts`)
@@ -1,6 +1,6 @@
1
1
  # Client Service, Context, and Routed Tabs Examples
2
2
 
3
- Use these examples when the shorter Client references do not show enough implementation detail. They follow the current `ClientApplication`, authorization Client, React Router, and shadcn/base-nova APIs on `v3-develop`; adapt package names, resource identities, copy, and event topics to the owning plugin.
3
+ Use these examples when the shorter Client references do not show enough implementation detail. They follow the current `ClientApplication`, authorization Client, React Router, and shadcn/base-nova APIs on `v3`; adapt package names, resource identities, copy, and event topics to the owning plugin.
4
4
 
5
5
  ## Application-scoped Client service with typed options
6
6
 
@@ -1,6 +1,6 @@
1
1
  # Server Route examples
2
2
 
3
- Use these examples when the concise rules in [Server development](./server.md) are not enough. They follow the current NocoBase v3 `defineApiRoutes()`, `defineRootRoutes()`, `Auth`, and `AppAuthorization` contracts on `v3-develop`.
3
+ Use these examples when the concise rules in [Server development](./server.md) are not enough. They follow the current NocoBase v3 `defineApiRoutes()`, `defineRootRoutes()`, `Auth`, and `AppAuthorization` contracts on `v3`.
4
4
 
5
5
  ## Choose the mount scope first
6
6
 
@@ -1,6 +1,6 @@
1
1
  # ServiceToken and Provider examples
2
2
 
3
- Use these examples after [Services, tokens, and Providers](services.md) identifies the container and lifecycle as the right design. The snippets follow the current `@nocobase/service-provider` and `@nocobase/app-server` APIs on `v3-develop`: Tokens use object identity, singleton factories are synchronous, Server plugins require an absolute `baseDir`, and the App drives Provider lifecycle methods.
3
+ Use these examples after [Services, tokens, and Providers](services.md) identifies the container and lifecycle as the right design. The snippets follow the current `@nocobase/service-provider` and `@nocobase/app-server` APIs on `v3`: Tokens use object identity, singleton factories are synchronous, Server plugins require an absolute `baseDir`, and the App drives Provider lifecycle methods.
4
4
 
5
5
  ## ServiceToken patterns
6
6