Guides

    A VS Code marketplace listing is an icon plus a screenshot row

    The SKU is a square icon and a row of editor stills with command names readable. Qwen holds the UI type. An npm readme hero (already a post) is a heading and badge row — a different shelf.

    Versely Team6 min read

    The SKU is a square icon and a row of editor stills with command names readable. Qwen holds the UI type. An npm readme hero (already a post) is a heading and badge row — a different shelf.

    A VS Code extension that converts is type a maintainer can proof at 100%: the marketplace icon as it will upload, command names as they appear in the Command Palette, the sidebar chrome a buyer will match against the live editor. It is not a cinematic coding session with invented glyphs. Letter the listing.

    The square icon and the screenshot row are the product

    Procurement of an extension is a pause test. The icon has to be the mark on the Marketplace. The screenshot row has to show this editor: Activity Bar, command names, a settings grid a buyer can proof. A photoreal hero of “a developer’s dark IDE at night” is a different object. Nobody copies a lamp. They copy the command.

    Microsoft’s Marketplace expects a 128×128 PNG icon. Gallery images are typically 1280×800 or 640×480. Exact pixels. Not a 16:9 trailer frame cropped “close enough.”

    Do not prompt a video model to “show a premium VS Code extension with a glowing palette.” It will invent a cousin command and a cousin sidebar. A buyer who lands on the real card and sees a different string is looking at a lie.

    Capture the live editor if the type already holds. Crop chrome that is not the SKU, including a leaked test email or a star count that will be stale tomorrow. If the live UI is unreadable, typeset a mock of the editor — not a host. Quote command names character for character. Format Document is not Pretty Print.

    Qwen holds the command names

    Body copy, the command list, a screenshot row that has to read as words. That is a page. Qwen Image 3 Text to Image is the stills row when the letters have to read: third-generation Qwen, complex text in Chinese and English, prompt rewriting on by default, 4 credits, 2K max, qualities 1K and 2K. No audio. No duration. Quote every string. Rewriting is not a licence to paraphrase editor.action.formatDocument into format on save. Scout at 1K. Keep at 2K when someone will zoom.

    Write the exact strings. If a command or keybinding must stay verbatim, say so in the prompt and inspect the still. A video model will give you almost-commands and a panel you cannot ship.

    Generate an image from text is the named agent job: describe the still, the agent asks about style, aspect, and count, then picks a fitting image model — or uses the one you name. Cost is priced per model, shown before you confirm. Name Qwen Image 3 when the command list is the product. A bare “make me a VS Code marketplace hero” is how you get a cinematic desk. Text to image is the editor-shaped door for the same still.

    Ideogram letters the icon

    Eight to twelve words that must read at tile size. Extension name, a one-word stamp, a flat mark. That is Ideogram V4: 6 credits, posters and logos listed, accurate text rendering. Quote the string. Do not ask a photoreal workhorse to spell the scope into a 3D laptop.

    Use Ideogram when the cover is a glyph more than a palette: name, one command claim, a square lockup the Marketplace will letterbox into 128×128. Use Qwen when the cover is the screenshot row. Mixing them in one generate is how you get a pretty mark sitting on unreadable chords, or a dense editor whose title is mush.

    Proof at 100%. One wrong character in the extension name is a regenerate. Overlay later if the version will change. Neither row is a video model. Motion on an approved still will not correct a misspelled command. If the printed chord is already sharp in the screenshot, you may not need a generate at all.

    An npm readme is a different shelf

    An npm readme hero is Qwen type, not a screencast already owns the package page: heading, npm i, license badges. That swarm is the registry hero. This page is the Marketplace listing. Mixing them is how a VS Code card becomes a package.json, and how a readme ships a cousin Command Palette.

    The install verbs are different objects. npm is npm i foo. VS Code is an icon plus a screenshot row of editor chrome. A Raycast store extension is an icon and command stills already owns launcher palette chrome. Do not paste a Command Palette screenshot into a VS Code tile. Wrong chrome is a cousin product.

    Do not generate a cinematic productivity host. Empty editor. Letter the commands. Overlay a version chip if the number will change. The test is a pause at tile size: can a buyer read the icon and the command names? If the answer is a pretty laptop and a mouth, you made a brand film.

    FAQ

    Can I put the command names in a video prompt so the terminal typesets itself?

    No. A video row will invent commands. Letter the screenshot row on Qwen Image 3 at 4 credits, 2K, or stamp the icon on Ideogram V4 at 6 credits, and proof the characters. Motion, if any, is a later still-to-motion pass of an approved card.

    Should the agent invent a typical extension name if I only said “VS Code marketplace hero”?

    No. Generate an image from text will fill something that looks like a Marketplace card. That something is not your extension. Write the icon mark, the command names, and the screenshot row, then name the stills row.

    When is Ideogram the better row than Qwen Image 3?

    When eight to twelve words must read at tile size — the extension name, a stamp, the 128×128 icon. Qwen Image 3 is the page: command list, screenshot row, a short body. Do not send a newspaper to Ideogram, and do not send a three-word lockup to a layout scout unless you already know it holds.

    Is the npm-readme post the same job as this Marketplace listing?

    No. The npm post is the package heading, install line, and badge row as a still. This page is the VS Code icon plus a screenshot row of editor chrome. Raycast is a launcher palette. A Veo terminal session is none of those.