A Raycast store extension is an icon and command stills

The store tile is a glyph plus a command-palette screenshot. Qwen holds the shortcut labels. VS Code marketplace is a different editor chrome. Do not generate a cinematic 'productivity' host.

A Raycast extension that sells is a store row: an icon, a command list a buyer will proof against the live palette, shortcut chords that match the README. Motion is optional. A constructed founder walking “how I run my day” is a host. It is not the listing.

The store tile is a glyph plus a command still

Digital tools have no unboxing. The fear is a thin file and a fake palette. Capture the real extension you would ship: command names matching the store copy, shortcuts matching the keymap, an icon that is the mark you will upload. Crop chrome that is not the SKU. The still is a document. Treat it like one.

Do not prompt a video model to “show a premium Raycast extension with cinematic productivity energy.” It will invent a cousin palette, a cousin chord, a cousin icon. A buyer who lands on the real store and sees a different command set is not looking at creative. They are looking at a lie.

If you do not have a screenshot yet, you still do not invent a host. You typeset a mock of the palette. Quote every string a buyer will proof: Clipboard History, ⌘⇧V, the extension name as it will appear. A photoreal operator pointing at a MacBook is a presenter. The SKU is the tile.

A Discord bot dashboard is a UI still, not a community clip is the same object class: a settings grid, not a community hang. Raycast is a launcher palette. Do not twin a server-promo playbook onto an extension tile.

Qwen holds the shortcut labels

Qwen Image 3 Text to Image is the stills row when the letters have to read. Catalog facts: Qwen’s third-generation image model, strong prompt adherence, complex text rendering in Chinese and English, intelligent prompt rewriting on by default, 4 credits, 2K max, qualities 1K and 2K. No audio. No duration. Aspects include 1:1, 16:9, 9:16, and 21:9.

Write the exact strings. If a command name or a shortcut chord must stay verbatim, say so in the prompt and inspect the still. Rewriting is a help for scene language, not a licence to paraphrase ⌘K into Ctrl+K. Set 1K while the words are in draft. Set 2K when the palette is the palette. There is no 4K chip on this row.

A video model is a bad typography engine. It will give you almost-commands and a panel you cannot ship. Approve the characters. Then consider motion.

Generate an image from text is the named agent job: you describe the still, the agent asks about style, aspect ratio, and count, then picks a model. Cost is priced per model, shown before you confirm. Name Qwen. A bare “make a Raycast extension” will land on a portrait row. Quote the palette. Scout at 1K. Keep at 2K when someone will zoom. Proof at 100%. One wrong character in a shortcut is a regenerate.

Text to image is the tool-shaped door for the same still.

Ideogram owns the icon lockup

Eight to twelve words that must read at tile size: extension name, one verb, a flat mark. That is Ideogram V4: text-to-image, 6 credits, posters and logos with crisp visuals and accurate text rendering listed. Quote the string. Do not ask a photoreal row to spell the extension name into a 3D laptop.

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

Neither row is a video model. There is no duration list because there is nothing to time. A listing that “needs motion” is a later image-to-video pass of an approved still, camera only. Motion will not correct a misspelled shortcut. If the printed chord is already sharp in the screenshot, you may not need a generate at all.

VS Code chrome is a different marketplace

A VS Code marketplace listing is Activity Bar chrome, a README hero, and an icon in a different grid. That is a different editor. Do not paste a Command Palette screenshot into a VS Code tile and hope the buyer does not notice. Do not paste a VS Code sidebar into a Raycast store row. The chrome is the SKU. Wrong chrome is a cousin product.

Do not generate a cinematic productivity host on either marketplace. A talking “I built this extension in a week” presenter is talent you did not cast, and a likeness if you seeded a real face. Empty palette. Letter the commands. Overlay a version chip if the number will change. Do not bake the shortcut into a video generate so a keymap change forces a new take.

The test is a pause at store-tile size. Can a buyer read the command and the shortcut? If the answer is a pretty laptop and a mouth, you made a brand film. If the answer is the glyph plus the palette, you made the listing.

FAQ

Can I generate a prettier palette instead of capturing the live extension?

You can typeset a mock on Qwen Image 3 at 4 credits, 2K, if you quote the real strings and proof them. You cannot invent commands or shortcuts. The live screenshot is the honest SKU. Ideogram V4 at 6 credits is the icon lockup, not a second palette.

Should the agent pick the image model for me?

Generate an image from text will pick a fitting row unless you name one. For a command list, name Qwen. For a glyph, name Ideogram. A portrait model will give you a mood of a desk, not a palette you can proof.

Is this the same job as a VS Code marketplace listing?

No. VS Code is Activity Bar chrome and a README still. Raycast is a launcher glyph plus a command-palette screenshot. Wrong editor chrome is a different store. Do not twin them in one generate.

Why not a cinematic productivity host as the store video?

Because the listing is type. A constructed host is a second asset you do not need, and a private-person problem if you referenced a real face. Hold the glyph. Hold the chords. Overlay the version that will change.