monorepo
Skill119 starsChanged 6 months agoMITView on GitHub
MUST use for ANY query mentioning packages, monorepo, workspace, catalog, turbo, turborepo, or pnpm in a multi-package context. MUST use when sharing config (ESLint, tsconfig, prettier) across packages, fixing build order between packages, adding new packages, scoping CI installs/caching to changed packages, or debugging pnpm catalog version resolution. This skill OWNS all cross-package coordination problems — even when they look like build, CI, config, or dependency issues. If two or more packages interact in the query, this skill applies. Takes priority over other skills when the problem spans package boundaries.
- Reads credentials
9 other projects use a version of this.
Adopted by
Most recently taken up by
- TheBeardedBearSAS/claude-crafttheir own version, first seen Nov 11, 2026
- Firzus/agent-skillstheir own version, first seen Oct 23, 2026
- mhosseinab/skillstheir own version, first seen Oct 9, 2026
- Mindrally/skillstheir own version, first seen Oct 8, 2026
- epicenter-md/epicentertheir own version, first seen Oct 8, 2026
- EpicenterHQ/epicentertheir own version, first seen Oct 8, 2026
Used with
Projects with it also use tauri, documentation and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
klauswgSkilltauri
Cross-platform app toolkit with Rust backend and WebView frontend. Use when building or maintaining Tauri apps, configuring IPC/security, or developing plugins.
Also in 3 projects that use this
AnthropicSkilldocumentation
Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.
Also in 3 projects that use this
NVIDIASkilltesting
Run Python and Rust tests for physicsnemo-curator using uv + pytest with coverage reporting via pytest-cov, and cargo-nextest for Rust tests. Includes benchmark workflows with pytest-benchmark and criterion.
Also in 3 projects that use this
GoogleSkillprototype
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
Also in 3 projects that use this
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- epicenter-md/epicenter★ 4.8ksame name
- EpicenterHQ/epicenter★ 4.8ksame name
- Mindrally/skills★ 275same name
- TheBeardedBearSAS/claude-craft★ 108same name
- wpank/ai★ 11same name
- YepAPI/skills★ 8same name
- Firzus/agent-skills★ 4same name
- mhosseinab/skills★ 1same name
- poorvith-mp/skills-developer★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository22 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- agent-browserSkill
- askSkill
- cookSkill
- create-docSkill
- diagnoseSkill
- discussSkill
- docs-seekerSkill
- fixSkill
- frontend-designSkill
- give-planSkill
- media-processorSkill
- optimus-primeSkill
- prime-syncSkill
- review-codeSkill
- self-evolveSkill
- skill-creatorSkill
- testSkill
- backend-fastapi-pythonSkill
- dockerSkill
- frontend-developmentSkill
- humanizerSkill
The file
Files
Monorepo
Project-specific patterns for pnpm workspaces + Turborepo.
Architecture Decisions
Workspace Organization
- Split apps from packages —
apps/for deployables,packages/for shared libraries. - Namespace packages — Prefix with
@org/to avoid npm conflicts. - Single lockfile —
pnpm-lock.yamlat root only. Never commit multiple lockfiles. - No cross-package file access — Never use
../to reach into other packages; import via dependencies.
Dependency Management
- Use
workspace:*protocol — Always for internal package dependencies. - Hoist common devDependencies — Shared tooling (TypeScript, ESLint) in root.
- Peer dependencies for frameworks — React, Vue, etc. as peers to avoid version conflicts.
- Consider Catalogs (pnpm 9.5+) — Centralize versions in
pnpm-workspace.yamlfor large repos.
Turborepo Tasks
- Use
^for build dependencies —"dependsOn": ["^build"]for topological order. - Always define
outputs— Without outputs, nothing gets cached. - Mark dev servers as persistent —
"persistent": true, "cache": false. - Be explicit about environment — List all build-affecting vars in
envorglobalEnv.
Gotchas
- Missing
outputsin turbo.json silently disables caching for that task. The task runs every time and you won't get an error — just slow builds. Always verify outputs are configured. pnpm installdoes NOT respect--filterfor installation — it always installs the entire workspace. Filtering only works forpnpm runandpnpm exec.workspace:*resolves to the CURRENT version of the local package, not "latest from npm". If the package has"version": "0.0.0", published packages will have"dependency": "0.0.0"— set meaningful versions before publishing.- Turborepo's
envfield in turbo.json uses GLOB patterns, not exact matches."env": ["API_*"]capturesAPI_KEY,API_URL, etc. Forgetting this causes over-invalidation. turbo run build --filter=app-abuilds app-a AND all its workspace dependencies. If a dependency fails, app-a won't build. Check transitive deps.- Adding a package to
packages/requires runningpnpm installbefore the workspace recognizes it. The new package also needs a validpackage.jsonwithnamematching the workspace pattern. - TypeScript project references (
referencesin tsconfig.json) must match the workspace dependency graph. Mismatches cause type errors that only appear duringtsc --build, not in IDE. turbo.json'sglobalDependenciesinvalidates ALL tasks when listed files change. Don't put frequently-changed files here — use task-levelinputsinstead.- Shared Tailwind configs need
@sourcedirectives pointing to consuming packages' source directories, otherwise classes used in shared packages are purged. pnpm deploy(for production) copies a single package and its dependencies to a target directory. It does NOT run build scripts — build first, then deploy.- Remote cache (Vercel or self-hosted) requires
outputsto be correct. If outputs are wrong, cached artifacts will be incomplete and downstream tasks break silently. persistent: truetasks preventturbo runfrom exiting. Don't include persistent tasks in CI pipelines unless they have a timeout.
References
| When you need... | Read |
| workspace.yaml, workspace: protocol, filtering | pnpm-workspace.md |
| turbo.json schema, tasks, dependsOn | turborepo.md |
| Cache outputs/inputs, remote cache setup | caching.md |
| Directory layout, package naming, tsconfig | structure.md |
| Tailwind v4 shared theme package | tailwind-v4.md |
External Resources
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
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.

