forgecad-image-prompt
starsforks
How to install forgecad-image-prompt?
forgecad/forgecad-public-kit/forgecad-image-prompt
$npx -y skills add ForgeCAD/forgecad-public-kit --skill forgecad-image-promptWrite builder-honest AI image prompts from a concrete ForgeCAD model, build brief, HLD, or LLD without hiding how the artifact is built.
SKILL.md
| 1 | # Image Prompt |
| 2 | |
| 3 | ## Scope |
| 4 | |
| 5 | 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. |
| 6 | |
| 7 | ## Core Rule |
| 8 | |
| 9 | 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. |
| 10 | |
| 11 | Negatives (the only negatives list — reuse it, never restate variants): |
| 12 | |
| 13 | - no fake sleek consumer shell, no hidden mechanics |
| 14 | - no over-smoothed geometry, no sci-fi styling |
| 15 | - no CAD-drawing, blueprint, or dimension-arrow pretense |
| 16 | - no cutaway, sectioned, or exploded teaching view unless the user explicitly asks |
| 17 | - no text, labels, or humans |
| 18 | |
| 19 | ## Prompt Skeleton |
| 20 | |
| 21 | Block order: identity → mechanism truth → materials/color truth → pose/state → shot/camera/lighting → negatives. Fill in, don't copy: |
| 22 | |
| 23 | ```text |
| 24 | 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]. |
| 25 | ``` |
| 26 | |
| 27 | Default shot: `front-left three-quarter hero view, eye-level product camera`. Alternate: `rear-right three-quarter view showing motor placement and belt routing`. |
| 28 | |
| 29 | ## Modes |
| 30 | |
| 31 | 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. |
| 32 | |
| 33 | | Mode | Job | Signature phrases | |
| 34 | |------|-----|-------------------| |
| 35 | | Honest hero render (default) | Final object clearly, still reads as buildable | `clean premium studio product render`, `physically buildable and mechanically honest` | |
| 36 | | 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` | |
| 37 | | 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` | |
| 38 | | Workshop prototype realism | Feel like a real first prototype | `visible print lines and honest surface texture`, `uncluttered engineering bench background` | |
| 39 | | End-effector close-up | Wrist/gripper mechanism detail | `close-up on the wrist and end effector showing the mechanism clearly` | |
| 40 | |
| 41 | ## Writing Rules |
| 42 | |
| 43 | - Use real artifact language: base, turntable, shoulder, rails, bearings, gripper, belt, pulley, shaft. |
| 44 | - Prefer visible subsystem truth over poetic adjectives. |
| 45 | - Keep exact dimensions out unless they matter visually and are already known. |
| 46 | - If a detail is uncertain, stay honest at the subsystem level — never invent internals. |
| 47 | - Ask for "physically buildable", "mechanically honest", "visible part boundaries" when central. |
| 48 | - Mention motors, belts, pulleys, shafts, guide rods, fasteners, or service covers only if genuinely part of the artifact. |
| 49 | - A short strong prompt beats a style dump. |
| 50 | |
| 51 | ## Output Contract |
| 52 | |
| 53 | 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. |
People who liked this also viewed
6 picksType
- ai-video-generationinference.sh Agent skills for using our API to give your agents access to hundreds of apps and other agentsSkillsJul 2026
- imagegen-frontend-webElite frontend image-direction skill for generating premium, conversion-aware website design references. CRITICAL OUTPUT RULE — generate ONE separate horizontal image FOR EVERY section. A landing pageSkillsJul 2026
- hyperframes-mediaWrite HTML. Render video. Built for agents.SkillsJul 2026
- media-useAgent Media OS, the single skill for every media need in a HyperFrames project. Resolve BGM, SFX, image, icon, brand logo, voice, color grade, or LUT into a frozen local file or paste-ready block + leSkillsJul 2026
- general-videoAuthor or edit a custom HyperFrames composition when no specialized workflow fits, or when BRIEF.md sets flow: companion. Use for longer or multi-scene pieces, brand and sizzle reels, montages, staticSkillsJul 2026
- product-launch-videoTurn a product or marketing URL, pasted script, or brief into a product launch / promo video — SaaS promos, feature reveals, product demos, app and company launches. Use when the user wants to market,SkillsJul 2026
