Skip to content

Blog· Community

Share Your AI Workflow — What a Reproducible Record Should Contain

Which model is better at Zemax reconciliation, which prompt saves an optimization from detours, at which step the AI often goes wrong — none of these has a ready-made answer yet.

The LensBench TeamOct 17, 2026 · 1 min read

With AI-native ways of working, everyone is a beginner: which model is better at Zemax reconciliation, which prompt saves an optimization from detours, at which step the AI often goes wrong: none of these has a ready-made answer yet. This is exactly what this community most wants to build up.

You're welcome to share your AI workflow in the forum's "Workflows and designs". To let others reproduce and compare, we suggest a record contain:

  • Task: what problem you are solving (specs, starting design)
  • Model and client: which model and which AI client you used
  • Prompt or skill: the key instructions or template you gave the AI
  • Result: key numbers with evidence ids; if you ran verify, post its verdict; if not, mark it "unverified"
  • Time spent: roughly how long it took and how many tool calls were made
  • Where the AI went wrong: at which step it went off course and how you corrected it; this part is often the most valuable

Two reminders:

  • Please use public reference designs for design data (patents, textbooks, samples); you don't need to post your own designs.
  • Prompts and skills shared by others are instructions written for the AI; read them yourself before using them.

Docs ship with the software, same version; the reference sections are generated from code (Chinese only for now)