bun

Route Bun questions to runtime, test, or package manager sub-skills.

1|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/matthewharwood/dean-stack --skill bun-matthewharwood
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bun
Source: https://github.com/matthewharwood/dean-stack/tree/main/.claude/skills/bun
Command: npx skills add https://github.com/matthewharwood/dean-stack --skill bun-matthewharwood

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route Bun questions to the right sub-skill (runtime, test, or package manager) and pin Bun 1.3.13 for consistent tooling.

Core Features & Use Cases

  • Routing: Directs Bun-related queries to bun-runtime, bun-test, or bun-package-manager based on user intent.
  • Pinning: Enforces Bun 1.3.13 via packageManager to ensure deterministic installs.
  • Use Case: Ask "how do I pin Bun" or "what Bun version is installed" to get the right guidance.

Quick Start

Route Bun questions to the correct sub-skill and confirm Bun 1.3.13 is pinned via packageManager.

Frequently Asked Questions about bun

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I pin Bun to a specific version in my project?

You can pin Bun 1.3.13 by configuring the packageManager field, which enforces deterministic installs and ensures consistent tooling behavior across your local environment.

What is the best way to route Bun runtime questions versus test or package manager queries?

Routing Bun questions involves directing queries to bun-runtime, bun-test, or bun-package-manager based on user intent. This ensures you get accurate guidance for installation, runtime behavior, or testing within the dean-stack context.

How does the Bun package manager pinning mechanism work?

Bun package manager pinning works by enforcing version 1.3.13 through the packageManager field. This mechanism intercepts triggers like 'which bun' or 'bun overview' to guarantee deterministic tooling setups.

Can I use this routing approach for general Bun installation and overview queries?

Yes, this routing approach applies when users ask for Bun installation, runtime behavior, or an overview within the dean-stack context. It dispatches your query to the correct sub-skill for targeted guidance.

Why do I need to pin Bun 1.3.13 for my runtime and test environments?

Pinning Bun 1.3.13 is needed to ensure deterministic installs and consistent tooling across runtime and test environments. It prevents version drift by enforcing the specified packageManager configuration.

When should I not use automated Bun routing for my sub-skills?

You should not use automated Bun routing if your queries fall outside runtime, test, or package manager scopes. The routing table specifically dispatches to bun-runtime, bun-test, or bun-package-manager and ignores unrelated intents.