The rule. Treat Figma Make's default output as a sketch of somebody else's product: fidelity to yours starts when you wire the design system into a Make kit (the npm package, library variables and styles, and guidelines).
Why. Make kits exist so teams can build designs and prototypes "realistic to how your product looks and functions without having to add code and style context from scratch," and a kit carries three things: npm packages, variables and styles from published libraries, and guidelines that teach Make how to use them (Figma, n.d.-a). A design system package puts "fully interactive, production-ready components directly in prototypes," and Figma calls the guidelines "critical" for reliable output, recommending you let Make generate them and then review the result (Figma, n.d.-b). Config 2026 itself said little about Make and pushed from the other side instead: code layers, in closed beta, "bring working code into the Figma canvas as a new kind of layer" (Figma, 2026). The prototype-to-production gap is closing from both ends, which makes an unbranded Make build easier to mistake for the real thing.
Seen in the wild. Figma now lets any paid plan "publish private design system packages and use them in Figma Make," so a company's components reach the model without ever touching the public registry (Figma, n.d.-b).
Verified as of 2026-09-29 against current Figma Learn documentation.