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 Frontend Engineer
Team-wide and cross-team libraries, shared styles for colour, text, grids and effects, and tokens and variables that generated components bind to are all documented, with design system theming and APIs gated to Enterprise. I found no public information on library change notes with versions, prototype conditional logic, or token export in a documented format for development, which is what I need to wire a design system into code. 7 9 2 2 6