v3: P2 prompt pack (scenes 00, II-V) + pilot bench - regime detect, HUD, hand scrub
This commit is contained in:
@@ -0,0 +1,55 @@
|
||||
# Scene prompt - Course III scene B: the pod (one IP, shared fate)
|
||||
|
||||
v2 diagram: the jacket around containers - app, sidecar, initContainer, volumes, probes,
|
||||
one shared network namespace. Six parts.
|
||||
Generate ~4 at 16:9, curate with the reject checklist, save to disk for pickup.
|
||||
|
||||
---
|
||||
|
||||
Dark technical exploded-view illustration in a cinematic sci-fi engineering style.
|
||||
Solid near-black deep void background, hex #070b14 - completely clean: no stars, no grid,
|
||||
no texture, no particles behind or around the objects. Matte dark metal-and-glass surfaces
|
||||
with glowing neon edge lighting: primary cyan #3fbaf5, secondary magenta #e879f9 accents,
|
||||
cool white rim highlights. Camera: fixed 30-degree isometric angle, subject perfectly
|
||||
centered with generous empty margins on all sides. Even studio lighting, no vignette,
|
||||
no lens flare, no depth-of-field blur. ABSOLUTELY NO text, no letters, no numbers, no
|
||||
words, no code, no glyphs, no labels, no arrows, no callout lines, no UI elements
|
||||
anywhere in the image - every surface marking must be an abstract geometric pattern
|
||||
only. Every component is fully separated from its neighbours by generous gaps of pure
|
||||
void - nothing touching, nothing overlapping, and no beams, cables, or connectors
|
||||
spanning between the separated parts.
|
||||
|
||||
The subject: one sealed capsule blown open into its six pieces, all floating apart in
|
||||
the void, mid-explosion.
|
||||
|
||||
The two halves of the capsule shell, upper left and upper right: smooth semi-transparent
|
||||
frosted-glass shells with a soft cyan rim glow, clearly two halves of one enclosure that
|
||||
has been opened, each floating alone.
|
||||
|
||||
Centre: the main core - an upright glowing cylinder of dark metal and glass with a
|
||||
strong cyan light column inside it, the heart of the scene and its brightest object.
|
||||
|
||||
Beside the core, slightly smaller: a companion cylinder of the same design language but
|
||||
with a magenta light column, clearly a partner unit rather than a twin.
|
||||
|
||||
Below the core: a flat gate wedge - a low dark chamfered block with a single amber-white
|
||||
glowing edge, positioned underneath everything like a foundation step.
|
||||
|
||||
To the lower right: a short stack of three thin crystalline discs with faint cyan edge
|
||||
light, neatly aligned but not touching, storage-like and passive.
|
||||
|
||||
---
|
||||
|
||||
## Build-side notes (not part of the prompt)
|
||||
|
||||
- **Slice plan:** 6 polygons - shell half L, shell half R, app core, sidecar cylinder,
|
||||
initContainer gate wedge, volume disc stack. Collapse closes the shell around the
|
||||
contents (the jacket); scrub blows it open to the hero. Clamp at hero.
|
||||
- **Probes:** NOT in the image - startup/readiness/liveness are legend entries + a small
|
||||
DOM accent on the core, keeping the part count sliceable. The exit-137 field note
|
||||
stays with this scene.
|
||||
- **Legend mapping (v2 terms):** shared network namespace "one IP" / app container "your
|
||||
process" / sidecar "proxy, logs, reload" / initContainer "runs first, to completion -
|
||||
the gatekeeper" / volumes "shared mounts" / probes "startup -> readiness -> liveness".
|
||||
- **Watermark:** Gemini sparkle bottom-right - strip with
|
||||
`bztmon-site/scripts/dewatermark.mjs` before slicing.
|
||||
Reference in New Issue
Block a user