Bring order to a messy project folder.

Get a proposed structure before anything moves.

Why try this?

An agent can inventory a folder and propose a consistent organization.

What to bring

A backed-up copy of one folder with only the files needed for the task.

Your starting request

Inspect this project folder read-only. List the file types and propose a clearer folder structure. Produce a table of current path, proposed path, and reason. Flag ambiguous or duplicate-looking files. Do not move, rename, overwrite, or delete anything yet.

Illustrative result

This is an authored teaching example, not a live model response.

An inventory and proposed move table, with ambiguous files left for a human decision.

Then make it fit

Apply only these approved moves: [list]. Never overwrite a destination. Keep a log so I can reverse the changes.

Before you use it

Back up first. Inspect proposed paths, confirm ambiguous files, and verify links and applications still work after approved moves.

What you are learning

For actions that change your files, review the exact proposed changes first.

All uses | Choose a tool

Related Power of AI pages

Keep reading with Start here, everyday uses, the tool guide, the writing workshop, and sources and standards.