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 24 August 2026 · Source dated 1 October 2025
Used for: Alpha assumption; Design-system tidy; Stakeholder brief; Portfolio proof; Tool experiment. Practice brief for the gate you are in — not an industry digest dump.
Hype check: Established. Treated as established practice. Source dated 1 October 2025.
Saves the claim and source date (1 October 2025) on this device. No account.
Design tokens — named values for colour, spacing, type — are the established backbone of keeping design systems consistent across Figma, Penpot and production code. Not new, but still the bit a lot of junior portfolios skip entirely.

Coach
Open a current Figma or Penpot file, pick three colours you've used more than once, and turn them into variables/tokens instead of hard-coded values.
Source: radical.design ·
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