Skip to main content
store-art is a skill from the Summer skill library: a guide your AI agent reads when the task matches, so it builds the good version on the first try. Make Summer Games store art per slot: key art, covers, icons, screenshots, trailer, size and text rules.

​
When your agent uses it

  • Making or choosing store art for Summer Games: key art, cover, icon, screenshots, trailer
  • Store.set_art rejects an image for its shape or size, or store.get_listing says an art slot is missing
  • Deciding whether a store image may carry text, and which slot falls back to which

​
Install

summer setup installs every skill for your agent. To add only this one:
Swap claude-code for your agent, such as codex or cursor. See Skills for every option.

​
The skill

This skill covers every store art slot per flow (desktop and mobile): size, shape, text rules, fallbacks, and why each one matters. Its current text lives on the hosted Summer Engine MCP, the same text the Studio agent reads, so it changes with the store and is never stale here. Load it before you act:
  1. summer_docs_read with id skill/store-art returns the current text when this machine is signed in (summer login).
  2. A host that shows MCP prompts or resources has it as the store-art prompt and the resource summer://skills/store-art.
  3. Without a store sign-in: https://docs.summerengine.com/llms.txt lists every docs page; fetch any page as .md.
Screenshots: summer_capture_gameplay takes them offscreen. Get past the title screen with the game’s own flags in args or with steps, e.g. {"args":["--autostart"],"steps":[{"wait":3000},{"shot":true},{"key":"Space"},{"wait":800},{"shot":true}]}. The one rule to keep even before you load it: Key art, covers and icons carry no text: the stores draw the title over them. Screenshots are real play.

​
From a shell

No Summer MCP tools in this session? Run each one as a command; when summer --version is missing or below 4.0, use npx -y summer-engine@latest in place of summer. Fields are flags in kebab-case (--scene-path res://main.tscn) or one --input '<json>', and summer ops describe <op> prints the exact input. The summer-cli skill has the rest.
  • publish-your-game: Publish a game on Summer Games through MCP: store page, art, build upload, submit, owner approval link.
  • store-listing: Write a Summer Games store page: title, tagline, descriptions, tags, per platform, and what never to write.
Source: library/skills/store-art/SKILL.md, rendered from summer-engine@4.3.0 on npm.