/store-assets internals

Rules and commands bound to /store-assets's own tooling. Cross-cutting rules (lib-orchestrator.sh, skill directory shape) live in the root CLAUDE.md.

Commands

Always render before validating. render.mjs's own pre-flight already fails before any render on a broken config, a missing source PNG, or a missing bezel/status-bar asset, but it does not check the previous run's output; validate.mjs is what checks the files actually on disk, so a stale or partial generated/ tree from an earlier round needs a fresh render first. Neither command deletes the project's own generated/ files itself: a schema change that drops or renumbers scenes (e.g. a scene-id rename) can leave stale files behind, remove them by hand before the next full render.

Rebuilding the bezel/status-bar cache on a new machine

None of ~/.cache/store-assets/bezels/, ~/.cache/store-assets/statusbar/, or the Android SDK's ~/Library/Android/sdk/skins/pixel_9_pro/{back,mask}.webp are downloaded or generated by the skill itself; see references/store-specs.md "Devices" > "Asset provenance" for the exact DMG URL, simctl status_bar override invocation, and Android SystemUI demo-mode steps. render.mjs's pre-flight fails with the missing path before any render if the cache is not there yet.

Gotchas

• Playwright fallback lives in ~/.cache/store-assets/npm. When the project has no own playwright/@playwright/test, render.mjs runs npm install --prefix ~/.cache/store-assets/npm playwright@<pin> once (not npx, which gives no importable module path), imports it from there, and sets PLAYWRIGHT_BROWSERS_PATH=~/.cache/store-assets/browsers, running install chromium only when that dir has no chromium* entry. Nothing is installed into the project or the skill.
• bin/lib.mjs is the single source of truth for reviewedHash() and parseArgs(). Both render.mjs's pre-flight and validate.mjs's real gate call the exact same function with the exact same arguments (reviewedHash(text.headline, text.subline), no fallback); a scene with no subline key (a headline-only combo scene) hashes subline as JavaScript's undefined coerced to a string, not empty string. Do not reintroduce a || '' fallback at only one of the two call sites, they will disagree again.
• templates/scene.html never hardcodes a machine path, brand value, or project copy. Device bezel/status-bar paths come from references/store-specs.md's "Devices" JSON (extracted at render time by render.mjs, not parsed by the browser); fonts/colors/logo/headlines/pills come from the project's own .store-assets/store-assets.json via query params. A combo scene's compositional constants (rotation angles, overlap offsets, margins) are the one exception: they are skill-level art-direction, not project config, and live as named constants in scene.html's own combo branch.
• ios-ipad-13 is frameless. DEVICE_BY_FORMAT maps it to the ipad Devices entry (frameless: true); pre-flight skips bezel/status-bar checks for it and instead requires source_ipad per scene (front part for combo, which renders as one single device). Rounded corner, width, top edge and shadow constants live in the Devices JSON (ipad, and ipad-landscape for ios-ipad-13-landscape), scene.html's frameless branch only reads them from deviceSpec. Config overrides (format_options.<id>.width_pct/top_pct, scene ipad_*_pct, scene formats) are validated in render.mjs's pre-flight; defaults keep existing projects' output unchanged.
• Milestone B (video, templates/preview.html + bin/render-video.mjs) is not built. Nothing in SKILL.md's Ablauf beyond stills is implemented yet; see the plan's Step 10.