What problem does it solve?
Working on the Xberg repository's TypeScript and JavaScript packages requires knowing its non-standard toolchain: poly for linting and formatting, a pnpm workspace with exceptions, and napi-rs/wasm-pack bindings. Generic TypeScript conventions lead to wrong commands, misplaced dependencies, and invalid assumptions about tooling.
Core Features & Use Cases
- Toolchain Guardrails: Enforces
poly lint and poly fmt instead of directly invoking oxlint, oxfmt, Prettier, ESLint, or Biome.
- Workspace Boundary Awareness: Distinguishes packages inside the pnpm workspace (using
workspace:* dependencies and the root lockfile) from integrations/node/ packages that use their own npm lockfiles.
- Build and Test Conventions: Clarifies Vitest with
@vitest/coverage-v8 for testing, tsup for integration packages, and napi-rs/wasm-pack for bindings without application bundlers.
- Use Case: When adding a dependency or fixing a lint error in a TypeScript package, load this Skill to determine whether the package belongs to the pnpm workspace and which commands are valid before making changes.
Quick Start
Load this Skill before modifying any TypeScript or JavaScript package in the Xberg repository and ask it to verify the correct lint, test, and dependency workflow for that package.