agentleFS
Sign inStart free
darellchua2darellchua2/civiltekk-opencode-claude-skills/skills/monorepo-management-skill/SKILL.md

monorepo-management-skill

Skill7 starsChanged 58 days agoApache-2.0View on GitHub

Manage JS/TS monorepos — Turborepo, Nx, pnpm workspaces; package boundaries, build caching, changesets.

The file

Create a free account to mount
Files
SKILL.md

What I do

Structure JS/TS monorepos: tool selection (Turborepo vs Nx vs pnpm-only), workspace layout, shared config packages, enforced package boundaries, build caching, changesets.

When to use me

  • Setting up or restructuring a monorepo (apps/ + packages/ split, shared configs)
  • Cross-package breakage risk, cache misses, or boundary drift (apps importing package internals)

Related: performance-optimization-skill (profiling/bundles) · civiltekk-documentation-sync-skill (doc sync across packages).

House conventions

Layout: apps/* (deployables) + packages/* (shared: ui, utils, typescript-config, eslint-config). Internal deps use "@repo/x": "workspace:*".

Shared TS config: packages/typescript-config/{base,nextjs,react-library}.json; app tsconfigs extend @repo/typescript-config/nextjs.json via "extends". Same pattern for ESLint (@repo/eslint-config).

Enforced boundaries (eslint-plugin-boundaries, boundaries/element-types): apps must import package ENTRY POINTS, never packages/*/src/** internals; packages/ui must not depend on apps/*. Message strings say why — the rule is teaching, not just blocking.

OpenCode LSP (root config): a root opencode.json with "lsp": {"typescript": {}, "eslint": {}} gives ambient cross-package diagnostics (a packages/ui change breaking apps/web surfaces live). Servers trigger per-file by extension; one root config covers the whole workspace — no per-package config. Token cost is real in large repos: monitor, scope servers, or set "lsp": false to disable. Refs: opencode.ai/docs/lsp, /docs/config.

Caching: Turborepo local cache by default; remote cache (Vercel) for CI speedup; pipeline defined in turbo.json (build depends on ^build). pnpm-workspace.yaml defines package globs; root package.json drives scripts.

Removed 2026-09: step-by-step tool-selection essays, full turbo.json/pnpm-workspace/package.json listings, ESLint flat-config walkthroughs, task-pipeline deep-dives, changesets tutorial, common-issue troubleshooting — vendor docs the model knows; what remains is the house layout, boundary rules, and the root-LSP integration pattern.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free