Ask for range if you want it, but not without the rubric. Figma's November 4, 2026 workflow lab prompts its agent for three variations of a delivery-address button with 'surprise me with the other two,' the designer clicks through them and is happy with the omnisearch option, and the technical spec is written last to describe the changes. The pick is the one step with nothing written down. Before the prompt, write three lines per variation: what it must never do, what a failure costs the user, and the one data question the canvas cannot answer, which in Figma's own example is the share of orders that go to a repeat address. Score each code layer pass or fail with a severity as a comment beside it, and open the spec first so the agent's end-of-flow document is a diff against it. The rubric comes from grading thirty real outputs on gut feel and keeping the dimensions where failing costs something.
Not without the rubric. Three lines per variation before the prompt, the score beside each code layer, and the spec opened first. "Happy with" is not a record of a design decision.
The workflow step by step, the three lines, and the data question the canvas cannot answer are in Figma's Agent Made Three Prototypes From 'Surprise Me.' Kill the Brief. Write the Rubric First.. The extraction method is the Design Operating Model chapter The Rubric Is the Spec.
Last reviewed 2026-11-05 · 1 min read