[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70FNW6W7Z409QED1EHHDNSM":3,"skill-same:01M70FNW6W7Z409QED1EHHDNSM":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M70FNW6W7Z409QED1EHHDNSM","bun-runtime",null,"Bun as runtime, package manager, bundler, and test runner. When to choose Bun vs Node, migration notes, and Vercel support.","mdnaimul22\u002Fhuman-skills","mdnaimul22","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F64520358?v=4","01M70FH95MH2H796Q01TYSFZ03","Naimul","01M70FH96798CQR4YHA13F17GA",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fbun-runtime\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"runtime","bun runtime","bun","vercel","when","bundler","manager","as","runner","migration","support","node","choose","package","notes","package manager","test runner","test","2026-11-10 10:12:30",false,"---\nname: bun-runtime\ndescription: Bun as runtime, package manager, bundler, and test runner. When to choose Bun vs Node, migration notes, and Vercel support.\nmetadata:\n  origin: ECC\n---\n\n# Bun Runtime\n\nBun is a fast all-in-one JavaScript runtime and toolkit: runtime, package manager, bundler, and test runner.\n\n## When to Use\n\n- **Prefer Bun** for: new JS\u002FTS projects, scripts where install\u002Frun speed matters, Vercel deployments with Bun runtime, and when you want a single toolchain (run + install + test + build).\n- **Prefer Node** for: maximum ecosystem compatibility, legacy tooling that assumes Node, or when a dependency has known Bun issues.\n\nUse when: adopting Bun, migrating from Node, writing or debugging Bun scripts\u002Ftests, or configuring Bun on Vercel or other platforms.\n\n## How It Works\n\n- **Version baseline**: guidance below targets Bun 1.4.x. Check the actual version with `bun --version` before relying on flag names, since CLI flags can change between releases.\n- **Runtime**: Drop-in Node-compatible runtime, built on JavaScriptCore. As of Bun 1.4 the runtime itself is implemented in Rust (migrated from Zig). Not 100% Node-compatible — some native addons, less-common `node:` internal APIs, and packages that depend on Node-specific internals can still fail; verify before depending on it in production.\n- **Package manager**: Bun includes a package manager; installation performance depends on the project, network conditions, and cache state. Lockfile is `bun.lock` (text) by default in current Bun; older versions used `bun.lockb` (binary) — Bun still reads that format for migration, but new projects should use `bun.lock`.\n- **Bundler**: Built-in bundler and transpiler for apps and libraries.\n- **Test runner**: Built-in `bun test` with a Jest-like API.\n\n**Migration from Node**: Replace `node script.js` with `bun run script.js` or `bun script.js`. Run `bun install` in place of `npm install`; most packages work. Use `bun run` for npm scripts; `bun x` for npx-style one-off runs. Node built-ins are supported; prefer Bun APIs where they exist for better performance.\n\n**Package and workspace commands**: `bun add \u003Cpkg>` \u002F `bun remove \u003Cpkg>` \u002F `bun update [pkg]` manage dependencies; `bun outdated` lists stale deps. `bun pm ls` lists project dependencies and resolved versions using the lockfile; `--all` includes transitive dependencies. It is not an integrity check of installed file contents. [`bun audit`](https:\u002F\u002Fbun.com\u002Fdocs\u002Fpm\u002Fcli\u002Faudit) queries registry advisories using package names and versions from `bun.lock`; it does not modify `package.json`, `bun.lock`, or `node_modules`. Review approved destinations before sending private package metadata. Packages whose scoped registry lacks an advisory endpoint are skipped and do not affect the exit code. `bun audit fix` upgrades and installs dependencies, changing the lockfile and installed packages and sometimes direct version pins; review it as a modifying install operation, including applicable lifecycle scripts. `bun dedupe` collapses duplicate installs, and `bun prune` removes packages no longer referenced. Monorepos use a root `workspaces` array in `package.json` (same convention as npm\u002Fyarn); run a script in one workspace with `bun run --filter \u003Cpkg-name> \u003Cscript>`.\n\n**Built-in APIs**: reach for these before adding a dependency — `Bun.file` \u002F `Bun.write` for file I\u002FO, `bun:sqlite` for an embedded SQLite database, `Bun.serve` for an HTTP\u002FWebSocket server, [`Bun.sql`](https:\u002F\u002Fbun.com\u002Fdocs\u002Fruntime\u002Fsql) for SQL databases, [`Bun.redis`](https:\u002F\u002Fbun.com\u002Fdocs\u002Fruntime\u002Fredis) for Redis, and [`Bun.S3Client`](https:\u002F\u002Fbun.com\u002Fdocs\u002Fruntime\u002Fs3) for S3-compatible object storage. See the [1.4 release notes](https:\u002F\u002Fbun.com\u002Fblog\u002Fbun-v1.4) for the rest of what's new.\n\n**Vercel**: Set `bunVersion: \"1.4.x\"` in `vercel.json` to use Bun 1.4 (Rust runtime). See [Vercel's Bun runtime docs](https:\u002F\u002Fvercel.com\u002Fdocs\u002Ffunctions\u002Fruntimes\u002Fbun). Build: `bun run build` or `bun build .\u002Fsrc\u002Findex.ts --outdir=dist`. Install: `bun install --frozen-lockfile` for reproducible deploys.\n\n**Reference**: [Bun 1.4 release notes](https:\u002F\u002Fbun.com\u002Fblog\u002Fbun-v1.4).\n\n## Examples\n\n### Run and install\n\n```bash\n# Install dependencies (creates\u002Fupdates bun.lock)\nbun install\n\n# Run a script or file\nbun run dev\nbun run src\u002Findex.ts\nbun src\u002Findex.ts\n```\n\n### Scripts and env\n\n```bash\nbun run --env-file=.env dev\nFOO=bar bun run script.ts\n```\n\n### Testing\n\n```bash\nbun test\nbun test --watch\n```\n\nFor CI on Bun 1.4, available options include `bun test --changed[=\u003Cref>]` for affected tests, `bun test --isolate` for per-file globals, `bun test --parallel[=\u003Cn>]` for worker processes, and `bun test --shard=\u003Cn>\u002F\u003Ccount>` for CI partitioning. `--isolate` creates a fresh JavaScript global for each file in the same process and cleans up documented per-file resources; it is not a process or security sandbox. `--parallel` enables it by default. `--timings=\u003Cfile>` reads prior durations for scheduling; `--update-timings` records durations. Example: `bun test --parallel --timings=.\u002Ftest-timings.json --update-timings`. Check the installed version's help and documentation before choosing timing-file paths for a multi-shard workflow.\n\n```typescript\n\u002F\u002F test\u002Fexample.test.ts\nimport { expect, test } from \"bun:test\";\n\ntest(\"add\", () => {\n  expect(1 + 2).toBe(3);\n});\n```\n\n### Runtime API\n\n```typescript\nconst file = Bun.file(\"package.json\");\nconst json = await file.json();\n\nBun.serve({\n  port: 3000,\n  fetch(req) {\n    return new Response(\"Hello\");\n  },\n});\n```\n\n## Best Practices\n\n- Commit the lockfile (`bun.lock`) for reproducible installs.\n- Prefer `bun run` for scripts. For TypeScript, Bun runs `.ts` natively.\n- Keep dependencies up to date; Bun and the ecosystem evolve quickly.\n","# Bun Runtime\n\nBun is a fast all-in-one JavaScript runtime and toolkit: runtime, package manager, bundler, and test runner.\n\n## When to Use\n\n- **Prefer Bun** for: new JS\u002FTS projects, scripts where install\u002Frun speed matters, Vercel deployments with Bun runtime, and when you want a single toolchain (run + install + test + build).\n- **Prefer Node** for: maximum ecosystem compatibility, legacy tooling that assumes Node, or when a dependency has known Bun issues.\n\nUse when: adopting Bun, migrating from Node, writing or debugging Bun scripts\u002Ftests, or configuring Bun on Vercel or other platforms.\n\n## How It Works\n\n- **Version baseline**: guidance below targets Bun 1.4.x. Check the actual version with `bun --version` before relying on flag names, since CLI flags can change between releases.\n- **Runtime**: Drop-in Node-compatible runtime, built on JavaScriptCore. As of Bun 1.4 the runtime itself is implemented in Rust (migrated from Zig). Not 100% Node-compatible — some native addons, less-common `node:` internal APIs, and packages that depend on Node-specific internals can still fail; verify before depending on it in production.\n- **Package manager**: Bun includes a package manager; installation performance depends on the project, network conditions, and cache state. Lockfile is `bun.lock` (text) by default in current Bun; older versions used `bun.lockb` (binary) — Bun still reads that format for migration, but new projects should use `bun.lock`.\n- **Bundler**: Built-in bundler and transpiler for apps and libraries.\n- **Test runner**: Built-in `bun test` with a Jest-like API.\n\n**Migration from Node**: Replace `node script.js` with `bun run script.js` or `bun script.js`. Run `bun install` in place of `npm install`; most packages work. Use `bun run` for npm scripts; `bun x` for npx-style one-off runs. Node built-ins are supported; prefer Bun APIs where they exist for better performance.\n\n**Package and workspace commands**: `bun add \u003Cpkg>` \u002F `bun remove \u003Cpkg>` \u002F `bun update [pkg]` manage dependencies; `bun outdated` lists stale deps. `bun pm ls` lists project dependencies and resolved versions using the lockfile; `--all` includes transitive dependencies. It is not an integrity check of installed file contents. [`bun audit`](https:\u002F\u002Fbun.com\u002Fdocs\u002Fpm\u002Fcli\u002Faudit) queries registry advisories using package names and versions from `bun.lock`; it does not modify `package.json`, `bun.lock`, or `node_modules`. Review approved destinations before sending private package metadata. Packages whose scoped registry lacks an advisory endpoint are skipped and do not affect the exit code. `bun audit fix` upgrades and installs dependencies, changing the lockfile and installed packages and sometimes direct version pins; review it as a modifying install operation, including applicable lifecycle scripts. `bun dedupe` collapses duplicate installs, and `bun prune` removes packages no longer referenced. Monorepos use a root `workspaces` array in `package.json` (same convention as npm\u002Fyarn); run a script in one workspace with `bun run --filter \u003Cpkg-name> \u003Cscript>`.\n\n**Built-in APIs**: reach for these before adding a dependency — `Bun.file` \u002F `Bun.write` for file I\u002FO, `bun:sqlite` for an embedded SQLite database, `Bun.serve` for an HTTP\u002FWebSocket server, [`Bun.sql`](https:\u002F\u002Fbun.com\u002Fdocs\u002Fruntime\u002Fsql) for SQL databases, [`Bun.redis`](https:\u002F\u002Fbun.com\u002Fdocs\u002Fruntime\u002Fredis) for Redis, and [`Bun.S3Client`](https:\u002F\u002Fbun.com\u002Fdocs\u002Fruntime\u002Fs3) for S3-compatible object storage. See the [1.4 release notes](https:\u002F\u002Fbun.com\u002Fblog\u002Fbun-v1.4) for the rest of what's new.\n\n**Vercel**: Set `bunVersion: \"1.4.x\"` in `vercel.json` to use Bun 1.4 (Rust runtime). See [Vercel's Bun runtime docs](https:\u002F\u002Fvercel.com\u002Fdocs\u002Ffunctions\u002Fruntimes\u002Fbun). Build: `bun run build` or `bun build .\u002Fsrc\u002Findex.ts --outdir=dist`. Install: `bun install --frozen-lockfile` for reproducible deploys.\n\n**Reference**: [Bun 1.4 release notes](https:\u002F\u002Fbun.com\u002Fblog\u002Fbun-v1.4).\n\n## Examples\n\n### Run and install\n\n```bash\n# Install dependencies (creates\u002Fupdates bun.lock)\nbun install\n\n# Run a script or file\nbun run dev\nbun run src\u002Findex.ts\nbun src\u002Findex.ts\n```\n\n### Scripts and env\n\n```bash\nbun run --env-file=.env dev\nFOO=bar bun run script.ts\n```\n\n### Testing\n\n```bash\nbun test\nbun test --watch\n```\n\nFor CI on Bun 1.4, available options include `bun test --changed[=\u003Cref>]` for affected tests, `bun test --isolate` for per-file globals, `bun test --parallel[=\u003Cn>]` for worker processes, and `bun test --shard=\u003Cn>\u002F\u003Ccount>` for CI partitioning. `--isolate` creates a fresh JavaScript global for each file in the same process and cleans up documented per-file resources; it is not a process or security sandbox. `--parallel` enables it by default. `--timings=\u003Cfile>` reads prior durations for scheduling; `--update-timings` records durations. Example: `bun test --parallel --timings=.\u002Ftest-timings.json --update-timings`. Check the installed version's help and documentation before choosing timing-file paths for a multi-shard workflow.\n\n```typescript\n\u002F\u002F test\u002Fexample.test.ts\nimport { expect, test } from \"bun:test\";\n\ntest(\"add\", () => {\n  expect(1 + 2).toBe(3);\n});\n```\n\n### Runtime API\n\n```typescript\nconst file = Bun.file(\"package.json\");\nconst json = await file.json();\n\nBun.serve({\n  port: 3000,\n  fetch(req) {\n    return new Response(\"Hello\");\n  },\n});\n```\n\n## Best Practices\n\n- Commit the lockfile (`bun.lock`) for reproducible installs.\n- Prefer `bun run` for scripts. For TypeScript, Bun runs `.ts` natively.\n- Keep dependencies up to date; Bun and the ecosystem evolve quickly.\n",{"name":5,"metadata":47,"description":7},{"origin":48},"ECC","main","74715deacdc69119d739f38916f8ee4f0f979ebf","skills\u002Fstorage\u002Faffaan-m_ECC\u002Fbun-runtime",0,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills","https:\u002F\u002Fgithub.com\u002Fmdnaimul22","AI Agents Workflows Automation | Specializing in Python, FastAPI, MCP Agents & Custom ERP.","2026-11-11 21:16:57",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add mdnaimul22\u002Fhuman-skills --skill bun-runtime",{"tool":63,"command":64},"bunx","bunx skills add mdnaimul22\u002Fhuman-skills --skill bun-runtime",{"tool":66,"command":67},"pnpm","pnpm dlx skills add mdnaimul22\u002Fhuman-skills --skill bun-runtime","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fbun-runtime\u002FSKILL.md",true,[],[72,80,88,95,102,109],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":79},"01M767791C1KRP2ZRW2Z73VZ5Q","system-lifecycle-designer","Universal architectural methodology for designing granular, atomic, and sub-atomic lifecycles and end-to-end workflows for single functionality integrations across any domain (daemons, batch jobs, request transactions, resource pools). Provides patterns for deterministic identity, pre-commit validation, differential reconciliation, sticky leasing, state machines, transactional persistence, and closed-loop feedback.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fmy_skills\u002Fsystem-lifecycle-designer\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":87},"01M748ABPN5F1FANHH6HKZQMXT","style-sampling","Make a new episode in a proven video style - Collage Explainer, Finance Explainer, Animated Science Explainer, 3D Brand Explainer, 3D True Crime - on the person's topic. Use for \"an episode of\", \"in the style of\", \"sample this style\", 「用这个风格做一集」. One video to copy is reverse-any-video.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Fstyle-sampling\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":87},"01M748A59V04PKW4HA0XQ81FGP","reverse-any-video","Rebuild any video file as an editable HyperFrames project - motion graphics, talking heads, live action or AI-generated footage - checked against the original frame by frame. Use to reverse, recreate, remake, replicate or copy a video, or 「复刻这个视频」「照着这个视频做一个」.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fheygen-com_hyperframes\u002Freverse-any-video\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":87},"01M7487T50P55CSXMWXZ0G9KRG","typescript-patterns","TypeScript patterns for strict, type-safe, maintainable code in modern TypeScript and JavaScript applications. Covers strict compiler configuration, type design, narrowing, discriminated unions, generics, async and error handling, module boundaries, dependency hygiene, and type-level testing. Use when writing or reviewing TypeScript or JavaScript code.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftypescript-patterns\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":87},"01M7487ERZRGPC5NJ75077Y238","test-collaboration","Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing test registry or TESTS.md. Use for test inventory, test gap analysis, unit\u002Fintegration\u002Fcontract\u002FE2E\u002Fsmoke classification, bug-to-test regression protection, consumer\u002Fprovider contract testing, test-necessity review, and pre-delivery evidence review.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Ftest-collaboration\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":87},"01M748721J3GKR2WS6K0QWFC35","story-lifecycle","Manage a file-based epic → story → sprint development loop without requiring an external project management tool. Creates and tracks epics, breaks them into user stories, assigns them to sprints, and drives implementation story by story. Use when starting a new feature initiative or when the team has no Jira\u002FLinear\u002FTaiga but needs structured delivery tracking.","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Fstory-lifecycle\u002FSKILL.md",[],[]]