科研 Skill
产品渲染图制作
product-render
Renders photoreal product images in Blender Cycles with studio lighting, a physical camera, and wear-aware materials, gated by a validation check. Use for hero shots.
SKILL.md
Product render
Turn a validated 3D assembly into images that read as photographs: for a landing page, a pitch deck or the final presentation. The bar is "a viewer believes it is a photo of a real, manufactured object". A render that looks like a CAD screenshot or a toy is worse than no render, because it tells the viewer the product is not real.
Talk to the user in their language. Show each image as soon as it exists, and save it to hw/renders/ at the
same moment.
Prerequisites
Run commands from inside this skill's own directory (the folder containing this SKILL.md), since script and reference paths below (such as scripts/foo.py) are written relative to it, not to the project root.
Inputs
hw/mech/— the assembly.blend, built byenclosure-engineer(enclosure, boards, battery, parts).hw/validation/*.json— the assembly validator report. Required (see Gate).hw/pcb/export/pads.json— the real pads, for solder fillets.pcb-engineerowns and writes it. For a board it did not build,scripts/kicad_pads.pycalls the same exporter.hw/brief.md— colors and finishes, where and how the product is used (this drives the shot list).
Outputs
hw/renders/<shot>.png(16-bit) plus<shot>.json, a sidecar with recipe, camera, samples and time.hw/renders/scenes/<shot>.pyor.blend— what is needed to re-render the shot.hw/renders/sheet_<round>.png— contact sheets of variants compared side by side.
Gate
Before any render:
- The geometry validator passed on the exact assembly being rendered. Use the same pose: validate in the frozen device frame, then move the whole assembly rigidly for the shot.
- The report is newer than the
.blend.
scripts/studio.py enforces both. --allow-unvalidated exists only for material tests and scenes that are
not an assembly. Never use it to get past a failing assembly. Fix the geometry at the source instead (owner:
enclosure-engineer).
Before calling the presentation done, every shot must pass references/realism-checklist.md.
Workflow
- Plan the shots with
references/shot-list.md. Pick 3–6 shots that show what the brief promises: size in the hand or on the body, the main interaction, the materials, and the inside (exploded or close-up). Ask the user only about taste decisions that change the set, such as colorway, mood or background. Default to a dark product on a dark studio; it reads best (see the checklist). - Freeze the geometry. Copy the validated assembly to
hw/renders/base.blendand never edit its geometry there. Changes to look (materials, lights, camera) go into a script that opens the frozen file. If a fix and a regression start undoing each other, stop. Rebuild in the fixed order: assembly → fit → solder → validate → freeze. Do not patch in a loop. - Materials:
scripts/materials.py(reference:references/materials.md). Map every object to a material kind with name globs:
Wear is on by default: fingerprints, smears, micro-scratches, and dust on up-facing faces. Clean surfaces look fake. Real scans (ambientCG CC0 sets) look better than the procedural fallback. Fetch them once, withblender -b base.blend --python scripts/materials.py -- \ --assign "Enclosure*=plastic_black:wear=0.4" "Window*=plastic_clear:wear=0.6" \ "Strap*=silicone:color=0.02,0.02,0.022" --wear-textures <ambientCG folder> --save look.blendtoolchain-setup. - Solder (any shot that shows a board):
scripts/solder.py --pads pads.json --board main=<collection>. It simulates each fillet from the real pad, stencil and paste volume. Wrinkles and slight asymmetry are correct. Floating or blobby solder is not. Run it last in the build, before validation. The contact line sits--edge-inset(0.03 mm) inside the copper, so zero-margin masks do not clash. If the validator still reports solder × mask on one part, the footprint's pad and mask opening disagree: send that topcb-engineer, and solder the rest with--exclude <ref>.--onlyand--excludetake ref globs, so you can enable parts one by one. - Preview first. Render
--format preview --preset previewfor every shot, and compare variants (HDRI rotation, colorway, exposure, f-stop) withscripts/contact_sheet.py. Show the sheet. Only then render finals. - Final:
scripts/studio.pywith--format 4k-vertical|4k-horizontal --preset final|hero. Run finals on a GPU. If the user's computer is a laptop or has no strong GPU, use a cloud GPU (references/cloud-gpu.md), and pull each image as soon as it finishes. - Check each image against
references/realism-checklist.mdbefore showing it. Name the problems you see before the user does. If the user rejects an image, write down the reason as a rule for the next shots.
blender -b look.blend --python scripts/studio.py -- --target "Product" --recipe dark-studio \
--view hero --lens 100 --fstop 8 --format 4k-vertical --preset final \
--emit "LED*=1,0.86,0.70:60" --validator-json hw/validation/assembly.json --out hw/renders/hero_dark.png
Recipes (scripts/studio.py --recipe)
| Recipe | Use | Key settings |
|---|---|---|
dark-studio | default hero, clear or dark products, LED on | world 0.012; one big soft key; 2 thin strips behind; weak top; AgX Base Contrast |
tabletop-hdri | "on the desk", lifestyle-neutral | studio HDRI for reflections, matte table, soft key; Khronos PBR Neutral |
white-seamless | catalog, spec sheets | curved backdrop, overhead softbox, fills; avoid white product on white |
hero-float | landing page hero | dark graphite wall with soft gradient, rim strips, optional glossy floor |
Details, light ratios and why each light is there: references/lighting-recipes.md.
Camera rules
- The scene's front is −Y.
--viewnames an azimuth and elevation around the product. The product faces the camera unless the shot is explicitly about the back (charging contacts, engraving). - Physical camera: 85–105 mm full-frame equivalent, which gives no wide-angle distortion on small objects. The
36 mm sensor side follows the long image side, so a vertical frame uses
sensor_fit=VERTICALwith sensor height 36. Leaving the 24 mm default crops the frame. - Depth of field is real but consistent. Small products need f/8–f/16 to stay sharp front to back. Anything at the same distance as a blurred object must be equally blurred, or the image reads as a composite.
- Focus is on the first surface the camera sees at the center, or on
--focus <object>(for example the LED).
Taste and pitfalls
- Never render before validating. A part poking through a wall gets noticed at once, and it costs more trust than any good render earns.
- Clear plastic is not glass. Use IOR ~1.49–1.59, a little volume absorption, an oily fingerprint film and micro-scratches. If it looks like a jewel, it is wrong.
- White products on white backgrounds turn into flat shapes. Use the dark colorway for hero shots and show white on dark or high-contrast scenes.
- Metal and glass look real only through what they reflect. Give them an HDRI or strip lights to reflect. A big softbox must not show as a white sheet across a screen or a window; use thin strips for edges.
- Cords, straps and fabric: use a real braided structure with fibers and lint (see the materials reference). A smooth tube looks fake at once.
- Hands and people: use a real rigged scan, fix its joints, and give the skin subsurface scattering. Do not let it go dark under studio light. If no good model is available, do not do a hand shot.
- Markings and labels are textures (laser marking, silkscreen, barcode). Use geometry only where it changes the silhouette or the reflections.
- Lights are invisible to the camera. Only the backdrop is seen. Caustics stay off, clamp indirect is 4, and blur glossy is 0.5. These stop fireflies without a visible loss.
- Animations: turn persistent data off, because it caused flicker every N frames. Render a low-res motion preview of every frame and watch it as a video before the final.
- Compositing into a user's photo is hard. Read
references/photo-compositing.mdand set expectations first. A clean studio shot beats a bad composite. - LED glow: use emission on the lens or phosphor plus a small point light just above it. Keep it subtle;
a lit LED should not light up the whole room.
studio.pyhides every light it did not create, so do one of these:- use
--emit; - tag your light with the custom property
hdt_keep_light = True; - make the glow an emissive mesh hidden from camera rays.
- use
- Offsets from a component: use
world_offset(obj, (dx, dy, dz)), which applies rotation only. KiCad and GLB component empties often carry a 1000× scale, andobj.matrix_world @ vputs the point metres away. - Targets:
--targettakes a collection, an object (with its children) or a glob. A glob that matches empties includes their children, and a glob can also match collection names (for a lineup). - Thin translucent parts over a dark cavity (membranes, TPU button caps, light windows) read dark with
a large subsurface scale. Use
MAT.get(kind, sss_mm=0.05)unless the part is lit from inside. - Exploded views:
- Gaps: about each part's plan diagonal × sin(camera elevation) plus its height, so no part covers the next one in the image.
- Layout: every part on one axis, in assembly order. Include every visible part (button caps, membranes, screws, gaskets).
- Check: look at the image for parts that overlap in 2D, not only in 3D.
- Engine: Cycles with OptiX. An A/B test found LuxCore no better for studio products and much slower
on a cold kernel cache (
references/cloud-gpu.md).
Scripts
| Script | What it does |
|---|---|
scripts/materials.py | PBR library (enclosure, metals, PCB parts, solder, LEDs, fabric, floors) with wear and per-part color variation; --list shows all kinds |
scripts/studio.py | recipes, camera, render settings, LED emission, the validation gate, sidecar JSON |
scripts/solder.py | Young–Laplace solder fillets from pads.json, conformed to the board surface; --only and --exclude per part, --edge-inset |
scripts/solder_geom.py | the pad rules of solder.py without Blender (wettable pads, inset, ref selection); tested by scripts/test_solder_geom.py |
scripts/kicad_pads.py | .kicad_pcb → pads.json: a thin wrapper around pcb-engineer's exporter (same format) |
scripts/contact_sheet.py | join previews into one sheet |
scripts/selftest.py | builds a test product and board, runs every recipe at thumbnail size; run it on a render machine (cloud GPU), not on a laptop that is also running the session |
All scripts run headless (blender -b … --python <script> -- <args>), print one summary line, and return a
non-zero code on failure. They work in scenes built in millimetres or in metres: sizes, light power and
texture scales follow the scene units.
References
references/realism-checklist.md— run it on every image before showing it.references/lighting-recipes.md— each recipe, light by light, and when to change it.references/shot-list.md— which shots tell the product story, with framing for each.references/materials.md— material values and the physics behind them, including solder.references/photo-compositing.md— placing the product into a real photo (camera match, shadow catcher, grain match).references/cloud-gpu.md— rendering on a cloud GPU, with speed and cost and the Cycles-versus-LuxCore note.
示例提示词
帮我用Blender给这款硬件渲染几张逼真的产品宣传图。
所属插件
安装该插件会一并获得同领域的 63 个 Skill / MCP。
同插件的其他科研 Skill
- ANDES电力系统动态仿真Runs ANDES power-system dynamic studies via PowerMCP: power flow, eigenvalue analysis, and time-domain simulation. Use for damping, stability, or oscillation-mode questions.
- 电池选型与电源预算Builds an evidence-tagged power budget and sizes a manufacturable battery with pouch outline, seals, and derating. Use when sizing runtime, mAh, charging, or supply rails.
- FPGA比特流生成与烧录Generates a Xilinx FPGA bitstream and programs it over JTAG, or burns an MCS image into flash for power-on boot. Use when flashing a board or diagnosing boot failures.
- 硬件项目发布包组装Assembles a hardware release package (fab files, BOM/CPL, carts, assembly guide, hashed manifest) and runs a ready-to-build gate. Use before ordering prototypes.
- 时钟域交叉风险审查Audits clock-domain-crossing risk on an FPGA design and applies the smallest safe synchronizer or constraint fix. Use to resolve CDC violations before sign-off.
- 硬件产品认证合规规划Plans certifications a hardware product needs per target market (FCC, CE/RED, UKCA, battery/radio rules), with cost and lead-time estimates. Use before PCB or enclosure tooling.
- Vivado XDC时序约束编写Authors a Vivado XDC timing constraint set from scratch: clocks, I/O delays, and timing exceptions. Use first, before timing closure, on a design with no or incomplete constraints.
- N-1/N-2应急违规处置Playbook for N-1/N-2 contingency violations: ranks contingencies and proposes preventive and corrective actions. Use after a study shows voltage or thermal problems.
- 潮流计算不收敛诊断Playbook for power-flow convergence failures in PSS/E, PSLF, PowerWorld, pandapower, PyPSA, surge, or OpenDSS. Use when a case diverges or fails to solve.
- 硬件成本核算与采购Prices a hardware product at multiple volumes with one-time vs per-unit cost, landed cost per country, and sourcing leads. Use to estimate unit cost before a pitch.
- RTL仿真覆盖率收敛Measures RTL simulation code coverage and iteratively closes it toward a target by adding testbench stimulus. Use for a sign-off-grade coverage report.
- 配电网DER接纳能力治理Playbook for distribution DER hosting-capacity limits: voltage rise, reverse flow, and thermal limits from PV and storage. Use to estimate how much DER a feeder can host.
- 电子电路设计与审查Designs, audits, or corrects an electronic circuit from a brief, schematic, or netlist, checking power domains, reset sequencing, and ratings. Use for circuit review.
- 硬件可制造性红队审查Red-team audit that fix-loops a hardware project to ready-to-build, re-deriving parts, rails, battery physics, and cost. Use for a reality check before committing to a design.
- 电力系统动态稳定处置Playbook for dynamic stability problems: poor damping, angle instability, or sustained oscillations from eigenvalue or time-domain studies. Use after an unstable study result.
- Egret电力市场调度优化Runs Egret market/operations optimization (DC-OPF, AC-OPF, unit commitment) via PowerMCP. Use for cheapest dispatch, unit commitment, or congestion checks.
- 电子元器件选型核查Researches electronic components against primary sources: part numbers, datasheet limits, lifecycle, stock, and price breaks, one dossier per part. Use to verify or source a BOM.
- EMC电磁兼容预测试Plans grounding, shielding, and filtering for EMC/EMI, and runs an emissions pre-scan with a root-cause fix sequence. Use before a lab test or after a failed EMI scan.
- 产品外壳参数化建模Designs a hardware enclosure as parametric CAD with STEP/STL/GLB output, a DFM check, and Blender assembly validation. Use when designing a case or checking fit.
- 电网频率响应问题处置Playbook for frequency problems: low inertia, high RoCoF, weak primary response, or UFLS risk after loss of the largest unit. Use when a study flags frequency issues.
- FPGA RTL到比特流全流程Drives a Xilinx FPGA design end to end through RTL, simulation, synthesis, implementation, and bitstream, gated at every stage. Use to run the complete build flow in one pass.
- 硬件产品全流程总协调Leads a physical electronic product from idea to a doable design, coordinating specs, parts, battery, PCB, enclosure, render, and cost sub-skills. Use starting a hardware product.
- 硬件原理图与BOM审查Reviews hardware projects: checks schematics against datasheets, pin connections, and firmware-to-hardware alignment across KiCad/Altium files. Use for a design alignment check.
- FPGA ILA在线逻辑调试Inserts an Integrated Logic Analyzer, programs the board, arms a trigger, and reads captured waveforms on real FPGA hardware. Use when sim passes but the board fails.
常见问题
产品渲染图制作能做什么?
Renders photoreal product images in Blender Cycles with studio lighting, a physical camera, and wear-aware materials, gated by a validation check. Use for hero shots。
如何安装产品渲染图制作?
在科搭 Codar 左侧点击「插件」,在「组件」页签搜索「产品渲染图制作」并安装;在 Claude Code 或 Codex 中可以发送本页的安装提示词,或下载 Skill 包后解压到 ~/.claude/skills 或 ~/.codex/skills。
产品渲染图制作需要哪些权限?
该科研 Skill没有声明额外权限;执行具体操作时仍由 Agent 按自身规则请求确认。
产品渲染图制作经过官方审核吗?
是。SpeedSkills 收录的每个版本都会记录内容摘要与权限声明,当前版本已通过安全审核。