# Build Project Maps for Selected Folders

Large repositories are hard to understand when folder roles are undocumented. This skill creates or updates PROJECT_MAP.md files for selected folders with concise structure and context.

## Install

```bash
npx skillstore add yunshu0909/project-map-builder
```

## Metadata

- Status: approved
- Slug: yunshu0909-project-map-builder
- Skillstore revision: r1
- Version status: missing
- Tree hash: fbc72c0c9071a1452378a1faeb7a572b77c4ed1d069859ff6bee7d7915348683
- Author: yunshu0909
- GitHub username: yunshu0909
- License: MIT
- Repository: https://github.com/yunshu0909/yunshu\_skillshub/tree/master/project-map-builder
- Ref: 64ca8af0f54a325752f08bd54e52151061ea659a
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/yunshu0909-project-map-builder
- Manifest: https://skillstore.pages.dev/api/skills/yunshu0909-project-map-builder/manifest

## Capabilities

- Asks the user to define scan scope before reading files.
- Builds a PROJECT\_MAP.md structure for one selected directory.
- Supports merged or separate maps for multiple directories.
- Updates existing PROJECT\_MAP.md files with incremental changes.
- Lists files quickly and reads only key files for context.
- Marks assumptions and unconfirmed behavior in the document.

## Use Cases

- Document a Feature Area: Create a map for one feature folder before making changes.
- Onboard to a Repository: Produce a concise folder guide for teammates joining a project.
- Refresh Existing Project Notes: Update PROJECT\_MAP.md after files are added, removed, or reorganized.

## Prompt Templates

### Map One Folder

```
Use project-map-builder to create PROJECT_MAP.md for [folder]. Ask me before scanning anything outside that folder.
```

### Update Existing Map

```
Update the existing PROJECT_MAP.md in [folder]. Only scan [folder] and add a dated update section.
```

### Compare Multiple Folders

```
Build project maps for [folder A] and [folder B]. Ask whether I want one merged document or separate documents.
```

### Map Architecture Context

```
Create a PROJECT_MAP.md for [folder] that emphasizes entry points, configuration, storage, tests, module relationships, risks, and unknowns.
```

## Limitations

- It requires the user to provide folder scope before work begins.
- It does not perform full repository scans by default.
- It may miss details outside the selected folders.
- It depends on available file listing tools in the workspace.

## Best Practices

- Start with one folder or a small set of related folders.
- Confirm whether multiple folders should share one map or separate maps.
- Review assumptions and unknowns before treating the map as complete.

## Anti Patterns

- Do not request a full repository scan when a focused folder map is enough.
- Do not use the map as a substitute for reading critical source files.
- Do not overwrite existing PROJECT\_MAP.md content without checking changes.

## Security Audit

- Audited at: 2026-07-08T11:00:43.608\+00:00
- Summary: Both static findings are false positives after reviewing SKILL.md. The command finding is Markdown text recommending normal file listing tools, and the entropy heuristic reflects readable Chinese Markdown. No prompt injection, exfiltration intent, or hidden execution logic was found.

## Stats

- Views: 131
- Downloads: 28
- Favorites: 1
- Popularity score: 0