What problem does it solve? It prevents architectural mistakes when working with the GO CMS storage layer, such as hardcoding disk names, persisting mutable labels instead of stable disk codes, or confusing drivers, visibility, and module aliases. ## Core Features & Use Cases - Filesystem mental model: Enforces separation between drivers (local, S3), physical disks with stable codes and human labels, visibility policies, and module-local aliases. - Project disk declarations: Guides declaring disks as Go factories under backend/internal/filesystems with typed environment configuration instead of JSON env lists. - Admin and module integration: Covers the FileExplorer disk catalog flow, file picker restrictions by disk code, and module alias bindings resolved through ModuleContext. - Use Case: When adding a new S3-backed media disk to the CMS, follow the skill to declare the disk factory, bind module aliases, expose it through the /api/files/disks catalog, and add the required tests. ## Quick Start Ask the assistant to add a new private S3 disk named documents to the GO CMS project and wire it into the admin FileExplorer.
