/guizang-social-card-skill

name: guizang-social-card-skill
description: Generate Guizang-style social card image sets, Live Photo motion cards, material-first Live Photo puzzle layouts, triple Live Photo collages, long-video-to-Live-Photo treatments, and WeChat official account cover pairs from articles, scripts, screenshots, product notes, subtitles, photos, or user-supplied videos. Use when the user asks for 小红书图文, Rednote/Xiaohongshu images, social cards, carousel images, 3:4 covers, Live Photo, 实况照片, 单视频实况拼图, 二宫格实况拼图, 三连实况拼图, 四宫格实况拼图, 微信公众号封面, WeChat 21:9 + 1:1 covers, Swiss Style, or magazine-style social images.

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.

Generated work must live in a task folder, not in the skill root. Default to `local-tests/<slug>/` inside this repository, or use the explicit output folder requested by the user. Do not create root-level task folders such as `social-card-*`, `livephoto-*`, `wechat-*`, `output/`, or loose rendered assets next to `SKILL.md`.

What To Produce

Use this skill for:

• Social card / carousel image sets: cover plus content pages, especially Xiaohongshu/Rednote 3:4.
• Short Live Photo motion cards when the user asks for Live Photo / 实况照片 and supplies video evidence or screen recordings.
• Material-first Live Photo puzzle layouts when the user has high-quality video assets and wants single-video, two-grid, three-grid, or four-grid motion cards with little or no added text.
• Triple Live Photo collages when the user has three short videos, three results, three viewpoints, or a high-information comparison that should stay inside one image-card unit.
• Long-video intake for Live Photo: diagnose whether to trim, speed up, split into a triple collage, or ask the user for a specific time range before rendering.
• 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. This skill only supports short, layout-bound Live Photo cards that replace a still image slot with video.
• Pure image editing with no layout or article extraction requirement.

Rednote Category Capability (capability circle)

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.

Core Principle

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?

Required References

Read these files as needed:

• `references/platform-specs.md` for exact ratios, output sizes, and naming.
• `references/style-system.md` for Guizang editorial and Swiss visual rules.
• `references/theme-presets.md` when choosing electronic-magazine palettes or Swiss accent palettes.
• `references/layout-recipes.md` when selecting carousel/social-card/WeChat page structures.
• `references/components.md` for the shared component spec: font stacks, type scale, minimum readable sizes, Chinese title length bands, Swiss card-fill mutual-exclusion rule, image-container ratio classes, spacing tokens, and Lucide icon rules.
• `references/background-systems.md` when building electronic-magazine WebGL/ink/paper backgrounds.
• `references/portrait-fill.md` when adapting layouts to 3:4 and avoiding under-filled vertical space.
• `references/content-planning.md` for cover hooks, page breakdown, and copy compression.
• `references/production-workflow.md` for HTML/CSS rendering and image handling.
• `references/live-photo-production.md` when the user asks for Live Photo / 实况照片 / 三连实况拼图, supplies video assets for a social card, or wants Xiaohongshu / WeChat motion-card delivery. It covers information budget, single vs triple Live Photo, long-video intake, and platform publishing reminders.
• `references/image-overlay.md` whenever text sits on top of a photo: photo qualification, localized tint fallback, and face / subject avoidance via multimodal subject mapping.
• `references/screenshot-treatment.md` when the user supplies an app / web / code / dashboard screenshot — picks `.frame-