thorlabs-blender-optical-path

Name: thorlabs-blender-optical-path
Author: k-telux

111stars2forks

How to install thorlabs-blender-optical-path?

k-telux/opticalmodeler/thorlabs-blender-optical-path

$npx -y skills add k-telux/OpticalModeler --skill thorlabs-blender-optical-path

Installs into the current project.

Summary

Build, audit, and revise physically plausible Blender optical-table figures from 2D schematics and manufacturer CAD. Use for Thorlabs-compatible mirrors, lens mounts, beamsplitters, posts, fiber launches, apertures, detectors, optical topology, fail-closed evidence, or Nature-sty

Files · 1

View on GitHub

SKILL.md

1	# Thorlabs Blender Optical Path
2
3	Convert a 2D optical schematic into a physically explainable, independently auditable Blender scene.
4
5	## Load the relevant references
6
7	- Read [physical-gates.md](references/physical-gates.md) before geometry, CAD placement, or mechanical review.
8	- Read [evidence-contract.md](references/evidence-contract.md) before declaring any PASS or preparing a release.
9	- Read [history-derived-rules.md](references/history-derived-rules.md) when revising an existing scene or when old fixes may have regressed.
10	- Read [project-case-study.md](references/project-case-study.md) for the complete G1/G2 2D-to-3D example.
11
12	## Authority and revision rules
13
14	1. Apply system constraints first, then the newest explicit user wording or annotated screenshot, then active project rules, then this general skill, and only then older artifacts or PASS labels.
15	2. Freeze an accepted package. Start a new revision for every correction; never overwrite the prior evidence package.
16	3. Keep one writer for the shared Blender generator. Use helpers as read-only optical, mechanical, CAD, evidence, and visual reviewers unless an isolated write scope is explicit.
17	4. Translate every correction into object families, world-space geometry, a measurable gate, and required evidence before editing.
18	5. Use `BLOCKED` or `UNVERIFIED` when real geometry or evidence is missing. File existence, imported CAD, process success, labels, AABB contact, and self-reported text are not proof.
19
20	## Core workflow
21
22	1. Build a machine-readable map: `schematic node -> experimental role -> real asset -> optical/fiber/electrical ports -> support path`.
23	2. Inventory every branch, component, beam segment, beam height, aperture, connector, and required detector endpoint.
24	3. Acquire official CAD when licensing permits. Record part number, source URL, SHA-256, unit scale, bbox, local optical axis, surface normal, aperture, and provenance. Mark modeled or surrogate parts explicitly.
25	4. Solve optical constraints first: centers, surface normals, reflection, splitting planes, branch endpoints, and zero-radius clearance.
26	5. Solve mechanics post-first from verified table holes through real fasteners, clamps, holders, posts, mount faces, and device interfaces.
27	6. Fix the shared placement or transform root cause. Prove one representative repeated assembly before propagation, then reopen and recheck every copy.
28	7. Render bright audit views before beauty views. Use cutaways or transparency only to expose hidden, already-measured interfaces.
29	8. Complete the saved-scene, visual, export, document, hash, and rule-compliance gates in the evidence contract.
30
31	## Required semantic separation
32
33	- Treat free-space optical rays, guided fiber, and electrical/coaxial cables as different object families, materials, ports, and audit records.
34	- Terminate free-space light at the physical coupling surface; continue only the guided fiber from the ferrule/FC interface.
35	- Use open geometry for apertures and slits. A centered ray through an opaque disk is a collision, not a PASS.
36	- Remove duplicate surrogates and unexplained placeholders after the real or declared modeled assembly exists.
37
38	## Publication rendering
39
40	After physical gates pass, produce a clean editorial scene with restrained metals, readable black-anodized edges, physically modest glass, thin emissive beam cores, soft halos, and uncluttered labels. Preserve topology and geometry while changing camera, lighting, materials, or presentation. Nature-style appearance never replaces mechanical evidence.
41
42	## Completion language
43
44	- `PASS`: every applicable active gate has fresh evidence.
45	- `PARTIAL/SCOPED`: only a declared subset was audited.
46	- `UNVERIFIED`: required evidence is missing or cannot distinguish the claim.
47	- `BLOCKED`: a known requirement fails.
48
49	Never promote `PARTIAL/SCOPED` to whole-system PASS.

