objectstack-ai

@objectstack-ai source repo

20 skills
0 followers
8 hours ago last updated

▌
Objectui · objectstack-ai bundle
Universal Server-Driven UI (SDUI) engine for building JSON-driven React interfaces with Shadcn design quality. Use for schema-driven page building, plugin development, expression bindings, data integration, testing, auth/permissions, i18n, mobile responsiveness and project setup with the `@object-ui/*` packages. Triggers on ObjectUI, SchemaRenderer, JSON UI schemas, SDUI, metadata-driven UIs, `@object-ui/*`. Do NOT use for server-side ObjectStack concerns (data modelling, API endpoints, automation, formulas, agents) — those belong to the `objectstack-*` skills.

0
installs
▌
Verify · objectstack-ai
Verify metadata-admin designer (previews) changes end-to-end in a real browser without a backend, via the console preview gallery.

0
installs
▌
Plugin Dashboard · objectstack-ai bundle
@object-ui/plugin-dashboard — Skill notes

0
installs
▌
Objectui Contributor · objectstack-ai bundle
Repo-internal rules for contributors editing THIS monorepo — the Console reference app (`apps/console`, `@object-ui/app-shell`) and the Shadcn-synced primitives under `packages/components/src/ui/`. Use when working on this repository's own source, not when authoring an app with the published `@object-ui/*` packages.

0
installs
▌
Objectstack AI · objectstack-ai bundle
Design ObjectStack AI skills, tools, knowledge sources, and the open-edition MCP server surface. Use when the user is adding `*.skill.ts` / `*.tool.ts`, configuring an LLM provider, wiring the tools a skill grants, or indexing ObjectStack data as a knowledge source for RAG. Agents themselves are platform-internal (`ask` / `build`) — third parties extend them via skills, not by authoring `*.agent.ts`. Do not use for general LLM prompting questions unrelated to ObjectStack metadata.

