/punk-cover

name: punk-cover
description: Generate localized cover images and reusable image prompts from the shared Punk style library for articles, Xiaohongshu notes, WeChat public account posts, X posts, Instagram, Facebook, LinkedIn, YouTube, TikTok, Pinterest, Snapchat, Reddit, Threads, Bluesky, Medium, topic drafts, and requests for covers, social cover images, poster prompts, style-template-based image prompts, or image generation from long-form text. Use this skill to analyze source content, resolve unsupported ratios to the closest available generation ratio, select a localized visual style, save the final prompt, and generate the image when an image-generation tool is available.

Punk Cover

Core Rule

`punk-cover` is a cover-generation workflow, not a style owner. Select exactly one reusable style from the repository-level `styles/` library, then compile that style atom into the cover shape.

The workflow is localized. Detect the host system language/locale before presenting choices: use Chinese mode for `zh`, `zh-CN`, `zh-TW`, or another Chinese locale; use English mode for other locales. The user may explicitly override this with `中文`, `English`, or `中英双语`. In the selected mode, localize platform labels, style names, questions, notices, and generated supporting text. The source title and any user-provided proper nouns remain unchanged unless the user asks for translation.

The final image prompt is not a loose concatenation of "cover instructions + style instructions". It must be one integrated, cover-specific prompt that applies the selected style to the cover format.

Use three inputs:

1. `punk-cover` task fields: platform, requested aspect ratio, resolved generation ratio, language mode, optional output dimensions and output mode, title clarity, article summarization, cover communication goals, and universal output constraints. 2. The selected style's `META.md` metadata and `STYLE.md` reusable visual style atom. 3. `references/cover-prompt-blueprint.md`, which defines the full cover prompt shape.

The style file defines the reusable visual language. The cover blueprint defines the output form. The final prompt must fuse them into one complete cover-generation prompt.

Resources

• Read `references/style-catalog.md` to list or choose cover styles.
• Read `references/platform-catalog.md` before presenting platform choices or resolving an aspect ratio.
• Read `references/cover-prompt-blueprint.md` before composing the final prompt.
• For the selected style, read both:
• `../../styles/{style-id}/META.md`
• `../../styles/{style-id}/STYLE.md`
• Only expose styles whose `META.md` metadata has `outputs` containing `cover` or `poster`.
• Do not expose photo, avatar, portrait, pet-only, polaroid-only, or image-remix styles in the `punk-cover` menu unless their metadata explicitly includes `cover` or `poster`.
• Do not use legacy cover templates. Use only the selected style's `META.md`, `STYLE.md`, and `references/cover-prompt-blueprint.md`.

Workflow

1. Analyze the source material:

• Extract the core visual subject.
• Preserve the complete user title or topic when one exists, but do not copy the full article body into any output field.
• Draft an optional subtitle when the selected style has a subtitle field.
• Summarize context, audience, mood, metaphor, and banned elements.
• Convert long source material into concise derived fields: title/topic, 1-3 sentence context summary, visual subject, audience, mood, metaphor, and banned elements.

2. Confirm platform and aspect ratio before generating any prompt:

• Resolve the language mode from the host system before presenting this localized menu.
• Use `references/platform-catalog.md` for the localized platform menu and the complete platform-to-ratio mapping.
• Keep both the user's requested ratio and the resolved generation ratio in the task fields.
• For an unsupported requested ratio, automatically resolve to the numerically closest supported generation ratio. State in the active language mode that only the closest ratio can be generated, then use that resolved ratio directly; do not ask the user to choose another ratio.
• The X request `5:2` resolves to `21:9`.
• The WeChat public account request `2.35:1` resolves to `21:9`.
• Custom supported ratios are preserved; custom unsupported ratios use the same nearest-ratio rule.
• If the user only provides source content, ask which platform they want to publish to. Do not generate the prompt yet.
• If the user provides a custom ratio, resolve it as above and do not ask for platform unless the platform matters for wording.
• If the user provides exact width × height without a ratio, derive and preserve that ratio. If explicit dimensions and an explicit ratio conflict, ask which one should control before generating.
• Default to a single image. If the user explicitly requests a multi-size suite, preserve every requested ratio or output dimension and require at least two targets before generation.
• Never satisfy a multi-size request by cropping, stretching, padding, or placing multiple ratios in one grid; compile one independently composed prompt per target ratio.
• Only skip this question when the user has already provided a platform, a ratio, or explicitly says to decide everything automatically.

3. Confirm style before generating any prompt:

• Use the language mode already resolved from the host system language/locale; accept an explicit user override.
• When presenting style choices, show only the localized `Style name` and `Best for` content for the active mode. Do not show Chinese and English menu copies together unless the user selects bilingual mode or asks for both.
• In Chinese mode, use the Chinese style names and explanations from `references/style-catalog.md`; in English mode, use the English equivalents. The style ID remains unchanged in both modes.
• Accept a style ID or either localized display n