Menu
Use when asked to setup or initialize a new monorepo
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Bun is an all-in-one JavaScript/TypeScript toolkit that ships as a single binary. It includes a runtime (drop-in Node.js replacement), package manager, test runner, and bundler.
Use when configuring .oxlintrc.json or lint-related CI
WXT web extension framework — entrypoints, manifest generation, content scripts/UI, storage, messaging, modules, CLI, browser targets, publishing. Use when building, debugging, configuring, migrating, or publishing browser/web extensions with WXT.
Read this skill before serving as orchestrator
Read before writing user-facing docs — READMEs, tutorials, how-to guides, reference docs, or any prose for human readers. Use when creating or substantially editing docs aimed at users rather than agent-facing files like AGENTS.md.
Delegate work to configured subagents with single-agent, chain, parallel, async, forked-context, and intercom-coordinated workflows. Use only agents discovered from user or project Markdown agent files.
| name | setup-new-monorepo |
| description | Use when asked to setup or initialize a new monorepo |
When you're asked to set up a new monorepo, these decisions are already made — don't re-litigate them with the user, just apply them:
catalog for all non-dev dependencies and catalog:dev for all dev-only dependencies. Do not introduce additional subcatalogs beyond catalog:dev.bun run check before commit..env (start empty), .envrc that loads .env via direnv's dotenv./Users/m/repos/mydb/ is the reference for what "set up correctly" looks like in this house. When in doubt about shape, naming, or values — read the relevant file there and match it. In particular:
package.json — workspaces layout (packages/*, bindings/*, apps/*), catalog/catalogs structure, the check / typecheck / lint / fmt / test script set, prepare script that installs lefthook, trustedDependencies.dprint.json — plugin set, includes/excludes, formatting options..oxlintrc.json — plugin/category/rule set.lefthook.yml — pre-commit shape.tsconfig.base.json + tsconfig.json — strictness flags, the language-service plugin, include/exclude patterns..envrc, .env — direnv setup.Copy the shape of these files. Adapt the names, dependency versions (use latest), and workspace contents to the new project. Don't blindly copy mydb-specific things (e.g. drizzle config, alchemy scripts, @mydb/* paths) unless the new project actually needs them.
The "always yes" list and the mydb reference cover the spine. Everything else — what apps/packages to scaffold, which Effect platform packages to pull in, whether to wire up alchemy or drizzle or vitest, how to structure CI — depends on what the user actually wants the monorepo for. Ask if it's unclear, otherwise pick sensible defaults based on the stated purpose.