template-author

To convert an App Store listing into a reusable template, the Skill fetches listing data via URLs or IDs, downloads reference screenshots across macOS, iPhone, and iPad, and generates a bundled template package wired into the TemplateLibrary system.

Bundled file-based templates are static asset packages, while code-backed templates are generated programmatically. The Skill manages both backing forms with migration paths and sidecars to preserve catalog integrity across app and website repositories.

Yes, you need curl and jq installed as dependencies. The Skill relies on these command-line tools to execute scripts that fetch App Store listings, download reference screenshots, and parse the resulting JSON metadata.

Templates sync by applying changes to the ScreenShotComposer/Templates path in the app repo and the skills folder on the website. A template.json sidecar ensures metadata remains consistent across both locations during updates.

Yes, you can generate or select suitable background imagery such as landscape, arches, mesh, grain, or photography. The Skill wires the selected background image directly into the template's plate fill configuration for rendering.

Template previews fail to update when the refresh script is not run. You must execute bin/refresh-template-previews to re-render previews after integrating builders and copy(for:scene:) to ensure the template library displays current outputs.