Design arguments don’t resolve, so there are no predictions here — we track what the archive says instead.
The brief · 05–11 Oct 2026
Anthropic's design team works in code from week one, while Orosz could not find one company where designers or PMs ship production code. B2B products get there first. With a design system and a knowledge base in place, a PRD is enough to start, and an HTML preview close to the real screen gets the design approved. Consumer products are a long way from designers raising PRs. There, a strong base can open UI-level changes to PMs and designers, but engineering makes the final call to ship.
What the archive shows
297 signals · 21 weeks
Read backwards, not forwards. No predictions here — what follows already happened.
Discovery has gone quiet
22 articles across 7 weeks, then nothing for 8 weeks. Last seen 2026 week 33.
NN/G's study of Claude power users found they put more effort into context libraries than prompts, and often could not find the files Claude had written for them. One participant kept over 2,700 context files; another found a governing file he did not know existed.
Why it matters
One participant's podcast design guidelines leaked into a book-tracking app. For teams handing agents a design system, where those files sit decides which project they reach, so folder layout belongs in design system governance.
“Almost nobody in our study typed directly into their context files.”
— Nielsen Norman Group
Pattern
Atlassian published DESIGN.md in June and a UX.md was proposed in July, both files for agents to read. NN/G's study documents how such files go stale and get lost once people use them daily.
Inboxes and dashboards only answer what agents are doing right now, Wroblewski argues, and steering many agents needs views built for the task. In Intent, agents draw architecture diagrams before spending tokens, post before-and-after screenshots of UI changes, and read the same design-system note the user keeps open.
Why it matters
The review artefact changes. A designer judging agent work from side-by-side screenshots does not open the code, so that screenshot note becomes the approval record and needs the naming and versioning a design file gets.
“Agents can take before and after screenshots of their UI changes and place them side by side in a note letting you judge results without reading any code.”
— Luke Wroblewski
Pattern
Intent appeared on 1 October, when its sites bound agents to the stylesheet through an AGENTS.md file. Here the design system becomes a note that people and agents read together, away from Figma.
AI is not lowering intelligence, Polonski argues; it cuts how much of it people practise, so unused skills fade without anyone choosing to drop them. His opening example is the old landline number most people over thirty still know by heart.
Why it matters
The loss sits in skills nobody tracks. A team can watch output speed rise while the judgement behind its design reviews weakens, and it shows only when someone has to work without the tool.
