Image Prompt
Scope
Only for artifacts already concrete enough to visualize (a specific .forge.js model, build brief, or HLD); route vague briefs to forgecad-design-spec first. Read minimum context — entry .forge.js, one key helper if it delegates geometry, brief/HLD — and capture what must survive the image model: artifact type and scale, major subassemblies, actuation style, visible mechanisms, material and color cues.
Core Rule
Image prompts, not concept art: show the final artifact clearly, preserve build and subsystem truth, and keep visible the seams, modules, hardware, and mechanical hierarchy that matter.
Negatives (the only negatives list — reuse it, never restate variants):
- no fake sleek consumer shell, no hidden mechanics
- no over-smoothed geometry, no sci-fi styling
- no CAD-drawing, blueprint, or dimension-arrow pretense
- no cutaway, sectioned, or exploded teaching view unless the user explicitly asks
- no text, labels, or humans
Prompt Skeleton
Block order: identity → mechanism truth → materials/color truth → pose/state → shot/camera/lighting → negatives. Fill in, don't copy:
A [artifact identity and scale], designed as a real buildable CAD-driven object, not a fantasy concept. [Major subassemblies and mechanism truth]. [Materials, colors, finish, visible hardware]. Show it in [pose / state]. [Shot, camera, background, lighting]. It should look physically buildable and mechanically honest, with visible part boundaries and serviceable architecture. No [negative 1], no [negative 2], no [negative 3].
Default shot: front-left three-quarter hero view, eye-level product camera. Alternate: rear-right three-quarter view showing motor placement and belt routing.
Modes
Default to ONE honest hero render; add support prompts only when the user asks. Prefer separate single-purpose images over collages or multi-view boards.
| Mode |
Job |
Signature phrases |
| Honest hero render (default) |
Final object clearly, still reads as buildable |
clean premium studio product render, physically buildable and mechanically honest |
| Builder-first mechanical |
Teach the build; bias to interfaces, seams, mounted actuators |
clear visibility of interfaces, seams, and subsystem boundaries, serious prototype, not a polished consumer shell |
| Mild exploded |
Assembly logic; major modules only, no per-screw chaos. Image-only — the CAD model stays the complete assembled product |
major modules separated by small clean gaps, no tiny floating fragments |
| Workshop prototype realism |
Feel like a real first prototype |
visible print lines and honest surface texture, uncluttered engineering bench background |
| End-effector close-up |
Wrist/gripper mechanism detail |
close-up on the wrist and end effector showing the mechanism clearly |
Writing Rules
- Use real artifact language: base, turntable, shoulder, rails, bearings, gripper, belt, pulley, shaft.
- Prefer visible subsystem truth over poetic adjectives.
- Keep exact dimensions out unless they matter visually and are already known.
- If a detail is uncertain, stay honest at the subsystem level — never invent internals.
- Ask for "physically buildable", "mechanically honest", "visible part boundaries" when central.
- Mention motors, belts, pulleys, shafts, guide rods, fasteners, or service covers only if genuinely part of the artifact.
- A short strong prompt beats a style dump.
Output Contract
Return: one sentence interpreting the artifact, the primary prompt first (usually the honest hero render), optional support prompts, and a short which-to-try-first note. Never bury the prompts under theory.
1---2name: forgecad-image-prompt3description: Write builder-honest AI image prompts from a concrete ForgeCAD model, build brief, HLD, or LLD without hiding how the artifact is built.4---5
6# Image Prompt
7
8## Scope
9
10Only for artifacts already concrete enough to visualize (a specific `.forge.js` model, build brief, or HLD); route vague briefs to `forgecad-design-spec` first. Read minimum context — entry `.forge.js`, one key helper if it delegates geometry, brief/HLD — and capture what must survive the image model: artifact type and scale, major subassemblies, actuation style, visible mechanisms, material and color cues.
11
12## Core Rule
13
14Image prompts, not concept art: show the final artifact clearly, preserve build and subsystem truth, and keep visible the seams, modules, hardware, and mechanical hierarchy that matter.
15
16Negatives (the only negatives list — reuse it, never restate variants):
17
18- no fake sleek consumer shell, no hidden mechanics
19- no over-smoothed geometry, no sci-fi styling
20- no CAD-drawing, blueprint, or dimension-arrow pretense
21- no cutaway, sectioned, or exploded teaching view unless the user explicitly asks
22- no text, labels, or humans
23
24## Prompt Skeleton
25
26Block order: identity → mechanism truth → materials/color truth → pose/state → shot/camera/lighting → negatives. Fill in, don't copy:
27
28```text
29A [artifact identity and scale], designed as a real buildable CAD-driven object, not a fantasy concept. [Major subassemblies and mechanism truth]. [Materials, colors, finish, visible hardware]. Show it in [pose / state]. [Shot, camera, background, lighting]. It should look physically buildable and mechanically honest, with visible part boundaries and serviceable architecture. No [negative 1], no [negative 2], no [negative 3].
30```
31
32Default shot: `front-left three-quarter hero view, eye-level product camera`. Alternate: `rear-right three-quarter view showing motor placement and belt routing`.
33
34## Modes
35
36Default to ONE honest hero render; add support prompts only when the user asks. Prefer separate single-purpose images over collages or multi-view boards.
37
38| Mode | Job | Signature phrases |
39|------|-----|-------------------|
40| Honest hero render (default) | Final object clearly, still reads as buildable | `clean premium studio product render`, `physically buildable and mechanically honest` |
41| Builder-first mechanical | Teach the build; bias to interfaces, seams, mounted actuators | `clear visibility of interfaces, seams, and subsystem boundaries`, `serious prototype, not a polished consumer shell` |
42| Mild exploded | Assembly logic; major modules only, no per-screw chaos. Image-only — the CAD model stays the complete assembled product | `major modules separated by small clean gaps`, `no tiny floating fragments` |
43| Workshop prototype realism | Feel like a real first prototype | `visible print lines and honest surface texture`, `uncluttered engineering bench background` |
44| End-effector close-up | Wrist/gripper mechanism detail | `close-up on the wrist and end effector showing the mechanism clearly` |
45
46## Writing Rules
47
48- Use real artifact language: base, turntable, shoulder, rails, bearings, gripper, belt, pulley, shaft.
49- Prefer visible subsystem truth over poetic adjectives.
50- Keep exact dimensions out unless they matter visually and are already known.
51- If a detail is uncertain, stay honest at the subsystem level — never invent internals.
52- Ask for "physically buildable", "mechanically honest", "visible part boundaries" when central.
53- Mention motors, belts, pulleys, shafts, guide rods, fasteners, or service covers only if genuinely part of the artifact.
54- A short strong prompt beats a style dump.
55
56## Output Contract
57
58Return: one sentence interpreting the artifact, the primary prompt first (usually the honest hero render), optional support prompts, and a short which-to-try-first note. Never bury the prompts under theory.
KoStard