CloudCodeTree LogoCloudCodeTree
AI NewsTutorialsAbout
CloudCodeTree Logo
CloudCodeTree
  • AI News
  • Tutorials
  • About
← Back to AI News
Stop Reprompting the Whole Component: Figma Make Now Has a Properties Panel and In-Context Annotations

Stop Reprompting the Whole Component: Figma Make Now Has a Properties Panel and In-Context Annotations

Chris Harper

2 min read

Aug 17, 2026 · 20:05 UTC

AI
Workflow
Design
Design-to-Code

Figma Make's new properties panel brings familiar Figma Design controls into the AI editor; in-context annotations let you mark exactly what the agent should change — no more reprompting the whole component.

When you iterate on a design in Figma Make, the default workflow is one big prompt: describe what you want and hope the AI scopes itself correctly. Two new tools shipped in late July change that.

Properties panel. The same spacing, typography, layout, and color controls from Figma Design are now live in the Make editor. Select any element and adjust it directly — Make stages the change in the prompt box for you to review before it lands in the underlying code. For pure visual adjustments, this beats a natural-language prompt every time.

In-context annotations. For changes that go beyond visual properties — an animation, a hover interaction, a conditional render — select "Annotate for agent" in the toolbar and mark the exact area on canvas. Write your instruction directly on the design. The agent sees precisely what you're pointing at without you having to describe the surrounding layout.

The workflow in practice:

  1. Generate or open a component in Figma Make.
  2. Fix visual properties (padding, font size, color) directly in the properties panel.
  3. For behavior or animation changes, annotate the specific element — don't reprompt the full component.
  4. Review each staged change before committing — Make updates the underlying React/Next.js code automatically.
  5. Export or push to your repo when the component is right.

The practical gain: AI edits are scoped to exactly what you intended. Annotating one button's hover state on a complex dashboard is far less disruptive than reprompting the whole layout and reviewing a diff full of unrelated changes. Both tools work whether you're starting from scratch or editing existing Make-connected code.

Sources: A Properties Panel and Annotations, Now in Figma Make — Figma Blog · Figma Release Notes — Releasebot