菜单
Use when adding or changing packages/apps, TypeScript configs, workspace dependencies, package references, exports, or monorepo project-reference relationships.
Use when preparing, splitting, reviewing, or creating git commits in this repo, especially after larger implementations that should be broken into independently verified commits.
Use when opening, inspecting, clicking, filling, snapshotting, or otherwise automating web pages for this repo, including local dev servers and browser-based verification.
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.
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.
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.
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.
| name | typescript-monorepo |
| description | Use when adding or changing packages/apps, TypeScript configs, workspace dependencies, package references, exports, or monorepo project-reference relationships. |
Use TypeScript everywhere practical. Compiler settings are intentionally fairly strict.
tsconfig.options.json.tsconfig.json manages project references across the monorepo.tsc scripts use tsgo, but agents should run them through the
package script: bun run tsc.When adding a new package or app:
tsconfig.json references.tsconfig.json follows existing package/app patterns.When one workspace package depends on another:
workspace:* in the consuming package.references block
when needed for accurate and fast typechecking.Use the dependency catalog rules from tooling-and-dependencies for external
packages. Use workspace:* for internal package dependencies.
If a package is published, review its exports, typesVersions, files, peer
dependencies, and publish scripts before changing public entrypoints or
dependency ranges.