Figma for Agents vs Luma AI Dream Machine 2.0

“Read-only design context was useful; write access is transformative. Agents constrained to your actual design system tokens means the output is actually usable. The Skills markdown API is elegant — no plugin overhead. Works with all major MCP clients out of the box. The free beta window is a good time to build institutional muscle.”

“Agents writing to your production design system is a liability without a robust approval layer. The review UX for design diffs is nowhere near as mature as code review. Design systems carry brand, accessibility, and legal implications. And 'free during beta' with warnings they haven't figured out pricing means workflows you build could get expensive fast.”

“Camera controls on a video gen model are a real feature, not a checkbox — Runway and Kling are shipping similar controls and Dream Machine 2.0 is roughly competitive, with scene consistency being the area where Luma has a credible edge for multi-shot work. The failure mode hits fast though: ask it for a scene with two characters interacting across a table with consistent lighting and you'll get three clips where the faces share a general vibe but not an identity. What kills this in 12 months isn't a competitor — it's that the underlying model providers (likely Google Veo or OpenAI's video stack) will bake camera primitives natively into their APIs, and Luma's entire moat collapses to distribution. Ship now, reassess in Q1 2027.”

“The design-to-code pipeline just collapsed. When agents can read your codebase, write to your Figma design system, and generate code from those designs in one loop — the distinction between design work and engineering work starts to blur. The Skills feature is forward-looking: it's essentially defining agent personas for different design contexts.”

“The thesis Luma is betting on: in 3 years, the atom of video production is the prompt-defined shot, not the filmed frame — and the person who controls the camera control schema controls the creative workflow. That's a real bet, not a vibe. What has to go right is that camera vocabulary (dolly, push, orbit, rack focus) becomes a stable abstraction that downstream tools — editing software, storyboard apps, social platforms — integrate against. What has to not happen is that OpenAI or Google ships this as a commodity feature in their general assistant, which is a non-trivial dependency. The second-order effect nobody is naming: if controllable camera paths stabilize as an API primitive, indie directors stop budgeting for B-roll entirely, which collapses a specific tier of stock footage and freelance videography. Luma is riding the trend line of model capability catching up to creative control — they're on time, not early, but the storyboard mode is a genuine attempt to move up the stack before commoditization hits.”

“For content creators who live in Figma but aren't engineers, this finally makes AI-assisted design feel native. Describing a layout and having the agent use my actual brand components — not generic boxes — is the thing I've been waiting for. Start with a non-production project until you understand how the agent behaves with your design system.”

“The camera controls are the real unlock here — specifying a slow push-in versus an orbital reveal produces outputs that feel authored, not just generated. Scene consistency across shots is genuinely better than the 1.0 era where characters would drift in appearance clip to clip, though it still wobbles on complex wardrobe details. The storyboard mode finally gives the tool an editing surface that maps to how a video creator actually thinks: in beats and cuts, not individual prompts. The fingerprint is still present in the motion curves — too smooth, too cinematic-by-default — but for creators who need a fast rough cut to pitch, this earns its place in the workflow.”

“The job-to-be-done shifts between features and the product hasn't resolved it: are you hiring this to generate a single polished clip, or to produce a short coherent film? Storyboard mode and single-clip generation serve different workflows and the onboarding doesn't commit to either — new users land in a text prompt box with no clear path to the storyboard mode unless they already know it exists. The completeness problem is real: you still need a separate tool for audio, voiceover, and final cut, so this lives perpetually in the 'one piece of the puzzle' category rather than replacing anything end-to-end. The camera controls are genuinely opinionated and well-scoped — that's a product decision I respect — but the storyboard mode needs two more iterations before a creator can throw away their current workflow and adopt this wholesale.”