// Edit OpenStoreShot projects through storeshot.project.json, render, validate, export, and keep reference usage inspiration-only.
| name | storeshot-designer |
| description | Edit OpenStoreShot projects through storeshot.project.json, render, validate, export, and keep reference usage inspiration-only. |
Use this skill when working on an OpenStoreShot project.
storeshot.project.json.pnpm storeshot validate <path>.slides, artboards, layers, locales, platforms, and exportTargets.storeshot.project.json as the source of truth.text, x, y, width, height, fontSize, fontWeight, fill, device, locked, or hidden.pnpm storeshot validate examples/demo-project/storeshot.project.json
pnpm storeshot render examples/demo-project/storeshot.project.json
pnpm storeshot export examples/demo-project/storeshot.project.json --platform ios --locale ja-JP
pnpm storeshot export examples/demo-project/storeshot.project.json --platform android --locale ja-JP
Check generated files under examples/demo-project/exports.
When a user asks to use a popular app as reference, convert it to high-level patterns:
Never copy logos, UI, screenshots, characters, or distinctive visual expression.
OpenStoreShot itself does not use API keys. Use Codex to create or update local assets and storeshot.project.json, then use the app to review the result. The pnpm storeshot imagegen background ... command is a local placeholder helper for demo/test assets, not a remote generation client. Prompts must still avoid direct-copy language, famous logos, and copyrighted characters.
Report edited slides/layers, validation results, render/export commands, output paths, and any remaining warnings or mock behavior.