How do I install the Package Configuration skill?

Run npx skillmds@latest add tomevault-io/package-configuration in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Package Configuration safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Package Configuration?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Package Configuration free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Package Configuration?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Package Configuration by tomevault-io

Name: Package Configuration
Author: tomevault-io

Package Configuration

Configure workspace apps or packages to match the repo-wide Vite/Vitest/Turbo conventions (aliases, shared TypeScript configs, scripts, and caching). Use when Codex needs to set up or change tooling for an app/package or explain how the dev/test/build pipeline is wired across workspaces. Use when this capability is needed.

tomevault-io c791158 2 files · 3.9 KB Updated Sep 17, 2026

File contents

Package configuration reference

Follow this skill whenever you touch tooling for an app or package (Vite, Vitest, or Turbo). The guidance keeps tooling aligned with existing workspace conventions.

Vite + Vitest wiring

Start from the React app templates in apps/mvvm-react and apps/task-flow-ui. The Vite configs there define the alias maps (e.g., linking @repo/models, @repo/view-models, @web-loom/mvvm-core, @web-loom/ui-core, etc., to ../../packages/...) and the plugin stack (@vitejs/plugin-react-swc). Extend the alias resolver whenever you expose a new shared package; keep optimizeDeps.include in sync when dependencies must be pre-bundled. See references/vite-and-vitest.md for the patterns.
Vitest uses the same alias map so tests resolve workspace packages the way builds do. The shared test config blocks (globals, jsdom environment, coverage filters, setupFiles) are already captured in apps/mvvm-react/vitest.config.ts.

Turbo repository pipelines

Root turbo.json governs caching and task dependencies (build, lint, check-types, test, dev). Keep new tasks aligned with these definitions: e.g., dev is marked cache: false and persistent: true, while test depends on ^build. When adding a new app/package, give it the standard scripts (dev, build, lint, test, check-types) so Turbo can orchestrate it out-of-the-box. Refer to turbo.json for inputs/outputs and to the root package.json scripts (e.g., npm run dev, npm run test) that wrap turbo run.

TypeScript + workspace sharing

Every package relies on @repo/typescript-config variants (base.json, react-library.json, etc.). Extend or compose those configs when adding new tsconfig(s). Make sure tsconfig.json references the correct root packages/typescript-config. When publishing or building, run npm run check-types/tsc --noEmit via Turbo so emitted dist artifacts stay accurate.
Share code through the apps/* and packages/* workspace layout defined in the root package.json. Depend on packages with workspace ranges ("@repo/shared": "*") and export from each package via exports/main/types so Vite/Vitest/Turbo resolve them correctly.

Verification checklist

npm run lint, npm run check-types, npm run test (or filtered Turbo task) succeed from the workspace root.
npm run dev (or turbo run dev --filter=<app>...) starts the intended app—watch the console for alias resolution warnings.
Any new package gets referenced aliases updated in the Vite/Vitest configs and the packages/typescript-config setups.

See references/vite-and-vitest.md for concrete config snippets derived from the existing apps.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: package-configurationdescription: Configure workspace apps or packages to match the repo-wide Vite/Vitest/Turbo conventions (aliases, shared TypeScript configs, scripts, and caching). Use when Codex needs to set up or change tooling for an app/package or explain how the dev/test/build pipeline is wired across workspaces. Use when this capability is needed.---# Package configuration referenceFollow this skill whenever you touch tooling for an app or package (Vite, Vitest, or Turbo). The guidance keeps tooling aligned with existing workspace conventions.## Vite + Vitest wiring- Start from the React app templates in `apps/mvvm-react` and `apps/task-flow-ui`. The Vite configs there define the alias maps (e.g., linking `@repo/models`, `@repo/view-models`, `@web-loom/mvvm-core`, `@web-loom/ui-core`, etc., to `../../packages/...`) and the plugin stack (`@vitejs/plugin-react-swc`). Extend the alias resolver whenever you expose a new shared package; keep `optimizeDeps.include` in sync when dependencies must be pre-bundled. See `references/vite-and-vitest.md` for the patterns.- Vitest uses the same alias map so tests resolve workspace packages the way builds do. The shared `test` config blocks (globals, `jsdom` environment, coverage filters, `setupFiles`) are already captured in `apps/mvvm-react/vitest.config.ts`.## Turbo repository pipelines- Root `turbo.json` governs caching and task dependencies (`build`, `lint`, `check-types`, `test`, `dev`). Keep new tasks aligned with these definitions: e.g., `dev` is marked `cache: false` and `persistent: true`, while `test` depends on `^build`. When adding a new app/package, give it the standard scripts (`dev`, `build`, `lint`, `test`, `check-types`) so Turbo can orchestrate it out-of-the-box. Refer to `turbo.json` for inputs/outputs and to the root `package.json` scripts (e.g., `npm run dev`, `npm run test`) that wrap `turbo run`.## TypeScript + workspace sharing- Every package relies on `@repo/typescript-config` variants (`base.json`, `react-library.json`, etc.). Extend or compose those configs when adding new tsconfig(s). Make sure `tsconfig.json` references the correct root `packages/typescript-config`. When publishing or building, run `npm run check-types`/`tsc --noEmit` via Turbo so emitted `dist` artifacts stay accurate.- Share code through the `apps/*` and `packages/*` workspace layout defined in the root `package.json`. Depend on packages with workspace ranges (`"@repo/shared": "*"`) and export from each package via `exports`/`main`/`types` so Vite/Vitest/Turbo resolve them correctly.## Verification checklist1. `npm run lint`, `npm run check-types`, `npm run test` (or filtered Turbo task) succeed from the workspace root.2. `npm run dev` (or `turbo run dev --filter=<app>...`) starts the intended app—watch the console for alias resolution warnings.3. Any new package gets referenced aliases updated in the Vite/Vitest configs and the `packages/typescript-config` setups.See [references/vite-and-vitest.md](references/vite-and-vitest.md) for concrete config snippets derived from the existing apps.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/bretuobay) — claim your Tome and manage your conversions.

Frequently asked questions