People who liked this also viewed

6 picks

Type

thorlabs-blender-optical-path

111stars2forks

View on GitHub

How to install thorlabs-blender-optical-path?

k-telux/opticalmodeler/thorlabs-blender-optical-path

$npx -y skills add k-telux/OpticalModeler --skill thorlabs-blender-optical-path

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Thorlabs Blender Optical Path
2
3	Convert a 2D optical schematic into a physically explainable, independently auditable Blender scene.
4
5	## Load the relevant references
6
7	- Read [physical-gates.md](references/physical-gates.md) before geometry, CAD placement, or mechanical review.
8	- Read [evidence-contract.md](references/evidence-contract.md) before declaring any PASS or preparing a release.
9	- Read [history-derived-rules.md](references/history-derived-rules.md) when revising an existing scene or when old fixes may have regressed.
10	- Read [project-case-study.md](references/project-case-study.md) for the complete G1/G2 2D-to-3D example.
11
12	## Authority and revision rules
13
14	1. Apply system constraints first, then the newest explicit user wording or annotated screenshot, then active project rules, then this general skill, and only then older artifacts or PASS labels.
15	2. Freeze an accepted package. Start a new revision for every correction; never overwrite the prior evidence package.
16	3. Keep one writer for the shared Blender generator. Use helpers as read-only optical, mechanical, CAD, evidence, and visual reviewers unless an isolated write scope is explicit.
17	4. Translate every correction into object families, world-space geometry, a measurable gate, and required evidence before editing.
18	5. Use `BLOCKED` or `UNVERIFIED` when real geometry or evidence is missing. File existence, imported CAD, process success, labels, AABB contact, and self-reported text are not proof.
19
20	## Core workflow
21
22	1. Build a machine-readable map: `schematic node -> experimental role -> real asset -> optical/fiber/electrical ports -> support path`.
23	2. Inventory every branch, component, beam segment, beam height, aperture, connector, and required detector endpoint.
24	3. Acquire official CAD when licensing permits. Record part number, source URL, SHA-256, unit scale, bbox, local optical axis, surface normal, aperture, and provenance. Mark modeled or surrogate parts explicitly.
25	4. Solve optical constraints first: centers, surface normals, reflection, splitting planes, branch endpoints, and zero-radius clearance.
26	5. Solve mechanics post-first from verified table holes through real fasteners, clamps, holders, posts, mount faces, and device interfaces.
27	6. Fix the shared placement or transform root cause. Prove one representative repeated assembly before propagation, then reopen and recheck every copy.
28	7. Render bright audit views before beauty views. Use cutaways or transparency only to expose hidden, already-measured interfaces.
29	8. Complete the saved-scene, visual, export, document, hash, and rule-compliance gates in the evidence contract.
30
31	## Required semantic separation
32
33	- Treat free-space optical rays, guided fiber, and electrical/coaxial cables as different object families, materials, ports, and audit records.
34	- Terminate free-space light at the physical coupling surface; continue only the guided fiber from the ferrule/FC interface.
35	- Use open geometry for apertures and slits. A centered ray through an opaque disk is a collision, not a PASS.
36	- Remove duplicate surrogates and unexplained placeholders after the real or declared modeled assembly exists.
37
38	## Publication rendering
39
40	After physical gates pass, produce a clean editorial scene with restrained metals, readable black-anodized edges, physically modest glass, thin emissive beam cores, soft halos, and uncluttered labels. Preserve topology and geometry while changing camera, lighting, materials, or presentation. Nature-style appearance never replaces mechanical evidence.
41
42	## Completion language
43
44	- `PASS`: every applicable active gate has fresh evidence.
45	- `PARTIAL/SCOPED`: only a declared subset was audited.
46	- `UNVERIFIED`: required evidence is missing or cannot distinguish the claim.
47	- `BLOCKED`: a known requirement fails.
48
49	Never promote `PARTIAL/SCOPED` to whole-system PASS.

People who liked this also viewed

6 picks

Type