0
installs
▌
Objectstack UI · objectstack-ai bundle
Author ObjectStack UI metadata — Views (list/form/kanban/calendar/gantt), Apps (navigation), Pages (structured plus the HTML and React source-authoring tiers, ADR-0080/0081), Dashboards, Reports, Charts, Actions, and package Docs (`src/docs/*.md`). Use when the user is adding `*.view.ts` / `*.page.ts` / `*.app.ts` / `*.dashboard.ts` / `*.report.ts` / `*.dataset.ts` / `*.action.ts` / `src/docs/*.md` files or designing a Studio-rendered UI surface. Do not use for: data schema (see objectstack-data), multi-step flows that BRANCH on logic between steps (those are `*.flow.ts` with `type: 'screen'` — see objectstack-automation; a stepped form over ONE object is this skill's `formViews` `type: 'wizard'`), or Studio's own admin UI (that ships with the platform). CEL expressions in visibility/conditional rules: load objectstack-formula alongside.

0
installs
▌
Objectstack API · objectstack-ai bundle
Design the server-side API surface that an ObjectStack runtime exposes — REST endpoints, auth providers, realtime channels, error envelopes, batch contracts. Use when the user is adding `*.endpoint.ts`, configuring auth providers, defining custom routes, or extending the REST generator. Do not use for: consuming an ObjectStack API from a client (that is just standard HTTP — no skill needed); the auto-generated CRUD endpoints (those follow from objectstack-data); request-side query syntax (see objectstack-query). CEL expressions in route guards or auth predicates: load objectstack-formula alongside.

0
installs
▌
Objectstack Data · objectstack-ai bundle
Design ObjectStack data schemas — objects, fields, field conditional rules, relationships, validations, indexes, lifecycle hooks, permissions, row-level security, data `lifecycle` retention/TTL/rotation, metadata `protection` locks, and external / federated datasources (`defineDatasource`) — and the seeds (`defineSeed()`) that load fixtures and reference data alongside them. Use when the user is creating or modifying `*.object.ts` files or `src/data/*.ts` seed modules, picking field types, modelling relationships, writing `beforeInsert`/`afterUpdate` hooks, configuring per-object access control, pointing an object at an existing external database, or authoring bootstrap / demo data. Use for `visibleWhen` / `readonlyWhen` / `requiredWhen` rules that belong on fields. Do not use for querying data (see objectstack-query) or for plugin / kernel hooks (see objectstack-platform). CEL expressions in formulas / validations / sharing rules / dynamic seed values: load objectstack-formula alongside.

0
installs
▌
Objectstack I18N · objectstack-ai bundle
Author ObjectStack translation bundles — object/field labels, view text, app navigation strings, automation messages — and configure locale fallback, coverage reporting, and the source layout. Use when the user is adding `*.translation.ts` files, authoring a `translation` metadata item in the Studio or through the metadata API, shipping a generated bundle from a package or plugin, wiring a new locale, or resolving missing-translation warnings. Do not use for general i18n library questions unrelated to ObjectStack bundles.

0
installs
▌
Objectstack Query · objectstack-ai bundle
Construct ObjectQL queries — filters, sorting, pagination, aggregation, relation expansion, and full-text search. Use when the user is writing a query DSL expression or picking a pagination strategy. Do not use for defining objects / fields / relationships (see objectstack-data), for designing the API endpoint that exposes a query (see objectstack-api), or for a list view's filter rules / dashboard datasets (see objectstack-ui).

0
installs
▌
Pm Dispatch · objectstack-ai bundle
Project-manager dispatch loop: pull ready issues from the GitHub backlog, claim and dispatch each to a parallel `os-dev` developer subagent, review the structured reports they return, then dispatch the next batch — filing `needs-user-decision` issues for anything that requires the maintainer's confirmation instead of guessing. Use when asked to "work through the backlog", "派发 issue 给开发 agent", "batch-dispatch issues", or via /pm-dispatch. NOT a customer-published skill — internal agent tooling (lives in .claude/, never in the published `skills/` dir).

0
installs
▌
Objectstack Formula · objectstack-ai bundle
Author CEL expressions used across ObjectStack — formula fields, field conditional rules (`visibleWhen`, `readonlyWhen`, `requiredWhen`), validation / sharing / visibility predicates, flow conditions, and dynamic seed values. This is the companion skill that objectstack-data, -ui, -api and -automation each tell you to load alongside them. Use when the user is writing an `F`, `P`, or `cel` tagged-template literal, or asks "how do I express X as a formula / predicate". Do not use for SQL fragments (driver-native) or L2 hook bodies (those belong in objectstack-data).

0
installs
▌
Objectstack Upgrade · objectstack-ai
Upgrade an ObjectStack metadata project across a protocol major — run the deterministic conversion chain, then work the semantic residue the chain cannot express (intent choices, custom code on retired APIs, stale prose) to a decision with the project's owner, and finish with a green `validate` plus a human-readable upgrade report. Use when a project is on an older protocol major and must move to the current one, when `@objectstack/spec` was bumped across a major and metadata or code stopped parsing, when a parse or `tsc` error quotes a `[REMOVED]` prescription, or when asked to "upgrade to v17" / "升级到 v17" / "一键升级元数据项目". Do not use to author new metadata (the domain skills cover that), or to reconcile physical database drift (that is objectstack-platform's `os migrate plan` / `os migrate apply`).

0
installs
▌
Objectstack Platform · objectstack-ai bundle
Bootstrap, configure, extend, and operate ObjectStack runtimes. Covers project setup (`defineStack`, drivers, scaffolding), declaring platform capabilities (`requires:` — which service plugins boot), plugin and service development (PluginContext, DI, kernel hooks like `kernel:ready`), and operations (CLI commands, migrations, deployment, test harnesses via LiteKernel). Use when the user is writing `objectstack.config.ts`, building a plugin or driver, turning a platform capability on, mounting the Hono HTTP layer, running `os` CLI commands, or planning deployment. Do not use for data schema design (see objectstack-data) or query patterns (see objectstack-query); data lifecycle hooks (beforeInsert / afterUpdate) belong in objectstack-data — only kernel / service-level events live here.

