Design, prototyping & design systems
How this is scored
The making itself: vector and layout tools, interactive prototypes, and the shared components, styles and tokens that keep a company's products and materials consistent — judged on what the feature and help pages document, not on showcase images.
0 — A single-purpose editor with no reusable components, no shared styles and no prototyping.
3 — Templates and basic shapes or layouts, with styles saved per file only and prototyping limited to linking screens.
5 — Reusable components and shared styles across files, responsive or auto layout, clickable prototypes with transitions, and team libraries that update where they are used.
8 — A design system managed in the tool: variables or tokens for colour, type and spacing with modes or themes, component variants and properties, prototypes with conditional logic, and library change notes with versions.
10 — The design system is a governed product: library releases versioned and reviewable, token export in a documented format for development, usage analytics per component, and accessibility checks such as contrast built into the editor.
The Product Designer
Prototypes behave like the end product — variables, expressions, conditional logic, interactive form fields, states and video are all documented — and the design system is managed rather than decorative: master components sync back to the library, color and font tokens import from JSON or a CDN and propagate to components, and WCAG contrast checks with color-blindness simulation sit in the tool. What holds it below the top band is system governance: spacing and padding tokens are only planned, and we found no public information on token modes or themes, component variants as a named capability, or versioned library releases with change notes. 1 2 5 6 8 9