dev-capsem

Map Capsem's codebase structure, crates, and skill locations.

68|10|Updated Sep 26, 2025
One-click install
npx skills add https://github.com/google/capsem --skill dev-capsem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-capsem
Source: https://github.com/google/capsem/tree/main/skills/dev-capsem
Command: npx skills add https://github.com/google/capsem --skill dev-capsem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capsem project overview and navigation to help developers quickly understand what Capsem is, how the codebase is organized, which crate does what, and which skill to consult for a specific area. This is the map of the project -- start here when orienting on any task.

Core Features & Use Cases

  • Provides a map of Capsem's crates, modules, and skill locations to accelerate onboarding.
  • Assists in architecture reviews and task scoping by clarifying component responsibilities.
  • Serves as an orienting guide to locate the right skill or crate for a given task.

Quick Start

List the Capsem crates and point me to the skill that handles development workflows.

Frequently Asked Questions about dev-capsem

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

FAQPage Schema
How do I navigate a Rust codebase with multiple crates during onboarding?

To navigate a Rust codebase during onboarding, map the project structure to identify which crate handles what functionality. This clarifies component responsibilities and points you to the correct skill or crate for a specific development task.

What is the best way to orient myself when starting development on a new codebase?

The best way to orient yourself on a new codebase is to consult a project overview map. It helps you quickly understand the organization, locate the right skill or crate, and scope your task without reading the entire codebase.

How do I scope tasks and review architecture across unfamiliar crates?

To scope tasks and review architecture across unfamiliar crates, use a codebase map to clarify component responsibilities. This guides you to the correct skill or crate for the specific development area you are reviewing.

Do I need a SKILL.md file with YAML frontmatter to map project structure?

Yes, mapping project structure requires a SKILL.md file with YAML frontmatter containing a name and description. It may also reference optional scripts, references, or assets directories to extend context and locate skills accurately.

What are the limitations of using a project map for codebase navigation?

A project map for codebase navigation is limited to orienting you on structure and pointing to the correct skill or crate. It does not execute code or replace detailed documentation found within the individual crates or skills themselves.