Content & publishing

WeChat article assets

Cover images, inline graphics and paste-ready cards at the sizes WeChat actually crops.

Paid $15 list, $12 until 2026-12-31 · one skill, yours for good. The outline, the steps and the file open after purchase.

Background

Visuals and deliverables only: covers, body images, card images, previews, export bundles. Never touch the Chinese body copy: titles, sentences and fact lists are read-only; log problems in qa/ instead of editing the copy. Publishing is out of scope for this skill.

Why it is built this way

Everything downstream is derived from two files: brief.md and the YAML header on copy/*.md. The card count decides how many files the batch produces, and the cover text decides what fits in 6 to 10 characters at 2.35:1. A missing field is raised as an error and never filled in, because a guessed dek or cover line gets rendered at 1080 wide and then has to be caught by a person rather than by a script.

The QA table asks for numbers because the eye cannot check them: 4.5:1 contrast, 96px main title at 1080 wide, a pixel-exact 900x383. The confirmed platform guidelines outrank the defaults in the same file, which is why the cover command pins layout=full with show_footer=false and show_credit=false; the default adds a brand mark and a page number, and both are banned there. Proofs come first for the same reason, since one cover and one card expose the font and the crop before seven cards are rendered.

Where it bites

• Chinese renders as boxes A font without CJK coverage turns every Chinese glyph into a box, and the file is still 1080x1440, so a size check passes while the cover is unreadable. One image has to be read character by character before delivery, and the font list starts at Source Han Sans, never a Western monospace face.
• Cover text pasted from the title The headline runs past 10 characters, wraps to a third line, and the 2.35:1 crop eats the top of the type. The cover field holds 6 to 10 characters over two lines, and a 375px preview before batch render shows the loss while it is still one file to fix.
• Seven cards, eight files The batch renders one extra card or leaves a gap in the numbering, and the upload order no longer matches the article. The YAML cards count and the 8-digit date plus purpose naming are the two places that number is written down, and the delivery layout expects card01 through card07.
• A generated lead image An AI illustration sits in the lead slot with a caption that reads like an on-site photo, and the sourcing quota for the whole batch breaks at once. The first-image truth row checks that image against the event, and render_real.py refuses a manifest whose cover is not a real image.

When to use it

Produce WeChat Official Account assets: 900x383 lead-story cover, 500x500 second-story cover, body images plus 1080x1440 card images, and a phone preview, then export docx/pdf/zip. Use when the user asks to \"make a WeChat Official Account cover\", \"produce WeChat Official Account card images\", \"make the images for this WeChat Official Account article\", \"render cards from a job sheet\", or \"export a WeChat Official Account document\". Not for publishing (use ai-trend-publish or publish manually).