Monorepo Project Rules

monorepoarchitecture

Conventions and best practices for managing monorepo projects, covering workspace structure, dependency management, and cross-package coordination.

Целевые файлы

Файл	Формат
.cursorrules	plaintext
CLAUDE.md	markdown
.github/copilot-instructions.md	markdown

Содержимое

Monorepo tool: ${tool}. Use workspace protocols for internal dependencies — never publish internal packages to a registry for local use. Structure: apps/ for deployable applications, packages/ for shared libraries, tooling/ or config/ for shared build and lint configs. Each package must have its own package.json with explicit dependencies. Never rely on hoisted dependencies — imports must be declared. Define a clear public API for each package via exports field in package.json or an index.ts barrel file. Keep internal modules private. Use shared configurations for TypeScript, ESLint, and Prettier at the root. Packages extend the base config with local overrides only when necessary. Run tasks incrementally: only build/test/lint packages affected by changes. Use ${tool} caching and dependency graph awareness. Version packages independently unless they share a release cycle. Document inter-package breaking changes in a changelog. CI must validate the entire dependency graph: build packages in topological order, then run tests. Never skip downstream consumers.

Переменные

ID	Метка	По умолчанию	Варианты
tool	Monorepo Tool	pnpm	pnpmturboreponx

CLI

npx mindaxis apply monorepo-rules --target cursor --scope project

Используется в паках

Cloud Native

Cloud-native development toolkit

Открыть пак →

← Правила