monorepo-bun

Define a Bun-based monorepo structure with workspace conventions for multi-package projects.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Defines a standard Bun-based monorepo structure with workspace conventions for multi-package projects.

Core Features & Use Cases

  • Structure guidelines for apps/ and packages/ directories.
  • Root configuration patterns and TypeScript path mappings across packages.
  • Reusable conventions for cross-package references and shared tooling.

Quick Start

Set up a Bun-based monorepo following the apps/* and packages/* layout, then run bun install.

Frequently Asked Questions about monorepo-bun

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

FAQPage Schema
How do I structure a Bun monorepo with multiple packages?

A standard Bun monorepo structure uses apps/ and packages/ directories to organize multi-package projects. You define workspace conventions in the root package.json to manage cross-package references and shared tooling.

How do I set up TypeScript path mappings across packages in a Bun workspace?

TypeScript path mappings in a Bun workspace are configured at the root level to resolve cross-package references. This ensures that imports between packages in the apps/ and packages/ directories map correctly.

Can I use Biome for shared tooling in a Bun monorepo?

Yes, Biome can be used for shared tooling in a Bun monorepo. Root configuration patterns allow you to apply consistent linting and formatting across all workspace packages.

What is the best way to manage root configuration for Bun workspaces?

The best way to manage root configuration for Bun workspaces is to centralize settings in the root package.json. This approach standardizes workspace conventions and shared tooling for all included packages.

Does Bun work with standard monorepo layouts like apps and packages?

Bun works seamlessly with standard monorepo layouts using apps/* and packages/* directories. You simply define these workspaces in your root package.json and run bun install to link them.

Why define workspace conventions for a Bun-based monorepo?

Defining workspace conventions for a Bun-based monorepo standardizes project structure and cross-package references. This ensures consistent TypeScript paths and root configurations across multi-package projects.