bun-developer

Enforce Bun-native development practices and anti-pattern avoidance for TypeScript projects.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/Yoraexe/ceobe --skill bun-developer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bun-developer
Source: https://github.com/Yoraexe/ceobe/tree/main/skills/bun-developer
Command: npx skills add https://github.com/Yoraexe/ceobe --skill bun-developer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces Bun-native development practices and anti-pattern avoidance for TypeScript projects. This skill standardizes tooling choices, accelerates performance, and reduces Node.js dependency drift by guiding teams to adopt Bun as the primary runtime and package manager.

Core Features & Use Cases

  • Bun-centric workflow: replace Node.js/npm with Bun for installation, execution, and development tasks to improve speed and consistency.
  • Anti-pattern enforcement: disallow the use of npm, node, and Express, and promote Bun equivalents throughout the project lifecycle.
  • Guidance on runtime and tooling choices: recommends Bun-based testing, HTTP server patterns, and native Bun APIs for common tasks.

Quick Start

Activate the bun-developer skill to enforce Bun-native tooling for your new TypeScript project.

Frequently Asked Questions about bun-developer

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

FAQPage Schema
How do I replace Node.js and npm with Bun for TypeScript development?

You should use Bun instead of Express by adopting native Bun APIs and Bun-based HTTP server patterns, as this skill enforces anti-pattern avoidance by disallowing Express in favor of Bun equivalents throughout the project lifecycle.

Does this Bun workflow enforce anti-patterns for Node.js tooling?

Yes, the workflow validates configurations and disallows the use of npm, node, and Express, actively enforcing anti-pattern avoidance to guide teams toward Bun equivalents for all typical project lifecycle tasks.

What is the best way to configure a Bun-native TypeScript project lifecycle?

The best way is to standardize tooling choices by applying Bun across initialization, dependency management, and runtime execution, validating sample workflows to ensure Bun is used instead of Node.js.

Do I need Bun installed to enforce these TypeScript development guidelines?

Yes, you need Bun present in your environment before activating this skill, as it requires Bun to be installed to validate configurations and enforce Bun-native development practices for your TypeScript projects.

When should I avoid using Node.js tooling in favor of Bun runtime?

You should avoid Node.js tooling when you need to reduce dependency drift and accelerate performance in TypeScript projects, standardizing on Bun for testing, HTTP server patterns, and common tasks.