monorepo-navigation

Map the Leather monorepo structure and cross-package dependencies.

28|23|Updated Sep 14, 2023
One-click install
npx skills add https://github.com/leather-io/mono --skill monorepo-navigation-leather-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monorepo-navigation
Source: https://github.com/leather-io/mono/tree/main/.claude/skills/monorepo-navigation
Command: npx skills add https://github.com/leather-io/mono --skill monorepo-navigation-leather-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Leather monorepo navigation helps engineers quickly understand and locate the correct package and cross-package relationships within the monorepo, reducing time spent searching and guessing.

Core Features & Use Cases

  • Maps the monorepo structure (apps, packages, and domain peers) and clarifies how packages depend on each other.
  • Provides guidance for adding new code, finding existing implementations, and understanding import rules and architecture.
  • Use Case: when starting work on a feature across apps, use this skill to locate the relevant domain package and verify cross-package dependencies.

Quick Start

Ask the AI to map the monorepo layout for a given feature and identify the relevant package and dependencies.

Frequently Asked Questions about monorepo-navigation

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

FAQPage Schema
How do I navigate a monorepo to find the right package for a new feature?

Map the monorepo structure to identify apps, domain packages, and peers, verifying cross-package dependencies to locate the correct package for adding new code.

What is the best way to understand cross-package dependencies in a pnpm monorepo?

Understanding cross-package dependencies in a pnpm monorepo involves mapping package relationships and import rules to clarify how apps and domain peers depend on each other.

How do I locate existing implementations across packages in a turbo monorepo?

To locate existing implementations across packages in a turbo monorepo, analyze the architecture mapping to identify domain peers and find where specific code resides.

Can I use this to map import rules across apps and domain packages?

Yes, you can map import rules across apps and domain packages by analyzing the monorepo architecture to produce structured navigation guidance and cross-package relationship insights.

Does this work for adding new code across multiple apps in a monorepo?

Yes, it works for adding new code across multiple apps by providing structured navigation guidance that locates the relevant domain package and verifies cross-package dependencies before implementation.