Design tokens are now a baseline skill
Design systems coverage keeps circling back to tokens as the link between design files and code — not a nice-to-have anymore.
designsystems.news
Find what matters in the design archive
UCD CoachPractice brief · Design systems
Published 23 August 2026 · Source dated 1 December 2025
Used for: Design-system tidy; Portfolio proof; Tool experiment. Practice brief for the gate you are in — not an industry digest dump.
Hype check: Adoption. Teams are using this — still check the source date (1 December 2025).
Saves the claim and source date (1 December 2025) on this device. No account.
More teams are treating W3C-format design tokens, not static style guides, as the actual source of truth between design and code. Penpot's native token support follows the open spec, while Figma's variables remain mostly locked to its own ecosystem.

Coach
open your Figma variables panel, then read the W3C Design Tokens spec's intro section, and write one sentence explaining the difference to yourself.
Source: designsystems.news ·
Coach is the forward habit — today's five, every morning. Surf is the rearward workbench on the same briefing corpus. Today's five is not restaged here.
Open today's five on UCD Coach
Daily email stays on Coach. Surf has no subscribe form.
More practice briefs on the same topic — not today's five from UCD Coach.
Design systems coverage keeps circling back to tokens as the link between design files and code — not a nice-to-have anymore.
designsystems.news
Design Systems News' ongoing coverage shows tokens (colour, spacing, type as data, not just styles) are now standard practice, with tools syncing them across Figma, Penpot and code.
designsystems.news
Token-based systems — colours, spacing, type as reusable variables rather than hardcoded values — have moved from 'nice to have' to baseline practice in design systems work. If your portfolio still hardcodes hex values, that's a gap worth closing.
designsystems.news