folder-colorslisted
Install: claude install-skill Ramonvdo/folder-colors
# folder-colors
Everything lives at the repo root (`<root>`, found as `..\..\shared\tools.md` describes):
`Set-FolderColor.ps1` (the engine), `categories.json` (the mapping index -> colour ->
category -> group; the only file a user edits), `Pick-FolderColor.ps1` (the palette the
right-click entry opens), `install.ps1` / `uninstall.ps1` (the right-click entry) and
`assets\Windows_11_coloured_icons.icl`. Run scripts with Windows PowerShell 5.1:
`powershell -NoProfile -ExecutionPolicy Bypass -File "<root>\Set-FolderColor.ps1" ...`
## Engine
| Task | Command |
|---|---|
| List categories | `Set-FolderColor.ps1 -List` |
| Read a folder's colour | `Set-FolderColor.ps1 -Path <dir> -Get \| Format-List` |
| Colour a folder | `Set-FolderColor.ps1 -Path <dir> -Category "Clients"` (or `-Color "Light Blue"`, or `-Index 12`) |
| Back to default | `Set-FolderColor.ps1 -Path <dir> -Reset` |
Names match loosely (`light-blue`, `LightBlue` and `Light Blue` are the same). The colour
is stored in the folder's hidden `desktop.ini` as an **index**, so a category can be
renamed or regrouped later without touching any folder. Exit code 0 means applied; a
non-zero exit carries the reason on stderr.
A folder that already has a `desktop.ini` (folder-type template, folder picture, an icon
set through Properties) keeps it: the engine replaces only the icon lines, remembers the
previous icon and the folder's attributes, and `-Reset` puts both back. `-Get` reports an
empty index for a folder whose `des