0
installs
▌
Checklist Test · objectstack-ai
Execute the platform test checklist (docs/qa/platform-checklist/) against a real running app and produce a run record. Use whenever the maintainer says "测一下 <功能>", "跑这个测试项", "run the checklist for <area/item>", "test this feature file", "验证 <功能点>", or points at a framework source file and asks whether it still works. Takes a SELECTOR (item id · area · capability kind · priority · a release · or a source-file path) and drives every matched item through its steps following RUNNER.md. The companion to `checklist-author` (which AUTHORS items); this one RUNS them. NOT a customer-published skill — internal agent tooling (lives in .claude/, never in the published `skills/` dir).

0
installs
▌
Objectstack Automation · objectstack-ai bundle
Design ObjectStack automation — Flows (visual logic), Triggers, Approvals, state machines, and the `jobs` (`defineJob`) / `webhooks` (`defineWebhook`) stack collections. Use when the user is adding `*.flow.ts`, wiring an event-driven rule, modelling an approval chain, or building an interactive screen flow / wizard (objectstack-ui routes those here). Do not use for data lifecycle hooks at the object layer (see objectstack-data) or for kernel / plugin events (see objectstack-platform). CEL expressions in flow conditions / edge guards: load objectstack-formula alongside.

0
installs
▌
Objectstack Pm Dispatch · objectstack-ai bundle
Run a project-manager dispatch loop over a GitHub backlog: triage and queue ready issues, claim each one, dispatch it to a parallel developer agent that returns a structured JSON report, review the results against GitHub, and drive accepted pull requests to landing — escalating to the maintainer only what genuinely needs a human decision. Ships the developer-agent operating template the loop injects into every dispatch (no custom agent types required). Use when asked to "work through the backlog", "batch-dispatch issues", "派发 issue 给开发 agent", or to stand up a multi-agent delivery loop in an ObjectStack app project. Do not use for authoring ObjectStack metadata (the domain skills cover that), for a single already-scoped change you can just make, or as a replacement for the project's own conventions file — that file always wins.

0
installs
▌
Checklist Author · objectstack-ai
Re-audit the platform test checklist (docs/qa/platform-checklist/) for coverage gaps and author the missing items — the five-angle capability sweep. Use whenever the maintainer says "跑一轮 coverage sweep", "run a coverage sweep", "排查测试清单遗漏", "审计测试覆盖", or asks whether some platform surface "有测试吗" and the answer needs verifying rather than recalling. Also the right tool after a large platform surface lands or before a major release. NOT a customer-published skill — this is internal agent tooling (lives in .claude/, never in the published `skills/` dir).

0
installs
▌
Dogfood Verification · objectstack-ai
Internal process for dogfooding the ObjectStack platform — booting a real example app (showcase / CRM) and driving it in a browser as a real user or admin to find runtime bugs that static checks and unit tests miss, then fixing and shipping cleanly. Use whenever the task is "verify in the browser", "act as a real admin/user", "dogfood the Setup/Studio app", or browser-verify a change in the running app. NOT a customer-published skill — this is internal agent tooling (lives in .claude/, never in the published `skills/` dir).

0
installs
▌
Spec Property Retirement · objectstack-ai
Internal playbook for retiring an authorable `packages/spec` property under ADR-0049 enforce-or-remove — choosing the removal route, the liveness-ledger discipline each route implies, the ADR-0087 conversion, the generated baselines, forms, docs and pin tests a removal needs, and the gates that fail when any of it is missing. Use when a metadata key is declared-but-unenforced and the job is to REMOVE it, or when a ledger `dead` verdict needs confirming before you act on it: "retire this property", "enforce-or-remove", "the ledger says dead", "remove the inert key", "close out the liveness worklist". NOT a customer-published skill — internal agent tooling (lives in .claude/, never in the published `skills/` dir).

0
installs

20 published skills