All times UTC
Microsoft has made the GitHub Copilot harness generally available inside Copilot Studio, letting it orchestrate models, tools, memory and MCP servers together. It's a sign that MCP is becoming standard plumbing for agent workflows, not just a dev-tool novelty.
facebook.com (opens in a new tab)
Your move
spend 20 minutes this week reading a plain-English MCP explainer so you can follow the conversation when it comes up at work.
UK design job listings and industry coverage are increasingly expecting junior candidates to show comfort with AI-assisted workflows, not just tool proficiency. It's showing up as a baseline expectation rather than a nice-to-have.
designweek.co.uk (opens in a new tab)
Your move
add one portfolio case study note describing a specific point where you used an AI tool in your process, including what you changed after.
With so much noise about AI speeding up design, lightweight usability testing remains one of the most reliable ways to catch real problems early. It's an established method, not a new trick, and it still beats guessing.
nngroup.com (opens in a new tab)
Your move
run one 5-user or even 2-user guerrilla test on your current project this week and write down what broke.
As AI agents start reading design systems directly through MCP-style integrations, teams are cleaning up token naming and documentation so agents (and humans) don't misread intent. It's a quieter but real shift in design-system hygiene.
designsystems.news (opens in a new tab)
Your move
pick one component in your Figma or Penpot library and rename its tokens as if an agent (not a person) had to understand them cold.
Figma now ships a canvas agent that works alongside you inside a file, plus an MCP server that lets external agents read and write Figma designs. Both are shipped features you can use today, not a roadmap promise.
figma.com (opens in a new tab)
Your move
open a spare Figma file this week and try the built-in canvas agent on one small edit before touching the MCP server.
