Map repository module boundaries | DevPrompt Lab

A repository mapping prompt that bases architecture claims on actual files and imports.

Reusable content

Inspect the supplied tree, manifests, entry points, and imports. Produce a concise map of modules, what each owns, public entry points, allowed dependency direction, runtime boundaries, and generated or vendor areas. Cite paths for each claim. Identify cycles, duplicate ownership, and unclear boundaries only when visible in the evidence. Do not infer behavior from directory names alone. End with a short list of high-value questions for a maintainer.

Directory tree: {{DIRECTORY_TREE}}

Entry points: {{ENTRY_POINTS}}

Import rules: {{IMPORT_RULES}}

How to use it

Run an inventory and include representative imports. Exclude dependency and generated directories unless they are relevant.

Example

Frontend imports the API client through `src/utils/api.ts`; components should not construct alternate production origins.