bun-runtime
Bun JavaScript runtime, bundler, and package manager. Covers Bun.serve() HTTP server, Bun.file() I/O, SQLite, password hashing, Bun.build() bundler, bun:test runner, and package management. Use when building with Bun APIs, running scripts with Bun, bundling code, managing packages with bun install/add, or writing tests with bun:test.
What this skill does
# Bun Runtime
## Overview
Bun is an all-in-one JavaScript and TypeScript runtime that includes a fast package manager, bundler, test runner, and Node.js-compatible APIs. It natively executes TypeScript and JSX without a separate compilation step.
**When to use:** Fast server-side JavaScript, TypeScript-first projects, replacing Node.js for better startup performance, built-in SQLite, password hashing, file I/O, HTTP servers, bundling, and testing without external tooling.
**When NOT to use:** Projects requiring full Node.js ecosystem compatibility (some native modules unsupported), production environments needing battle-tested stability of Node.js, or browser-only code that does not need a runtime.
## Quick Reference
| Pattern | API | Key Points |
| ---------------- | ----------------------------------------- | -------------------------------------------------------- |
| HTTP server | `Bun.serve({ routes, fetch })` | Route-based, static/dynamic routes, per-method handlers |
| File read | `Bun.file(path)` | Lazy BunFile (Blob), `.text()`, `.json()`, `.stream()` |
| File write | `Bun.write(dest, data)` | Accepts string, Blob, Response, BunFile |
| SQLite | `new Database(path)` from `bun:sqlite` | Synchronous queries, prepared statements, WAL mode |
| Password hash | `Bun.password.hash(pw)` | Argon2id default, bcrypt option, async and sync variants |
| Password verify | `Bun.password.verify(pw, hash)` | Auto-detects algorithm from hash format |
| Bundler | `Bun.build({ entrypoints, outdir })` | Tree-shaking, code splitting, plugins, multiple targets |
| Test runner | `import { test, expect } from "bun:test"` | Jest-compatible, mocking, snapshots, watch mode |
| Install packages | `bun install` | Fast lockfile resolution, npm-compatible |
| Add package | `bun add <pkg>` | `-d` for dev, `-g` for global |
| Run script | `bun run <script>` | Runs package.json scripts or files directly |
| Execute binary | `bunx <pkg>` | Like npx, runs without installing |
| S3 client | `new S3Client(opts)` / `s3.file(key)` | Built-in S3-compatible storage client |
| HTML imports | `import page from './index.html'` | Fullstack: import HTML as route handler |
## Common Mistakes
| Mistake | Correct Pattern |
| ----------------------------------------------------- | --------------------------------------------------------------------------------- |
| Using `fetch` handler only without `routes` | Use `routes` object for static/dynamic routing (Bun v1.2.3+), `fetch` as fallback |
| Forgetting `await` on `Bun.write()` | `Bun.write()` is async, always await it |
| Using `Bun.file(path).text()` without `await` | `.text()`, `.json()`, `.arrayBuffer()` all return Promises |
| Creating SQLite database without WAL mode | Enable WAL for concurrent reads: `db.exec("PRAGMA journal_mode = WAL")` |
| Using `bun install` without `--frozen-lockfile` in CI | Use `bun install --frozen-lockfile` for reproducible CI builds |
| Importing `jest` globals in Bun tests | Import from `bun:test`, not `@jest/globals` or `vitest` |
| Using `node_modules/.bin/` directly | Use `bunx` or `bun run` instead of referencing bin paths |
| Expecting `Bun.build()` to throw on failure | Check `result.success` boolean, errors are in `result.logs` |
| Using `--target node` when deploying to Bun | Use `--target bun` for Bun-specific optimizations and bytecode |
| Synchronous password hashing in request handlers | Use `await Bun.password.hash()` async variant in servers |
## Delegation
- **Project scaffolding**: Use `Explore` agent
- **Performance profiling**: Use `Task` agent
- **Code review**: Delegate to `code-reviewer` agent
> If the `typescript-patterns` skill is available, delegate advanced TypeScript typing questions to it.
## References
- [Runtime APIs: Bun.serve(), Bun.file(), SQLite, password hashing, and utilities](references/runtime-apis.md)
- [Package management: install, add, remove, workspaces, lockfile](references/package-management.md)
- [Bundler: Bun.build(), entrypoints, plugins, tree-shaking](references/bundler.md)
- [Testing: bun:test, assertions, mocking, snapshots, lifecycle hooks](references/testing.md)
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.