Compile an article topic, product introduction, or open-source project intoa singleNeubrutalism prompt that can be handed directly to an image model.
Core principles:Lock the style, determine the direction first. Neubrutalism is not "deliberately making a mess"; 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). - If the user wants cases or topic inspiration: also read
references/examples.md(four decided finished prompts + real case list).
Input
Prefer 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). Default to A when ambiguous.
- Main headline: if the user provides the original text, copy it exactly; 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: prioritize user specification; for 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 recognized as fake, they will ruin the first impression that "this tool is honest." For B/C directions, by default recommend prioritizing real cases (Gumroad, RetroUI, Panda CSS, real GitHub projects; the list is in
examples.md); AI-generated images are only for 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 a decided finished piece using the template for the corresponding direction, locking the style, headline, main metaphor, and negative constraints. - Output: selected direction + one complete prompt + one sentence of rationale for the choice. Omit the explanation when the user only wants the prompt.
Quality Gates
- A thick border is structure made visible, not decoration; a hard shadow (offset to the lower right, no feathering) turns a component into an object.
- Flat, strong colors; actively avoid the default blue-purple gradient SaaS look; 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 the headline, components, and main visual must be readable.
- One image, one central metaphor; topics with many information levels and multi-step processes 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 blocky text lines instead of code.
- Do not invent fake UI microcopy or fake labels; Chinese titles must use the user's original text, with no fake Chinese characters appearing.
- This skill only produces prompts or directional suggestions, and does not fabricate already-generated image results.