What problem does it solve? Receiving a folder of sound effects from a sound designer and getting it correctly into a Unity project is error-prone: files must land in the right Assets folders, import settings must match 2D/3D and loop requirements, and someone must track which promised sounds are still missing. This Skill automates that intake process. ## Core Features & Use Cases - Manifest-driven intake: Reads the delivery's sounds.json passport and copies files to their declared unity_target_folder locations, updating per-folder sfx manifests without touching existing slots. - Dry-run verification: Runs a preview pass showing how many slots and files will go to each folder before committing any changes. - Library build and gap report: Triggers Unity sound library builds and reports three lists — what arrived and was placed, what is still missing per the delivery's "not done yet" section, and what arrived but is not yet wired to game events. - Use Case: A game designer drops a new Komnata_zvuk delivery folder into the repo. Run the intake to place all clips, rebuild the audio libraries in Unity, and get a ready-made list of sounds to request from the supplier. ## Quick Start Accept the newest sound delivery folder into the project and tell me which promised sounds are still missing.