openxiangda-skill-kit 2.0.0-alpha.13 → 2.0.0-alpha.131

package/skills/openxiangda-v2-frontend/SKILL.md

@@ -1,40 +0,0 @@
----
-name: openxiangda-v2-frontend
-description: Build OpenXiangda 2.0 React and Ant Design admin experiences. Use when implementing menus, routes, CRUD pages, role switching, workflow task pages, or application-defined action components.
----
-
-# OpenXiangda 2.0 Frontend
-
-Build inside `apps/web` with `openxiangda-admin`. Preserve the standard shell, role session, route guards, error handling, and typed clients.
-
-## Implementation Rules
-
-1. Register menus and routes through the application contribution API.
-2. Gate navigation and actions with generated capability names; the server remains authoritative.
-3. Use the active-role session supplied by the platform. Switching roles must refresh permissions and scoped data.
-4. Use the standard CRUD and workflow modules first; add application components only for real domain interactions.
-5. Render workflow actions and field policies from the backend protocol. Do not duplicate workflow transition rules in the browser.
-6. Keep data calls in typed client modules rather than components.
-7. Preserve the standard responsive layout, permission-filtered navigation,
-   cached tabs, personal center and stable role switcher. Build management lists
-   with the standard search, pagination, sorting, density, column settings,
-   revision-aware editing and batch action surfaces before adding custom UI.
-8. Use `department`, `user`, and `relation` search/form controls for persisted
-   identifiers. Render directory identifiers with `DepartmentText` or
-   `UserText`; do not expose internal IDs as the primary business label.
-9. Keep DataResource field policies effective across list columns, search,
-   forms, import and export. Authorization loading or errors must fail closed.
-10. Use the standard dashboard and CSV transfer modules before creating
-    application-specific copies. Imports must use restricted transactions and
-    stable idempotency keys.
-11. Keep the standard record detail drawer and business-audit timeline unless
-    the domain needs a genuinely different presentation. Use `DataFileField`
-    for managed attachments and the aggregate chart components for summaries;
-    never expose storage URLs or aggregate complete result sets in-browser.
-12. Import from the narrow `openxiangda-admin/core`, `/data`, `/dashboard`,
-    and `/workflow` entrypoints. Keep business route modules lazy and preserve
-    the template's chunk-cycle and size budgets.
-
-Run `openxiangda generate`, `openxiangda check`, and `openxiangda test` after changing contracts or pages. Run `pnpm test:e2e` for shell, navigation, role, data-page or recovery changes; preserve the desktop and mobile Chromium paths and use accessible role/label locators instead of Ant Design private DOM. Use accessible Ant Design patterns and run the repository's Ant Design lint when available.
-
-Read [Frontend](../../docs/frontend.md) for route, menu, role, and workflow page examples.

package/skills/openxiangda-v2-frontend/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "OpenXiangda 2.0 Frontend"
-  short_description: "Build standard React and Ant Design application pages"
-  default_prompt: "Use $openxiangda-v2-frontend to implement this OpenXiangda 2.0 frontend."

package/skills/openxiangda-v2-workflow-events/SKILL.md

@@ -1,39 +0,0 @@
----
-name: openxiangda-v2-workflow-events
-description: Implement OpenXiangda Workflow Kernel v2 and durable application events. Use for approval definitions, assignee providers, task actions, delegation, add-sign, previews, data-change events, workflow events, or timers.
----
-
-# OpenXiangda 2.0 Workflow and Events
-
-The workflow kernel owns definitions, instances, tasks, transitions, delegation, add-sign, audit, and field policies. The application owns business records and application-specific logic.
-
-## Workflow
-
-1. Declare approval and conditional nodes in `openxiangda.config.ts`.
-2. Use provider contracts for application-data-dependent assignee resolution and custom action decisions.
-3. Keep submit preview and actual start on the same definition version and subject context.
-4. Return protocol `operations`, field policies, presentation hints, execution targets, and concurrency tokens from the backend. Task and instance operations may coexist on one Surface; dispatch them to their declared task/instance command scope.
-5. Persist business changes through Data API or App API, then correlate them to the workflow action.
-6. Test approve, reject, transfer, return, resubmit, delegation, add-sign, initiator withdrawal, admin termination, duplicate requests, and stale revisions.
-7. Rotate application Provider signing keys with `workflow provider rotate`,
-   then deploy. During that deployment the Nest adapter must accept both current
-   and `_NEXT` secrets; the platform activates the next version after readiness.
-
-## Events
-
-- Subscribe to typed data and workflow events; implement idempotent consumers.
-- Use timers as durable event producers.
-- Verify signatures, propagate correlation IDs, and fail retryably for transient dependencies.
-- Never assume event ordering unless the contract explicitly provides a partition key.
-- Inspect dead letters with `event delivery list` and replay with a stable
-  idempotency key. Do not retry deterministic 4xx failures in a consumer loop.
-- Keep the default platform-backed durable receipt store in production. It uses
-  the subscription HMAC secret and survives Pod restarts and multiple replicas;
-  inject `InMemoryOpenXiangdaEventReceiptStore` only in local tests.
-- Treat an in-flight duplicate as retryable, not successful. Use `event.id` as
-  the Data API transaction or downstream idempotency key for side effects that
-  can succeed before the receipt completion request reaches the platform.
-
-Use `openxiangda generate`, `openxiangda check`, and `openxiangda test` to keep providers and event payloads aligned.
-
-Read [Workflow and Events](../../docs/workflow-events.md) for protocol details.

package/skills/openxiangda-v2-workflow-events/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "OpenXiangda 2.0 Workflow and Events"
-  short_description: "Implement workflow providers and durable event consumers"
-  default_prompt: "Use $openxiangda-v2-workflow-events to implement this workflow and event behavior."