bun-workspace
Skill1 starsChanged 6 months agoMITView on GitHub
Use when working with Bun package management, Bun workspaces, bun.lock, package scripts, Bun runtime APIs, Bun build commands, or Node/npm-to-Bun command translation in this repo.
In this repository28 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-self-checkSkill
- biome-grit-rulesSkill
- biome-toolingSkill
- bun-testSkill
- cleanup-auditSkill
- code-reviewSkill
- dispatch-satelliteSkill
- docs-managementSkill
- docs-readingSkill
- effect-concurrency-lifecycleSkill
- effect-errors-schemaSkill
- effect-observability-timeSkill
- effect-services-layersSkill
- effect-testing-runtimeSkill
- effect-v4Skill
- jsx-md-authoringSkill
- monorepo-maintenanceSkill
- refactoring-disciplineSkill
- roadmap-managementSkill
- runtime-engineSkill
- server-runtimeSkill
- testing-patternsSkill
- theseus-designSkill
- tool-authoringSkill
- typescript-strictSkill
- ui-layout-disciplineSkill
- theseus-designSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. About 0 are common, 8 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 8
Use this skill for Bun runtime and workspace operations.
- Very specific: line 35
Read the relevant package.json before running scripts.
- Distinctive: line 36
Prefer existing scripts over raw binaries.
- Very specific: line 37
Use bun run <script> for scripts.
- Very specific: line 38
Use bunx <tool> only when no script exists and the tool is already an intended dev tool.
- Very specific: line 39
Use bun add, bun add -d, and bun remove for dependency changes.
- Very specific: line 40
Use workspace dependencies as workspace:* for local packages.
- Distinctive: line 41
Do not introduce npm, pnpm, yarn, or npx commands unless the user explicitly asks.
- Distinctive: line 45
Run broad checks from the root when cross-package types or exports changed.
- Distinctive: line 46
Run package-local scripts when the change is isolated and the package has the script.
- Distinctive: line 47
Keep package exports aligned with source entrypoints.
- Very specific: line 48
Do not edit generated dist/ output unless the task explicitly requires build artifacts.
- Very specific: line 49
If dependency installation or update is needed, expect bun.lock to change.
- Distinctive: line 53
Use Bun-native APIs when the package already targets Bun:
- Distinctive: line 58
Keep browser-safe packages free of Bun-only APIs.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Bun Workspace
Use this skill for Bun runtime and workspace operations.
Repo Facts
- Package manager: Bun.
- Workspace root:
package.jsonwithworkspaces: ["packages/*"]. - Lockfile:
bun.lock; do not hand-edit it. - Root scripts:
bun run lintbun run testbun run typecheckbun run effect:diagnosticsbun run effect:ls:checkbun run effect:ls:patch
- Package-local scripts exist under
packages/*/package.json.
Root Scripts
bun run effect:diagnostics- Effect language-service diagnostics for configured non-web packages.bun run effect:ls:check- check whether local TypeScript is patched for Effect diagnostics.bun run effect:ls:patch- patch local TypeScript so Effect diagnostics surface through build-time checks.bun run lint- Biome check.bun run test- Bun tests.bun run typecheck- TypeScript checks for the configured packages.
Command Rules
- Read the relevant
package.jsonbefore running scripts. - Prefer existing scripts over raw binaries.
- Use
bun run <script>for scripts. - Use
bunx <tool>only when no script exists and the tool is already an intended dev tool. - Use
bun add,bun add -d, andbun removefor dependency changes. - Use workspace dependencies as
workspace:*for local packages. - Do not introduce npm, pnpm, yarn, or npx commands unless the user explicitly asks.
Workspace Rules
- Run broad checks from the root when cross-package types or exports changed.
- Run package-local scripts when the change is isolated and the package has the script.
- Keep package exports aligned with source entrypoints.
- Do not edit generated
dist/output unless the task explicitly requires build artifacts. - If dependency installation or update is needed, expect
bun.lockto change.
Bun Runtime APIs
- Use Bun-native APIs when the package already targets Bun:
Bun.file/Bun.writefor simple file IO.Bun.spawnfor subprocesses.bun:sqlitefor SQLite.
- Normalize Bun API failures at the boundary; do not leak raw foreign errors through domain code.
- Keep browser-safe packages free of Bun-only APIs.
Verification
- Package manager or workspace changes:
bun install --frozen-lockfileif checking lockfile integrity. - Cross-package TypeScript changes:
bun run typecheck. - Script or runtime changes: run the relevant package script first, then root checks if the change crosses packages.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.