Compile a concept intoa singleprompt that can be handed directly to an image model, with the style locked to "technical schematic poster": a node-link topology diagram as the main visual, wrapped in a HUD instrument frame (corner data panels, legends, rulers, system logs).
Core principle:Style locked, the diagram is the content. This style is not adding a tech-feel filter; it is drawing the article's logical structure itself as an engineering diagram—nodes are roles, links are handoffs, diamonds are fan-out/fan-in. The clearer the structure, the better the diagram looks.
Two output modes
| Cover | Inline illustration | |
|---|---|---|
| Goal | Eye-catching on first screen, clickable | Explain the structure of one paragraph clearly |
| Aspect ratio (locked) | 5:2 landscape | 16:9 |
| Main title | Giant, rendered into the image | Very small amount of Latin small caps, or none |
| Topology complexity | Full diamond + named nodes + full HUD set | Single concept diagram, minimal HUD |
Single register
Pure black background + a single neon green glow + monospace type, cyber terminal / system monitoring HUD feel. The whole set has only this one color scheme, no alternatives.
The blue-background white-line engineering drawing has been split into a separate skill:
engineering-blueprint-sheet. That side isprinted paper(line-weight hierarchy, dimensions, title block, paper texture and folds), while this side isa glowing screen(uniform line weights, glow, scan lines). The elements of the two sides are not borrowed from each other—no folds allowed on the terminal, no glow allowed on the blueprint. If the user wants a blueprint, switch over there; do not adjust the color here.
Screen texture intensity
The place this style most easily fails is producing a clean vector flowchart—clean, correct, flavorless. The texture layer is not an optional filter; it isa mandatory section, existing independently of the content: the content is the flat line art, the texture is the screen carrying it.
Three tiers, choose one tier at a time,consistent across the whole article(the cover and all inline illustrations must use the same tier, otherwise one glance side by side makes it look fake):
| Tier | What it is for | What is added |
|---|---|---|
| CRT-01 CLEAN | High-information-density inline illustrations, extra-long-title covers | Horizontal scan lines + glow bloom + corner vignette |
| CRT-02 STANDARD (default) | Covers and most inline illustrations | Previous tier + phosphor vertical grain + screen curvature + edge defocus + glass haze + per-line brightness fluctuation |
| CRT-03 DEGRADED | Only for covers / single large images, about old, legacy, malfunction, or archived things | Previous tier + horizontal refresh bright band + rightward smearing + burn-in ghosting + snow noise + aged glass |
The user did not specify CRT-02.
One iron rule:The texture overlays the content and never eats into the content— Scanlines press over the title and node labels, but in thumbnail state all the text is still legible.
Read
- Compile prompt: read
references/compile-contract.md(disambiguation iron rule + locked core + fixed skeleton + the three texture-tier originals). The English paragraphs for the three SCREEN TEXTURE tiers are there; copy the whole paragraph, do not rewrite it yourself. - For finished-piece references or to batch-produce a whole piece: read
references/examples.md(the already-decided finished prompts for the cover + series illustrations).
Input
Infer from user input; do not require a form to be filled in:
- Mode: cover (5:2) or illustration (16:9). When producing a whole piece, output the cover first, then the illustration series.
- Texture strength: CRT-01 / CRT-02 (default) / CRT-03. If the user says “older”, “glitchy”, or “period feel”, go up to CRT-03; if they say “cleaner” or “too dirty”, drop back to CRT-01.
- Main title: copy the user’s original text verbatim, no translation and no polishing; a Chinese main title is recommended to be 2-8 characters, with at most one line of small subtitle. Only the cover renders a large title.
- Topology content: translate the paragraph logic into a node diagram—
- fan-out (one entry splits into multiple Agents)
- diamond (split → parallel → join → out)
- linear chain vs parallel (when discussing false dependencies)
- single-node self-loop (when discussing Loop)
- decision fork (when discussing Router / decision checklists)
Workflow
- Determine mode: cover locks 5:2, illustration locks 16:9. What the user wants is a blueprint, not a screen; convert
engineering-blueprint-sheet。 - Determine texture tier: default CRT-02; for a whole piece, stay on one tier all the way through.
- Choose topology: one image, one main structure, corresponding to the core logic of the paragraph. Abstract concepts must land on concrete topology (division of labor → diamond; false dependencies → chain breaking apart into parallel; acceptance → loop with a feedback cycle).
- Lock the signature devices: the whole piece—cover + all illustrations—shares the same set of HUD frames (corner panels / legend / ruler / log) + the same texture tier. Only the topology diagram and title in the middle change; the frame and texture stay unchanged word for word—this is the key to making the whole piece a series.
- Compile prompt: follow
compile-contract.md’s fixed skeleton to output the finished product, with no placeholders, no menu, and zero Chinese in the body (except the rendered title); copy the SCREEN TEXTURE section verbatim without rewriting it. - Output: mode + texture tier + one complete prompt + (optional) one sentence of rationale for the choice. Omit the explanation when the user only wants the prompt.
Quality Gates
- The topology diagram is the main visual; the HUD is the supporting cast; do not let panels and logs upstage the central node diagram.
- Single-hue iron rule: there is only one kind of green; the appearance of a second color means drift.The CRT texture is not an exception—RGB subpixel triads, chromatic separation, and rainbow fringes are all forbidden; here the old screen is a monochrome phosphor display.
- No paper elements are allowed: creases, water stains, paper grain, pushpin holes, line-weight hierarchy, dimension arrows, title-block tables—those belong to
engineering-blueprint-sheet, and their appearance means contamination. Here all lines are the same thickness; this is the syntax of the screen. - The texture layer is mandatory, and it must be a separate paragraph; writing only one line about scanline inside LOCKED will be ignored by the model, and the result will still be a clean vector image.
- Texture must not swallow the text: in thumbnail state, the main title and all node labels remain clearly legible. Scanlines biting through strokes, and glow blurring the title into a blob of light, both count as failed images.
- The node-to-edge relationships must be readable: entry, parallel branches, merge, exit, and loop-back—the structure must not blur in thumbnail state.
- The main title is rendered precisely; for Chinese titles use the user's original text, with no fake Chinese characters; for secondary small text use Latin field labels (NODE / EDGE / FAN-OUT / A1 / EXIT / [ok]).
- Do not generate large blocks of text that look like real readable code; logs and fields are short labels, not real code.
- Covers are always 5:2, illustrations are always 16:9, unless the user explicitly changes the aspect ratio.
- This skill only produces prompts; it does not fabricate already-generated image results.