wechat-visual-director
Project-level visual direction skill for WeChat Official Account articles. Use when planning, improving, diversifying, generating, or reviewing cover images and body illustrations for公众号文章, especially when Codex image generation should be used without being constrained by repetitive preset-based illustration skills.
- License 许可
- MIT
- 最近更新
- 2026-11-07
- Stars
- ★ 11
- Forks
- 5
01 前言 Front Matter
- name
- wechat-visual-director
- description
- Project-level visual direction skill for WeChat Official Account articles. Use when planning, improving, diversifying, generating, or reviewing cover images and body illustrations for公众号文章, especially when Codex image generation should be used without being constrained by repetitive preset-based illustration skills.
02 资源文件 2
- 参考文档agents/openai.yaml222 B
- 参考文档references/visual-strategy.md1.7 KB
03 SKILL.md 正文
WeChat Visual Director
Use this skill before generating article visuals. Its job is to choose visual concepts that fit the article, not to force every image through the same style preset.
Core Rule
Design first, generate second.
Do not start with type + style + palette. Start with article role, reader emotion, evidence type, and what the image must make easier to understand.
Visual Workflow
- Classify each needed visual.
- Cover: promise, tension, or central metaphor.
- Evidence visual: real screenshot, repo evidence, chart, table, UI state.
- Explanation visual: architecture, workflow, comparison, framework, timeline.
- Scene visual: workplace pain, decision moment, human context.
- Decide whether the visual should be generated.
- Use real screenshots for UI, repo pages, CLI output, dashboards, and product states.
- Use generated images for conceptual covers, scenes, metaphors, and explanatory illustrations.
- Do not generate decorative filler.
- Create 2-3 distinct visual routes for important images.
- Each route must differ in metaphor, composition, and rendering language.
- Avoid minor palette-only variation.
- Pick one route and write a prompt file.
- Save prompts before generation.
- Keep on-image text minimal; prefer no text for complex Chinese labels.
- If text is required, use short Chinese labels only.
- Generate with Codex native image generation when available.
- Use the native
image_gen/imagegencapability directly in Codex. - Do not route through a separate Codex CLI on another computer.
- Use
baoyu-image-genonly when an explicit API provider is needed.
- Use the native
- Review the image.
- Reject images that look like generic AI stock art, repetitive template covers, fake dashboards, unreadable text, or unrelated metaphors.
- Regenerate from a revised prompt; do not patch generated text with programmatic overlays.
Diversity Matrix
For a multi-image article, intentionally vary at least three dimensions:
- Composition: close-up, overhead map, split-screen, layered system, single object, human scene.
- Visual language: editorial photo-real, hand-drawn notes, precise product diagram, magazine infographic, cinematic metaphor, paper cutout, UI screenshot.
- Cognitive function: hook, proof, compare, sequence, explain, summarize.
- Texture: clean digital, paper, marker, screen glow, realistic workplace, blueprint.
- Camera: macro, desk-level, isometric, documentary, top-down, wide scene.
Never make every body image share the same border, palette, icon style, or abstract blob background.
Use External Skills As References
- Use
visual-storytelling-designwhen the article has data, comparisons, mechanisms, or claim framing that needs annotation and honest context. - Use
aestheticwhen visual hierarchy, mood, typography, or inspiration-quality review is needed. - Use
baoyu-article-illustratoronly after this skill has decided image roles and routes. - Use
baoyu-cover-imageonly for cover generation, not for all body images.
Output Contract
For visual planning, produce:
- Visual inventory with image role, evidence/generation decision, and placement.
- Route options for cover and key body visuals.
- Final prompt file paths to create.
- Generation aspect ratios.
- Review checklist and rejection criteria.
For direct generation, create prompt files first, then generate.
04 同仓库更多 Skills
xhs-pharma-social-listening
Run evidence-disciplined Xiaohongshu social listening for foreign pharma employee pain points. Use when the user asks to collect and analyze notes/comments about pharma companies, aliases, roles, compliance, medical affairs, or AI topics, then produce a cited and scored sampled-insight report. Includes independent-evidence counting, MediaCrawler batch collection, and CAPTCHA/461 fallback to Agent Reach/OpenCLI.
healthcare-phi-compliance
Protected Health Information (PHI) and Personally Identifiable Information (PII) compliance patterns for healthcare applications. Covers data classification, access control, audit trails, encryption, and common leak vectors. Use when code touches PHI or PII in a healthcare system, or when auditing access control, audit trails, or leak vectors.
healthcare-eval-harness
Patient safety evaluation harness for healthcare application deployments. Automated test suites for CDSS accuracy, PHI exposure, clinical workflow integrity, and integration compliance. Blocks deployments on safety failures. Use when a healthcare deployment must be gated on patient-safety tests for CDSS accuracy, PHI exposure, and workflow integrity.
healthcare-emr-patterns
EMR/EHR development patterns for healthcare applications. Clinical safety, encounter workflows, prescription generation, clinical decision support integration, and accessibility-first UI for medical data entry. Use when building EMR or EHR features such as encounter workflows, prescription generation, or clinical data entry UI.
healthcare-cdss-patterns
Clinical Decision Support System (CDSS) development patterns. Drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), alert severity classification, and integration into EMR workflows. Use when building clinical decision support — drug interaction checks, dose validation, clinical scoring, or alert severity.
dxy-task-clarify
用户的请求含糊、缺背景、缺资料说明、缺读者或用途时使用。先用少量带选项的追问把任务问清楚,写成任务卡,用户确认后再执行。尤其适用于医生、科研人员和药企各岗位的工作,例如「帮我分析一下这些数据」「帮我准备明天的拜访」「写个总结」「做个 PPT」「回一下这封邮件」「整理一下会议纪要」「整理一下这些文献」「帮我准备下周的讲课」「写个病例汇报」「帮我写个提示词」。用户说「先问我」「帮我理清需求」「我不知道怎么描述」「我不会问 AI」时也使用。用途、资料、读者都已说清的请求,纯翻译,以及写代码、改代码,不使用。