tidylisted

# Project Tidy — Organize, Don't Break Make a messy project clean and easy to manage **without breaking it**. Moving or deleting files can silently break a build, a page, or an import. So the rule is: **understand first, plan, get approval, then execute — and update every reference.** This skill can move and delete files. Treat that power carefully. When unsure whether something is safe to move or delete, **leave it and ask.** ## Step 1 — Understand the project Before touching anything: - Map the current tree (`git ls-files`, directory listing). Identify the project type (static site, Node app, Python package, etc.) and its **entry points** (`index.html`, `main.py`, `src/index.js`, etc.). - Read build/config files (`package.json`, bundler config, framework config) — they often hardcode paths and dictate where files must live. - Understand **how files reference each other**: HTML `src`/`href`, CSS `url()` and `@import`, JS/TS `import`/`require`, asset paths in code, config path strings. - Check what's tracked vs untracked (`git status`) so you don't reorganize generated output (`dist/`, `node_modules/`) — those belong in `.gitignore`, not in folders. ## Step 2 — Plan the reorganization (don't execute yet) Propose a clean structure based on what you found. Typical pattern for a flat web project with loose files: ``` before/ after/ index.html index.html ← entry stays at root about.html about.