monorepo-generator_skill

Overview

This skill generates production-ready monorepo structures for full-stack projects, including frontends (Next.js, React), APIs (Hono, Express), and data pipelines. It scaffolds workspace layouts, shared packages, and root tooling so teams can start building scalable multi-project architectures quickly.

How this skill works

I ask for the types of projects you need (web, api, pipelines, workers, CLI, mobile) and the preferred package manager (Bun, PNPM, Yarn). I generate a recommended directory layout (apps/, services/, packages/) with root package.json and Turbo configuration, plus per-project templates, TypeScript configs, and example scripts. The output includes workspace-aware dependencies, transpile/transpilePackages guidance, and example runtime scripts for development, build, and start.

When to use it

• Starting a new full-stack project that will contain multiple deployable apps and shared libraries.
• Scaffolding a team monorepo to enforce consistent tooling and workspace dependency management.
• Adding background jobs, ETL pipelines, or worker services alongside web and API projects.
• Migrating single repositories into a workspace to share UI, utils, and db clients.
• Setting up CI/CD and deployment boundaries for independently deployable projects.

Best practices

• Choose Bun for fast local dev or PNPM for strict deduplication; record choice in root packageManager.
• Keep deployable apps under apps/, backend services under services/, and reusable code in packages/.
• Use workspace:* references for shared internal packages and configure transpilePackages for Next.js.
• Add a root turbo.json (or equivalent) to define cross-package task dependencies and outputs.
• Provide shared TypeScript configs and ESLint configs in packages to enforce consistency.

Example use cases

• Create a Next.js storefront (apps/web), a Hono API (apps/api), and shared UI/components (packages/ui).
• Scaffold data pipelines that run ETL jobs under services/pipelines with reusable db and utils packages.
• Add a scheduled job worker that uses cron and accesses the monorepo db package.
• Bootstrap multiple admin dashboards by copying the frontend template into apps/dashboard and updating names.
• Prepare independent deployment pipelines so each app/service can be built and deployed separately.