Run any Skill in Manus with one click

tooling-and-dependencies

Use when running repo scripts, adding or changing dependencies, editing package.json files, installing packages, or deciding how Bun workspace commands should be invoked in this monorepo.

Run Skill in Manus

Stars5,105

Forks146

UpdatedJune 5, 2026 at 22:22

Source

pierrecomputer

pierrecomputer/pierre

View GitHub Repository View Creator Repositories

Install command

Download

Run Skill in Manus

SKILL.md

readonly

name	tooling-and-dependencies
description	Use when running repo scripts, adding or changing dependencies, editing package.json files, installing packages, or deciding how Bun workspace commands should be invoked in this monorepo.

Tooling and Dependencies

Bun

Use bun exclusively for commands and package operations.
Do not use npm, pnpm, npx, or other package runners unless there is a specific reason and you explain it.
Bun can run TypeScript directly, so local scripts may be .ts files without a separate compile step.

Dependency Catalog

This monorepo uses Bun's workspaces.catalog in the root package.json.

Never add a version directly to an individual package's package.json by default.
To add a dependency:
1. Add the exact version to the root package.json under workspaces.catalog, for example "new-package": "1.2.3".
2. Reference it from the package with "new-package": "catalog:".
Do not run bun add <package> inside a package directory; it writes direct versions and breaks the catalog pattern.
Published packages may intentionally use ranges for end-user compatibility. apps/docs should use catalog versions; published packages such as packages/diffs may use ranges only when that is intentional.

Scripts

Package scripts should work from the package directory.
Common scripts may be mirrored at the root as shortcuts. A root mirror should not behave differently from the package script it wraps.
Use the workspace runner when convenient:

bun ws <project> <task>
bun ws <project> <task> --some --flag

bun ws forwards arguments to the target script and does not require a standalone -- separator. The only special handling is that -v and --verbose are consumed by scripts/ws.ts.

More from this repository

same repository

git-commits

pierrecomputer/pierre

Use when preparing, splitting, reviewing, or creating git commits in this repo, especially after larger implementations that should be broken into independently verified commits.

2026-06-075.1k

browser-automation

pierrecomputer/pierre

Use when opening, inspecting, clicking, filling, snapshotting, or otherwise automating web pages for this repo, including local dev servers and browser-based verification.

2026-06-055.1k

performance

pierrecomputer/pierre

Use when changing loops, collection processing, invalidation logic, tree/diff traversal, path scanning, virtualized rendering calculations, or any code where repeated scans or boolean control flow affect performance or correctness.

2026-06-055.1k

testing-and-verification

pierrecomputer/pierre

Use when adding or running tests, checking snapshots, choosing between Bun tests and Playwright, running lint/format/typecheck, or deciding the verification scope for a change.

2026-06-055.1k

typescript-monorepo

pierrecomputer/pierre

Use when adding or changing packages/apps, TypeScript configs, workspace dependencies, package references, exports, or monorepo project-reference relationships.

2026-06-055.1k

worktrees-and-dev-servers

pierrecomputer/pierre

Use when working with the repo's bun run wt helper, Pierre-managed worktrees, dev-server port offsets, stale server cleanup, Playwright fixtures, or Chrome debug instances. Do not use this as a substitute for host-provided workspace isolation.

2026-06-055.1k

name	tooling-and-dependencies
description	Use when running repo scripts, adding or changing dependencies, editing package.json files, installing packages, or deciding how Bun workspace commands should be invoked in this monorepo.

Tooling and Dependencies

Bun

Use bun exclusively for commands and package operations.
Do not use npm, pnpm, npx, or other package runners unless there is a specific reason and you explain it.
Bun can run TypeScript directly, so local scripts may be .ts files without a separate compile step.

Dependency Catalog

This monorepo uses Bun's workspaces.catalog in the root package.json.

Never add a version directly to an individual package's package.json by default.
To add a dependency:
1. Add the exact version to the root package.json under workspaces.catalog, for example "new-package": "1.2.3".
2. Reference it from the package with "new-package": "catalog:".
Do not run bun add <package> inside a package directory; it writes direct versions and breaks the catalog pattern.
Published packages may intentionally use ranges for end-user compatibility. apps/docs should use catalog versions; published packages such as packages/diffs may use ranges only when that is intentional.

Scripts

Package scripts should work from the package directory.
Common scripts may be mirrored at the root as shortcuts. A root mirror should not behave differently from the package script it wraps.
Use the workspace runner when convenient:

bun ws <project> <task>
bun ws <project> <task> --some --flag

bun ws forwards arguments to the target script and does not require a standalone -- separator. The only special handling is that -v and --verbose are consumed by scripts/ws.ts.