Project Structure Index

Incremental Update Mode

When structure_project.md already exists:

• Read the existing file before scanning anything else.
• Treat the existing file as the baseline project map.
• Run a high-level scan to detect new directories, new modules, renamed paths, removed components, new scripts, new integrations, and changed architectural boundaries.
• Update only the affected sections when possible instead of rewriting the entire file.
• Remove stale references when the underlying paths no longer exist.

What To Capture

• Project purpose and high-level architecture
• Repository layout and the role of each major directory
• Main entry points, startup flow, and execution model
• Important modules, services, libraries, or apps
• Key configuration, environment, and build files
• Testing structure and how verification is done
• External integrations, data flow, and operational concerns
• Important conventions, constraints, and open questions worth preserving for later prompts

Output Rules

• Write the output in English.
• Keep the file dense with useful facts, not long prose.
• Prefer representative paths over exhaustive file dumps.
• Use headings and short bullet lists so the file works as a reusable lookup document.
• Separate verified facts from inferred conclusions when needed.
• Keep the file current after each run so later prompts can reference it directly.

Reference

Read references/structure_project_template.md before creating or refreshing structure_project.md.