An Obsidian plugin listing is a readme hero, not a PKM talking head
The community listing is a heading, install line, and settings still. Qwen holds the type. A Notion template gallery tile (already a post) is a database cover — a different app.
The community listing is a heading, install line, and settings still. Qwen holds the type. A Notion template gallery tile (already a post) is a database cover — a different app.
An Obsidian plugin that sells from the community list is a tile someone can read at thumbnail size: the plugin name, the one-line install, a settings pane whose toggles match the README. It is not a cinematic "second-brain" host walking PARA. Asking a video model to typeset Settings while it invents a PKM coach is how you get a cousin pane and a face you did not hire.
Heading, install line, settings still
Community listings are judged as a grid. Buyers scan names, not monologues. The frame that answers "is this the plugin with that command" is the hero: readable heading, true install line, a settings screenshot that matches what Community plugins will actually open. Inventing a prettier vault answers "does this look like a movie about notes."
Do not generate a settings pane and present it as the plugin if the labels are wrong. Quote the strings. "Daily notes", "Hotkey", "Install" — the brief is those glyphs, not "a cozy dark-mode vault." Capture the real settings window when you have one. Generated type is for the graphic that is not in the file yet. Do not prompt a model to "clean up" setting names it will then misspell.
Keep private faces out of the hero. A photoreal "that girl with a vault" is a likeness you did not clear. Empty-enough UI. True type.
Qwen holds the type
Lettering is a still job. Most photoreal models will give you a window-shaped texture with word-shaped smears. That is not a plugin name. Video models are a worse typesetter.
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 the plugin title or install line must stay verbatim, say so in the prompt and inspect the still. Rewriting is a help for scene language, not a licence to paraphrase Dataview into Data view. Set 1K while the words are in draft. Set 2K when the hero is the hero. There is no 4K chip on this row.
Qwen typesets a lockup. Proof at 100%. A wrong character is a different plugin. Do not ask Qwen for a photoreal founder holding a phone. That is a host. The SKU is the heading. Text to image is the catalog door for that still.
Seedream for the dense pane; the agent is a still job
A full settings grid is denser than a three-word title. Seedream 5.0 Pro is ByteDance's flagship text-to-image row: 7 credits, native text rendering in 14 languages, control over dense layouts and structured designs. Quote the schema. How many toggles. Which section headers. Proof at 100%.
Use Seedream when the hero is the settings pane. Use Qwen when the hero is a heading plus an install line. A real screenshot beats both.
Generate an image from text is the named still job: you describe the cover, the agent asks style, aspect, and count, then picks an image model — or uses the one you name. Priced per model, shown before you confirm. It is not a talking-presenter generate.
Name the row when the listing is the SKU. "Qwen Image 3, plugin heading and install line, these exact strings, no people." Stop. "Make me a productivity girl explaining my second-brain plugin" is the wrong object. Most listing weeks should stop at the still.
Notion is a different app. A PKM mouth is not the listing.
A Notion template gallery tile is a cover with readable type is already a post. That SKU is a database cover: property labels, a layout a buyer will duplicate. Obsidian is not Notion. Community plugins install from a list inside the app. Do not copy a Notion property grid onto an Obsidian settings still. Different app. Different tile.
A generated "PKM girl" walking PARA is not the community listing. Speech is optional. Type is not. Do not lipsync a generated face holding "your" vault. If a human must speak, that human is a real named person on a different day, pointing at the approved hero. Generation can still do the tile. It cannot be the coach.
If the marketplace title must sit outside the UI, add a text overlay burns one authored line, whole clip, top / center / bottom. It does not transcribe. Use it on a screenshot you already approved. Read every label. Leave the face off the generate.
FAQ
Can a talking video model typeset the plugin name if I write it in the prompt?
Do not. Prompted type in a video generate is a miss you cannot edit, and the model will still invent a host around it. Generate the hero as a still on Qwen Image 3 or Seedream 5.0 Pro, or keep a screenshot.
Qwen or Seedream for the community tile?
Qwen Image 3 is the lettering scout: 4 credits, 2K, English and Chinese type, prompt rewriting on by default. Seedream 5 Pro is the dense-layout row: 7 credits, 14-language type, structured designs. A heading plus install line is Qwen. A full settings grid is Seedream. A real screenshot beats both.
Is a generated "PKM girl" acceptable if we disclose she is AI?
Disclosure does not make her the listing. The community SKU is the heading, the install line, and the settings still. A constructed host is a second product and a likeness you did not need. Keep the UI. Keep the labels. Leave the face off the generate.
Do I need the agent if I already know the model?
No. Name Qwen or Seedream yourself. The agent is for the still job when you want it to ask aspect and count before it spends. It will not turn a talking-head brief into a community tile. It will not make Obsidian into a Notion cover.