vibe-modeling

I'm sorry, but which ones of these are complex? I'm looking through some [1] [2] [3] of the output PNGs and they look trivial. Like, my first 3d model in Blender trivial. In comparison, here's one of my recent designs: what I would still call a very simple case [4]. And it's not like I'm a trained mechanical engineer working commercially, this is stuff I design in my spare time as a programmer. [1] - https://github.com/cjtrowbridge/vibe-modeling/blob/main/outp... [2] - https://github.com/cjtrowbridge/vibe-modeling/blob/main/outp... [3] - https://github.com/cjtrowbridge/vibe-modeling/blob/main/outp... [4] - https://object.ceph-eu.hswaw.net/q3k-personal/fe3e54e6df604a...

This has been easy with OpenSCAD for a long time. I have made lots of cool, complex models this way. I built a repo of the prompts I use to show the llm how to do this and it includes many of the models I've created this way... https://github.com/cjtrowbridge/vibe-modeling

There are more elegant solutions to this problem. Why are you trying to get an LLM to work with bloated, archaic tools that you have to rent from a feudal lord in the cloud when there are free open-source alternatives like OpenSCAD. This is just one example of a superior tool that's natively easy for LLMs to interact with, because the source files are just composable scripts containing lists of shapes and then lists of tools and parameters to apply to the shapes. I wrote a simple set of system prompts you can use in any repo to show any LLM how to make SCAD files with a whole bunch of cool examples. This is just another example where walking away from the bloated, inferior feudal system of SaaS and cloud models leads to simpler processes and outcomes with superior results in less time, for free. https://github.com/cjtrowbridge/vibe-modeli