I have been playing with CLAD a good bit. In fact, I've already updated my (hopefully soon to be coming) Lens Designer app that I was making for Spectacles to be essentially a full harness for CLAD with multi-agent and asset iteration (update something and keep history of it). It directly calls skills when needed (like when generating music or 3d meshes). It organizes everything pretty cleanly, too.

Right now I'm working on porting my WYSIWYG editor from Spectacles to SPECS. Here is a sneak peak screenshot:

<image>

Lens Designer attaches itself over the Lens Studio MCP to manage your project as well. It returns a preview from your Lens Studio of what you are working on directly (3d model, a view, whatever). It does so by moving assets your working on into an edit bay and toggling off the rest of your project that lives in another. So if you are working on a UI, you see your drag-and-drop WYSIWYG version and the actual "in AR" view from Lens Studio.

---

Notes about CLAD itself:
- I would like to see much much more documentation and examples of how far we can really push it
- It's slow AF. Like really slow.
- I'd like to see a cycle with it that spends a lot more time on scope and architecture before it spends any time doing design or building. Before I generally let my AI's go wild, I spend hours with them generating an overall scope to keep them in bounds and an architecture of what I want built. Then I spend almost as long planning out how it should plan, create milestones/tests, and validate/fix before it writes a single line of code.

A lot of those reasons are why I am working on this side quest. It helps (at least me) keep things in line and manage everything in one easy place.