← ClaudeAtlas

bun-scriptinglisted

Use when writing helper scripts, utility tasks, or automation within the R&D pipeline — prefer Bun (TypeScript) over Python when available
oleksify/rnd-framework · ★ 0 · AI & Automation · score 75
Install: claude install-skill oleksify/rnd-framework
# Bun as Preferred Scripting Runtime When the `bun` binary is available on the system, **prefer Bun (TypeScript) over Python** for helper scripts, utility tasks, and automation. Bun provides faster startup, built-in TypeScript support, and a rich set of zero-dependency APIs that cover most scripting needs. ## Detection Before writing a helper script, check for Bun availability: ```bash command -v bun >/dev/null 2>&1 ``` If `bun` is present, write the script in TypeScript and run it with `bun run script.ts`. If `bun` is not available, fall back to Python as usual. ## Rules 1. **Single-file `.ts` scripts only.** No project setup, no `package.json`, no `tsconfig.json` needed. 2. **Never run `bun install`, `bun add`, or use any npm packages.** Use only Bun built-in APIs and Node.js compatible standard modules. 3. **Allowed imports are strictly limited to:** - `Bun.*` globals (always available, no import needed) - `bun:sqlite` — embedded SQLite - `bun:ffi` — foreign function interface (only if calling system C libraries) - `node:fs`, `node:fs/promises` — file system operations - `node:path` — path manipulation - `node:child_process` — spawning processes - `node:os` — OS information - `node:crypto` — hashing and cryptography - `node:util` — utilities like `promisify`, `TextDecoder` - `node:stream` — stream primitives - `node:url` — URL parsing - `node:zlib` — compression - `node:assert` — assertions - `node:buffer` — binary data hand