Compile the article topic, product introduction, or open-source project intoa singleNeubrutalism prompt that can be handed directly to an image model.
Core principles:Style locked down, direction determined first. Neubrutalism is not "deliberately messy"; it is precisely controlled roughness: how thick the borders are, how hard the shadows are, how the color blocks clash—all are design decisions. The skill first determines which direction the input belongs to, then compiles according to that direction's template.
Read
- Generate prompt: read
references/compile-templates.md(three-direction templates + style lock + paragraph rules). - User wants examples or topic inspiration: then read
references/examples.md(four already-decided finished prompts + real case list).
Input
Prioritize inferring from user input; do not require filling out a form:
- Direction: article cover (A), product/tool visual (B), developer/open-source project visual (C). When ambiguous, default to A.
- Main headline: if the user provides the original text, copy it verbatim; do not translate or polish it; for Chinese headlines, 2-4 characters are recommended, with at most one line of small subtitle.
- Visual metaphor: translate the topic into a component-feel graphic—button, Toggle, terminal window, card stack, broken grid, label block. One main metaphor per image; do not make a complete dashboard.
- Aspect ratio: prefer user-specified; covers default to horizontal 16:9 or 5:2.
Workflow
- Determine direction: article/opinion → A; product website/interface/Pricing → B; open-source project/API/tutorial → C.
- Remind first for B/C: once product screenshots and code cards are seen through as fake, they will ruin the first impression that "this tool is honest." For direction B/C, by default recommend prioritizing referencing real cases (Gumroad, RetroUI, Panda CSS, real GitHub projects; the list is in
examples.md); AI-generated images should only be clearly labeledconcept mockups. Compile only after the user confirms they want generation. - Choose metaphor: extract one UI component metaphor from the topic. Abstract concepts must land on concrete components: automation → Toggle switch; methodology → terminal input card; assets → card stack; the trend itself → broken grid.
- Compile prompt: according to
compile-templates.md, output an already-decided finished piece following the corresponding direction's template, locking the style, headline, main metaphor, and negative constraints. - Output: selected direction + one complete prompt + one sentence of rationale for the choice. When the user only wants the prompt, omit the explanation.
Quality Gates
- Thick borders make structure visible; they are not decoration. Hard shadows (offset to the lower right, no feathering) turn components into objects.
- Flat, strong colors; actively avoid the blue-purple gradient SaaS default; do not use glassmorphism, soft shadows, or glossy 3D.
- Anti-refinement does not equal chaos: the surface can be rough, but the structure cannot be messy; the relationship between headline, components, and main visual must be readable.
- One image, one central metaphor; topics with many information levels and multiple process steps to explain are not suited to this style—tell the user directly.
- Do not generate content that looks like real readable code; for developer-oriented directions, use abstract block-like text lines instead of code.
- Do not fabricate fake UI microcopy or fake labels; Chinese titles must use the user's original text, with no fake Chinese characters.
- This skill only produces prompts or direction suggestions, and does not fabricate already-generated image results.