map-project-monorepo

Map Cargo workspace crates and generate per-member CLAUDE.md documentation.

13|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/ulpi-io/browse --skill map-project-monorepo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: map-project-monorepo
Source: https://github.com/ulpi-io/browse/tree/main/.agents/skills/map-project-monorepo
Command: npx skills add https://github.com/ulpi-io/browse --skill map-project-monorepo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Generate self-contained CLAUDE.md documentation for every member crate/package in a workspace, ensuring Claude has per-crate context without cross-crate leakage.

Core Features & Use Cases

  • Discover all workspace members (crates/packages) and determine their actual exported surfaces, wiring points, and dependencies.
  • Generate per-member CLAUDE.md files that expose public APIs, key files, runtime entry points, and registration points.
  • Produce a simplified root CLAUDE.md that references per-crate docs and preserves architecture decisions.

Quick Start

Run the map-project-monorepo skill to generate CLAUDE.md documentation for all workspace members.

Frequently Asked Questions about map-project-monorepo

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

FAQPage Schema
How do I generate per-crate CLAUDE.md documentation for a Cargo workspace?

A root CLAUDE.md references all generated per-crate CLAUDE.md files and preserves architectural decisions. This structure provides a simplified overview of the workspace while ensuring Claude reads specific crate context without cross-crate leakage.

How does the monorepo documentation discovery process identify crate boundaries?

The monorepo documentation discovery process enforces a Phase 1 discovery gate to identify each workspace member's actual exported surfaces, wiring points, and dependencies. This ensures accurate crate boundary detection before generating any CLAUDE.md files.

Can I use this to document multi-crate Rust projects with complex dependency trees?

Yes, you can use this to document multi-crate Rust projects with complex dependency trees. The skill specifically targets Cargo workspaces, identifying each crate's public surface and dependency wiring to generate self-contained per-crate CLAUDE.md context.

What is the best way to provide Claude with isolated context for individual workspace crates?

The best way to provide Claude with isolated context for individual workspace crates is by generating self-contained CLAUDE.md files for each member. This prevents cross-crate context leakage by exposing only the specific crate's public APIs and key files.