WeChat Official Account Smart Layout

Problem

When WeChat official-account articles are converted from plain Markdown, the result can read like a flat text dump: weak emphasis, unclear metadata, and layout decisions left to ad-hoc formatting. This skill turns composition into a constrained fence-block system where modules define the information skeleton and themes define the reading tone.

How It Works

• Start with explicit ::::title and ::::digest blocks instead of relying on automatic extraction from the first # heading or first paragraph.
• Choose a module stack based on article type, for example hero, metrics, infographic, and cta for product launches, or toc, image-steps, checklist, and faq for tutorials.
• Build a placeholder skeleton first, then fill in fields and prose; the workflow requires reading references/module_reference.md before writing module fields to reduce render failures caused by guessed field names.
• Emit a .md source file using standard Markdown plus fence blocks, without HTML tags, and use full HTTPS image URLs.

Scope and Caveats

This is useful for repeatable authoring pipelines that produce layout-ready official-account source files. Module fields differ significantly, and WeChat-native components such as profile, videosnap, and vote depend on real account information. Avoid stacking modules for visual variety; the number of modules should match the article's information density.