cover-light-product-with-docs

Light Product With Docs

Use this skill when one article needs both a cover and section-bound inline visuals in the light-product family. This skill is self-contained. Do not route runtime work to cover-light-product, light-product-kit, or illustration-light-product.

Hard Boundaries

• Accepted article sources: pasted article text, Markdown files, or plain-text files.
• Do not claim DOCX, PDF, remote article, or web-page ingestion support.
• The article source remains read-only.
• If no valid article content is available, ask the user for pasted content or a Markdown/plain-text path. Do not fall back to a single cover.
• Default output is returned in the conversation. Write a file only when the user explicitly provides an output path.
• An output path applies only to that requested path; do not overwrite or modify any other file.

Output Type

Use the explicit --out-type parameter to decide what to output.

• --out-type template: output the invocation template only.
• --out-type brief: output the article visual brief set only.
• --out-type prompt: output final image prompts for every planned asset.
• --out-type all: output the brief set first, then the prompts.
• Omitted --out-type: default to brief.

Treat 直接生成, 出图, 生成封面和配图, and 开始生图 as direct image generation only when the user explicitly asks for images.

Template Output

For template-only mode, output exactly this structure and fill every field:

使用 $cover-light-product-with-docs 生成一套文章封面+正文配图方案
文章来源：{article_source}
输出类型：{out_type}
封面用途：{cover_use_case}
正文配图用途：{inline_use_case}
正文配图数量：{inline_count}
语言：{language}
封面画幅比例：{cover_ratio}
正文主画幅比例：{inline_ratio}
产品/场景：{product_context}
已有图片处理：{image_handling}
补充背景：{context}
禁用元素：{forbidden_elements}

Required Inputs

Extract or infer:

• Article source: required.
• Topic / article thesis: required.
• Cover use case: X header, WeChat article cover, blog header, SaaS launch cover, PPT cover, LinkedIn header.
• Inline use case: product docs, feature walkthrough, article inline image, workflow explainer, module explanation.
• Inline count: this is a hard constraint. If 正文配图数量 is omitted, use 3. If it is explicitly supplied, accept only an integer from 1 to 5. Validate this before producing any template, brief, prompt, or image. An explicit 0, negative number, non-integer, or value above 5 must fail with a clear request to use an integer from 1 to 5; never clamp, round, expand, truncate, omit, or route to the base cover skill or cover-only behavior.
• Language: Chinese, English, or mixed Chinese-English.
• Product context: AI product, agent workspace, research flow, coding workflow, automation system, dashboard, knowledge base, or feature module.
• Cover ratio and inline ratio: optional; infer from use case when omitted.
• Extra context: optional.
• Forbidden elements: optional.