Write the anti-patterns into the library guidelines, and mirror them in the repo instruction file. We measured the repo version: AGENTS.md, a +26.1 point lift on open-design-system-bench, 898 graded generations. Figma guidelines are the canvas copy of that move. Keep both short, and keep them the same.
Before 4 Nov, make one code layer from the repo you trust, if the beta has reached your paid plan. After that date, the same task spends credits.
Put the real prop names in the guidelines file until a code source is on your plan. Code sources are a closed beta. The list of props is not.
Move one live decision out of a side doc and onto a spec beside the frame. Design reads it. Engineering reads it. The agent reads whichever file you attached, so attach this one.
Publish the motion styles production already uses. Motion styles have been in open beta since 30 Sep. Leave the experiments in the file.
Who owns the list
Scale, govern, and ship still means a person owns it. On the design side, that person attaches the guidelines and the spec. On the engineering side, that person reviews the diff against the package the app installs. If those are two people, put both names on the list. A Q1 slide with no name is how you get a second button.
I checked the Figma release notes and the Config India 2026 help article on 18 Oct 2026. Plans, betas, and the 4 Nov credit window come from those pages. If your admin console disagrees, trust the console.