Run any Skill in Manus with one click

populate-project-map

Stars439

Forks322

UpdatedMay 5, 2026 at 22:59

Creates or updates a human-readable project map for the cuid workspace. Use when onboarding, when workspace layout changes, or when agents need up-to-date layout info.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

ROCm

ROCm/rocm-systems

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	populate-project-map
description	Creates or updates a human-readable project map for the cuid workspace. Use when onboarding, when workspace layout changes, or when agents need up-to-date layout info.

Populate Project Map

Creates or updates .claude/project-map.md — a single source of truth for the cuid project layout. All review agents and skills reference this instead of embedding layout info.

Steps

If .claude/project-map.md exists, update it. Otherwise, create it.
Explore the actual workspace to discover paths. Double-check that every listed path exists.
Identify:
- Source directories by language (C/C++, Python, Go, Rust, CMake)
- Build artifacts and packaging scripts
- Test directories
- Documentation directories
- Configuration files (pre-commit, formatters, build configs)
- Generated files and their generators
- Critical high-churn files
Write the map in the format below.
Open for user inspection.

Format

# Cuid Project Map

> Auto-generated by populate-project-map skill. Single source of truth for project layout.
> Referenced by review agents — update when directory structure changes.

## Source Directories

| Language | Directory | Purpose |
|----------|-----------|---------|
| C/C++ | `lib/src/` | Core library implementation |
| C/C++ headers | `lib/include/` | Public API headers |

## Build & Packaging

| Path | Purpose |
|------|---------|
| `CMakeLists.txt` | Root build configuration |

## Tests

| Path | Purpose |
|------|---------|
| `tests/functional/` | more involved tests |
| `tests/unit/` | unit tests |

## Documentation

| Path | Purpose |
|------|---------|
| `docs/` | Sphinx documentation source |
| `docs/doxygen/` | Doxygen config for C API |
| `docs/how-to/` | How-to guides |

## Critical Files (high churn — review carefully)

| File | Risk |
|------|------|
| `cli/amdcuid_tool.cc` | CLI behavior regressions, output format |
| `daemon/amdcuid_daemon.cc` | Daemon stability, API surface |
| `lib/src/cuid.cc` | Core C library — correctness |
| `lib/include/amd_cuid.h` | Public API — cascades everywhere |
| `CMakeLists.txt` | Build system, packaging, install targets |

## API Cascade Path

Changes to the public C API must propagate through all layers:

`lib/include/amd_cuid.h` → `lib/src/cuid.cc` → `cli/amdcuid_tool.cc` → `daemon/amdcuid_daemon.cc` → `docs/`


## When to Regenerate

- New top-level directories added
- Major restructuring (files moved between directories)
- New language bindings added
- Build system changes (new packaging targets, new CMakeLists.txt files)

More from this repository

same repository

amdsmi-changelog-automation

ROCm/rocm-systems

Check and generate changelog entries for amd-smi. Use when: reviewing PRs for changelog updates, generating release notes, checking CHANGELOG.md compliance.

2026-07-21439

amdsmi-commit-and-pr-conventions

ROCm/rocm-systems

Use when writing or restructuring git commits or opening/updating a pull request for amd-smi — composing commit titles, commit message bodies, PR titles, or PR descriptions. Defines the Conventional Commits `type(amdsmi):` title convention enforced by the Systems PR Bot, the rocm-systems PR template sections, the unit-test and JIRA/ISSUE-reference gates, brevity caps, and the rule that JIRA tickets appear only in the PR JIRA ID section, never in code comments or commit bodies.

2026-07-09439

amdsmi-restructure-commits

ROCm/rocm-systems

Use when finishing an amd-smi development branch — consolidating commits into logical groups with clean messages AND deciding how to integrate the work (merge to develop, push and open PR, keep as-is, or discard). Covers commit restructuring plus the merge/PR/cleanup workflow.

2026-07-09439

writing-plans

ROCm/rocm-systems

Use when an approved spec exists and you need a bite-sized, file-level implementation plan before any code is written. Produces a plan ready for executing-plans or subagent dispatch.

2026-07-09439

rdc-build-install

ROCm/rocm-systems

Build and install RDC from source. Use when: building locally, installing before tests, pre-review build verification, build + install + verify. Requires GRPC_ROOT to be set.

2026-06-24439

feature-unit-testing

ROCm/rocm-systems

Use when writing, planning, or improving unit tests for low-level transport or systems code — especially when reasoning about branch coverage, test gaps, identifying which uncovered paths are worth pursuing, or deciding when a feature's test suite is ready to merge.

2026-06-19439

Populate Project Map

Creates or updates .claude/project-map.md — a single source of truth for the cuid project layout. All review agents and skills reference this instead of embedding layout info.

Steps

If .claude/project-map.md exists, update it. Otherwise, create it.

Explore the actual workspace to discover paths. Double-check that every listed path exists.

Identify:

Source directories by language (C/C++, Python, Go, Rust, CMake)
Build artifacts and packaging scripts
Test directories
Documentation directories
Configuration files (pre-commit, formatters, build configs)
Generated files and their generators
Critical high-churn files

Write the map in the format below.

Open for user inspection.

Format

# Cuid Project Map > Auto-generated by populate-project-map skill. Single source of truth for project layout. > Referenced by review agents — update when directory structure changes. ## Source Directories | Language | Directory | Purpose | |----------|-----------|---------| | C/C++ | `lib/src/` | Core library implementation | | C/C++ headers | `lib/include/` | Public API headers | ## Build & Packaging | Path | Purpose | |------|---------| | `CMakeLists.txt` | Root build configuration | ## Tests | Path | Purpose | |------|---------| | `tests/functional/` | more involved tests | | `tests/unit/` | unit tests | ## Documentation | Path | Purpose | |------|---------| | `docs/` | Sphinx documentation source | | `docs/doxygen/` | Doxygen config for C API | | `docs/how-to/` | How-to guides | ## Critical Files (high churn — review carefully) | File | Risk | |------|------| | `cli/amdcuid_tool.cc` | CLI behavior regressions, output format | | `daemon/amdcuid_daemon.cc` | Daemon stability, API surface | | `lib/src/cuid.cc` | Core C library — correctness | | `lib/include/amd_cuid.h` | Public API — cascades everywhere | | `CMakeLists.txt` | Build system, packaging, install targets | ## API Cascade Path Changes to the public C API must propagate through all layers: `lib/include/amd_cuid.h` → `lib/src/cuid.cc` → `cli/amdcuid_tool.cc` → `daemon/amdcuid_daemon.cc` → `docs/` ## When to Regenerate - New top-level directories added - Major restructuring (files moved between directories) - New language bindings added - Build system changes (new packaging targets, new CMakeLists.txt files)