pop-project-reference

Loads sibling monorepo project context including dependencies, READMEs, and metadata from workspace files.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jrc1883/popkit-ai --skill pop-project-reference
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pop-project-reference
Source: https://github.com/jrc1883/popkit-ai/tree/main/packages/popkit-core/skills/pop-project-reference
Command: npx skills add https://github.com/jrc1883/popkit-ai --skill pop-project-reference

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Load cross-project context in monorepos to access information about sibling workspace projects without manual file traversal, enabling faster cross-project development and integration.

Core Features & Use Cases

  • List available workspace projects with name, type, and path.
  • Load project context for a named project, including CLAUDE.md, package.json dependencies, and README.
  • Gracefully skip missing files and continue with available data.
  • Support for pnpm, npm/yarn, Lerna workspaces, and PopKit-specific workspace markers.
  • Triggered by user commands like /popkit:project reference to explore or load context.

Quick Start

Invoke /popkit:project reference to list projects or load a specific project's context.

Frequently Asked Questions about pop-project-reference

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

FAQPage Schema
How do I load cross-project context in a monorepo to understand sibling workspace dependencies?

To load cross-project context in a monorepo, you can use a workspace context loading tool that reads package.json, CLAUDE.md, and README files from sibling projects to extract dependency and architecture information without manual file traversal.

What is the best way to list available workspace projects in a pnpm or Lerna monorepo?

Listing available workspace projects in pnpm or Lerna monorepos involves detecting workspace markers to return each project's name, type, and path. This approach supports npm/yarn workspaces and PopKit-specific configurations for accurate project discovery.

Does monorepo context loading work if CLAUDE.md or README files are missing from a project?

Monorepo context loading gracefully skips missing files like CLAUDE.md or README and continues processing with available data. This ensures you still retrieve package.json dependencies and partial architecture context even when sibling projects lack complete documentation.

Can I read package.json dependencies from a specific sibling project without navigating the entire monorepo workspace?

Yes, you can load context for a specific named project within a monorepo workspace to directly retrieve its package.json dependencies, README, and CLAUDE.md. This bypasses manual directory traversal and targets the exact sibling project context you need.

When do I need cross-project context loading for monorepo integration discovery?

You need cross-project context loading for monorepo integration discovery when you require visibility into sibling project APIs, dependencies, or architecture. It is essential for understanding workspace boundaries and integrating code across multiple projects without manually opening each file.