Agent Skills
› xberg-io/xberg
› xberg-typescript-toolchain
xberg-typescript-toolchain
GitHub规范 Xberg TypeScript/JS 仓库的构建、测试及依赖管理流程，明确使用 poly、Vitest 等工具链约定。
Trigger Scenarios
修改 TS/JS 包代码或配置
执行 lint/format/test/build 任务
处理 pnpm/npm 依赖工作区问题
Install
npx skills add xberg-io/xberg --skill xberg-typescript-toolchain -g -y
SKILL.md
Frontmatter
{
"name": "xberg-typescript-toolchain",
"type": "Playbook",
"title": "Xberg Typescript Toolchain",
"x-ai-rulez": {
"id": "xberg-typescript-toolchain",
"kind": "skill",
"metadata": {
"name": "xberg-typescript-toolchain"
}
},
"description": "Work on Xberg TypeScript or JavaScript packages with the repository's actual poly, pnpm, npm, Vitest, napi-rs, wasm-pack, and integration-package boundaries. Load for TS\/JS tooling or package changes, not Rust-only binding generation."
}
Xberg TypeScript toolchain
These repository-specific facts override generic TypeScript conventions where they differ.
- Lint and format with
poly lint .andpoly fmt .. Poly embeds oxlint and oxfmt; do not install or invoke oxlint, oxfmt, Prettier, ESLint, or Biome directly, and do not add per-package lint scripts. - Root
tsconfig.jsonenables strict checking options and is a project-reference root fore2e/nodeande2e/wasm. Confirm that the package being changed is included before treating a root typecheck as evidence. - Testing uses Vitest with
@vitest/coverage-v8. No coverage threshold is enforced unless one is added to current configuration. - No runtime schema-validator dependency is guaranteed. Use existing boundary guards or propose a dependency explicitly rather than assuming Zod is available.
- The pnpm workspace uses the root lockfile. Packages under
integrations/node/are outside that workspace and use their own npm lockfiles. Determine ownership before installing or updating dependencies. integrations/node/{langchain,llamaindex}-xberguse tsup. The Node binding is built by napi-rs and the WASM binding by wasm-pack; do not add an application bundler to either binding.- Prefer
workspace:*for new dependencies between packages that are actually in the pnpm workspace. - JavaScript dependency auditing is manual unless a current workflow says otherwise; do not claim an audit ran merely because Rust or poly checks passed.
Version History
- 3be78fd Current 2026-10-19 16:31
- d8e4815 2026-08-28 18:31
