Figma’s October 6 release notes say the agent can read Markdown guidelines attached to a design library, including rules, best practices, and antipatterns, whenever a prompt uses that library. The mechanism is not simply a larger prompt: guidance is attached to a reusable library and enters the agent’s context through that selection.
The thesis is: design-library guidance is becoming executable context for an agent, rather than documentation left for a human to interpret. The mechanism is: Figma lets teams upload Markdown rules, best practices, and antipatterns to a design library; the agent reads them when that library is enabled in a prompt. Why now: Figma says the agent has exited beta and pairs this with file search, broader file attachment, node pasting, and live visibility into teammates’ agents. The first implication is: Teams can encode design constraints in a reusable context source that follows agent work across prompts.
The release notes also report improved latency and access to files across Figma, FigJam, and Figma Slides. Those are concrete product claims, not evidence of measured quality gains, adoption, or reduced review effort. The evidence boundary is: The public release notes describe capabilities and availability, but provide no independent evaluation, usage data, or detailed paid-plan entitlements. The first watch condition is: Whether teams can govern and maintain library guidelines well enough that the agent applies them consistently across real design tasks. This begins a distinct analytical record because no prior New Runtime record was supplied for this specific release or its library-guideline mechanism.