guizang-social-card-skill

Create polished social card packages for Xiaohongshu/Rednote, WeChat Official Account, article covers, and platform thumbnails. This skill is self-contained. It borrows visual principles from the Guizang PPT style system, but it must not edit the original PPT skill, its templates, or its references. If the original PPT skill is available, you may read it for reference only. Put all generated work in the current project or in the user-requested output folder.

Use this skill for: • Social card / carousel image sets: cover plus content pages, especially Xiaohongshu/Rednote 3:4. • WeChat Official Account cover pairs: one 21:9 main cover plus one 1:1 square cover, composed together in the same HTML for visual checking. • Screenshot-heavy product posts, article covers, tutorial carousels, outdoor/lifestyle notes, AI/product update explainers. • Social images that need Guizang-style Swiss or editorial magazine layouts. Do not use this skill for: • Full slide decks or horizontal PPT websites. Use the PPT skill for that. • Long-form video generation. Use a video skill for that. • Pure image editing with no layout or article extraction requirement.

The 11 most-common Rednote (小红书) categories fall into three buckets. See references/category-cookbook.md for the recipe-by-recipe routing. Strong end-to-end (text, structure, and image story all in scope): • 旅行 (Travel), 职场 (Workplace), 推荐 (Recommended, after specifying a subtype). Strong on text & structure; image needs to come from the user or a sourced library: • 游戏 (Game), 影视 (Film/TV), 美食 食谱方向 (Food — recipes only), 彩妆 教程方向 (Makeup — tutorials only), 健身 (Fitness), 家居 (Home), 穿搭 精选方向 (Outfit — capsule/essay only). Outside scope — push back honestly rather than promise a result: • 美食 菜品大片摆盘 (food-photography showcase). • 穿搭 日常 OOTD 全身 (daily OOTD body shots; we cannot generate or simulate). • 情感 梦核 / 氛围感装饰风 (dreamcore / aesthetic-light styling — clashes with both Editorial and Swiss). • Y2K / 千禧辣妹 / 哥特萝莉 / kawaii decorated aesthetics. • Pure photography showcase posts where the image is the entire deliverable. When a request falls in the third bucket, name what we cannot do at intake — do not silently retrofit a layout that misses the user's intent.

Expression comes first. The goal is not to squeeze text into posters; it is to turn the source into a clear visual argument. For each page, decide: • What should the viewer understand in one glance? • What evidence, screenshot, or image supports it? • Which words must be large, and which can become captions or metadata? • What can be removed because it belongs in the post body, not the image?