Figma AI Generative Layouts & Auto-Annotation vs FluidCAD

“Generative layouts solve the specific, painful problem of component reflow when content changes length — the kind of thing that breaks a design system at the edges. Auto-annotation is the real win here: it closes the gap between the design surface and the developer's mental model without asking either party to change tools. The concern is consistency — if the annotation layer doesn't respect the existing token vocabulary in the file, it produces noise instead of signal, and early beta reports suggest the token mapping is imprecise on complex components.”

“The primitive here is automated design-spec extraction — Figma parses its own component graph and emits structured handoff annotations without a designer manually labeling anything. The DX bet is that removing the annotation step from the designer's workflow also removes the broken-telephone step from the developer's, which is a real problem worth solving. The moment of truth is whether the generated annotations match the token names your codebase actually uses — if they don't, you've traded manual annotation for manual correction, and that's not a win.”

“FluidCAD solves the thing OpenSCAD got wrong: the 'drag to prototype, lock to code' loop makes it accessible without sacrificing programmability. STEP export means it fits into actual hardware workflows, not just rendering. For software engineers doing mechanical work, this is the missing middle ground between Fusion 360's complexity and OpenSCAD's austerity.”

“The direct competitor to auto-annotation is Figma's own Dev Mode, which already does most of this, plus every design-to-code tool in the ecosystem — Anima, Locofy, Supernova — that has been doing automated annotation longer. Generative layouts break the moment a designer has strong layout opinions that don't match the AI's reflow heuristics, which is most senior designers most of the time. What kills this in 12 months: Figma ships it as a core feature included in all plans, commoditizing the beta and making the differentiation moot — the feature survives but the 'new thing' story dies.”

“Code-first CAD has a 30-year history of failing to reach mainstream adoption because engineers and designers don't want to write JavaScript. FluidCAD will appeal to a very narrow slice of software developers who also do mechanical work. The STEP import/export is table stakes, not a differentiator, and Onshape's API does everything this does for teams who need collaboration.”

“The job-to-be-done for auto-annotation is clear and singular: eliminate the handoff tax that exists between every designer and every developer in every organization using Figma today. That's a real job with real pain and Figma is the only entity with the right surface area to do it without a plugin. Generative layouts are a separate job — content-adaptive component reflow — and shipping both under one 'Figma AI' banner dilutes the message; these should be two distinct features with distinct onboarding paths, not one beta blob. The product earns a ship because the annotation job is complete enough to replace the current workflow, but the generative layouts piece needs its own moment-of-value story before it pulls its weight.”

“When AI can generate CAD from natural language, the tools that survive will be the ones with programmatic, diffable representations — not binary blob formats. FluidCAD's JavaScript-first approach puts it in exactly the right position for the AI-assisted hardware design wave that's coming. This is the OpenSCAD for the LLM era.”

“I appreciate the concept but the UI is clearly built by engineers for engineers. There's no real onboarding, the documentation assumes CAD literacy, and the JavaScript API surface is intimidating for anyone coming from traditional design tools. Until there's a visual-first entry point, this stays a curiosity for most designers.”