Produce the app store and website screenshots for the attendance app — seed a dev instance with realistic choir demo data (English or German via --lang de), shoot the dashboard widget, appointment list, group statistics, live check-in, activity history and scheduling states at a consistent size, regenerate the thumbnails and wire them into appinfo/info.xml and the website repo. Use when the user wants new or updated screenshots, mentions "screenshots erzeugen", "neue screenshots", "screenshots aktualisieren", "deutsche screenshots", "app store screenshots", "Bilder für den App Store", "Website-Screenshots", or after UI changes that make the shipped screenshots look outdated.
Handle Transifex translator feedback for the attendance app — fetch open questions/issues/suggestions from translators, triage them, fix source strings where translators are right, and post replies via the API. Use this whenever the user mentions Transifex, translator comments/questions/issues, string feedback, or wants to answer or resolve translation discussions — including phrasings like "check what translators asked", "answer the open translation questions", or "are there new comments on Transifex".
Keep the German l10n files in step with the code — fill every source string that has no German yet and drop entries whose source string is gone, writing into l10n/de.json, de.js, de_DE.json and de_DE.js so the app is fully German without waiting for the next Transifex sync. Use when the user wants to auto-translate missing strings to German, remove stale/orphaned translation keys, mentions "l10n-autotranslate", "alles auf Deutsch übersetzen", "fehlende Übersetzungen ergänzen", "stale strings entfernen", "translate missing strings", or after adding/renaming/removing t()/n() strings that should show up in German immediately.