link-workspace-packages

Link workspace packages to resolve monorepo dependency and module resolution issues.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/devswapnil1995/society-management-platform --skill link-workspace-packages-devswapnil1995
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: link-workspace-packages
Source: https://github.com/devswapnil1995/society-management-platform/tree/main/frontend/society-frontend/.cursor/skills/link-workspace-packages
Command: npx skills add https://github.com/devswapnil1995/society-management-platform --skill link-workspace-packages-devswapnil1995

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill resolves broken workspace package connections in monorepos by correctly linking dependencies instead of relying on fragile manual configuration changes.

Core Features & Use Cases

  • Workspace Dependency Linking: Adds package relationships using the correct workspace syntax for npm, yarn, pnpm, and bun.
  • Package Resolution Debugging: Helps fix missing module errors, failed imports, and TypeScript resolution problems caused by unlinked workspace packages.
  • Use Case: When a frontend application cannot import a shared package from a sibling workspace, use this Skill to identify the package manager and create the proper dependency link.

Quick Start

Ask the skill to link the workspace package dependency causing the unresolved import error in the monorepo.

Frequently Asked Questions about link-workspace-packages

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix unresolved imports in a monorepo?

To fix unresolved imports in a monorepo, you need to link workspace packages using the correct dependency syntax for your package manager. This creates valid local package connections resolving missing module errors.

How do I link workspace packages in npm, yarn, pnpm, and bun?

You link workspace packages in npm, yarn, pnpm, and bun by applying workspace-aware dependency declarations. This uses package manager commands to establish valid local connections between sibling packages and shared libraries.

Why does my frontend application fail to import a shared package from a sibling workspace?

Your frontend application fails to import a shared package from a sibling workspace because workspace packages are unlinked. Identifying the package manager and creating the proper dependency link resolves the broken connection.

Can I use this to fix TypeScript resolution problems caused by unlinked workspace packages?

Yes, you can fix TypeScript resolution problems caused by unlinked workspace packages. The process identifies your package manager and applies workspace-aware dependency declarations to create the proper local package connections.

What's the best way to resolve monorepo dependency and module resolution problems?

The best way to resolve monorepo dependency and module resolution problems is linking workspace packages instead of relying on fragile manual configuration changes. This correctly establishes valid local connections between sibling packages.