folder-context-optimization

To identify legacy files in a codebase, you can analyze file references across code, docs, and tests to classify each item as Core, Legacy, Ad-hoc, or Optional for archival.

The best way to generate an archival plan is to sweep a target directory, trace file usage references, and produce a per-file action map with a final archive proposal for approval.

Yes, you can use this during codebase refactors or reorganizations to archive stale folder content, classify files by relevance, and keep your project directories lean and navigable.

Folder cleanup works for project directories of varying sizes, applying file reference analysis and classification to propose archival plans and update documentation like READMEs.

You update documentation when archiving unused files by generating an archival plan that includes a README update, reflecting the proposed changes to keep the codebase lean.

You should not use automated archival proposals when file references cannot be accurately traced across code, docs, and tests, as misclassification of Core or Legacy files may occur.