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 — Not a design tool: a file viewer, a stock library or a single-purpose converter in which nothing is laid out or drawn.
3 — A canvas or editor with templates, shapes, text and images; reusable components, shared styles and prototyping are basic or not described.
5 — Reusable components or styles shared across files, responsive or auto layout, and clickable prototypes or presentations linking screens.
8 — A design system managed in the tool: team libraries that update where they are used, variables or tokens for colour, type and spacing with modes or themes, component variants and properties, prototypes with transitions and conditional logic, and library changes published 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
The prototyping engine is the strong suit: screens linked by 18 transitions, timeline-based state animation, over 80 events and 40 actions, and variables that do real logic across screens — that is conditional-logic prototyping, not a clickable deck. But the captured pages say nothing about team libraries updating where used, tokens for colour, type and spacing, component variants, or versioned publishing, so the design-system half that engineering relies on goes undocumented. 1 2 3 4