Link workspace packages in monorepos across npm, yarn, pnpm, and bun.
Works with
Detects package manager via packageManager field or lockfile presence, then uses the appropriate workspace linking command for each manager
pnpm and yarn use workspace: protocol; npm auto-symlinks workspace packages; bun supports workspace: protocol
Resolves \"cannot find module\" and import resolution errors by adding dependencies between sibling packages with proper symlink creation
Each manager has different
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionlink-workspace-packagesExecute the skills CLI command in your project's root directory to begin installation:
Fetches link-workspace-packages from nrwl/nx-ai-agents-config and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate link-workspace-packages. Access via /link-workspace-packages in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
12
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
12
stars
Add dependencies between packages in a monorepo. All package managers support workspaces but with different syntax.
Check whether there's a packageManager field in the root-level package.json.
Alternatively check lockfile in repo root:
pnpm-lock.yaml → pnpmyarn.lock → yarnbun.lock / bun.lockb → bunpackage-lock.json → npmnode_modules/Uses workspace: protocol - symlinks only created when explicitly declared.
# From consumer directory
pnpm add @org/ui --workspace
# Or with --filter from anywhere
pnpm add @org/ui --filter @org/app --workspace
Result in package.json:
{ "dependencies": { "@org/ui": "workspace:*" } }
Also uses workspace: protocol.
yarn workspace @org/app add @org/ui
Result in package.json:
{ "dependencies": { "@org/ui": "workspace:^" } }
No workspace: protocol. npm auto-symlinks workspace packages.
npm install @org/ui --workspace @org/app
Result in package.json:
{ "dependencies": { "@org/ui": "*" } }
npm resolves to local workspace automatically during install.
Supports workspace: protocol (pnpm-compatible).
cd packages/app && bun add @org/ui
Result in package.json:
{ "dependencies": { "@org/ui": "workspace:*" } }
Example 1: pnpm - link ui lib to app
pnpm add @org/ui --filter @org/app --workspace
Example 2: npm - link multiple packages
npm install @org/data-access @org/ui --workspace @org/dashboard
Example 3: Debug "Cannot find module"
package.jsonpnpm install, npm install, etc.)<consumer>/node_modules/@org/<package>node_modulesnode_modules)package.json should have "private": true to prevent accidental publishMake data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
link-workspace-packages is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: link-workspace-packages is focused, and the summary matches what you get after install.
Useful defaults in link-workspace-packages — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for link-workspace-packages matched our evaluation — installs cleanly and behaves as described in the markdown.
link-workspace-packages fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for link-workspace-packages matched our evaluation — installs cleanly and behaves as described in the markdown.
link-workspace-packages has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in link-workspace-packages — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: link-workspace-packages is focused, and the summary matches what you get after install.
Keeps context tight: link-workspace-packages is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 25