What problem does it solve? The pictures in the manual drift out of date whenever the application window changes, and retaking them by hand is slow, inconsistent, and easy to forget before a release. This Skill defines the complete screenshot pass: when to run it, what it needs, how to shoot, and how to verify the results. ## Core Features & Use Cases - Repeatable automated screenshots: Uses docs/notes/shoot_screenshots.py to load the program as a module, open a project built from test fixtures, and save window.grab() output in English and German (docs/images/NAME.png and NAME.de.png). - Release-gated workflow: Pictures are taken once per version, not after every change; outdated pictures are noted in between and refreshed in one pass before release. - Quality checklist: Eight verification questions catch cut-off labels, wrong-language catalogue entries, unparsable assembled sentences, leaked keys or real names, and unexpected changes. - Use Case: Before shipping a release, run the caption test with VPM_LAYOUT_PLATFORM=cocoa, build the fixtures, shoot the main, split, and channels sets in both languages, compare checksums, copy only changed pictures, and record what invalidated each one. ## Quick Start Run the pre-release screenshot pass for the manual: build the test fixtures, shoot all picture sets in English and German, compare checksums, and copy only the images that actually changed into docs/images.