AI UX WEEKLY
Week of August 24, 2026
5 stories · curated for designers
Whether it's an agent's first screen, a Figma spacing token, or an AI that scans your file for accessibility issues, the concrete wins this week all came from closing the gap between design intent and what actually ships.
The stories
This Week in AI Products
| Aug 21 |
Five principles for designing an agent's first five minutes
Microsoft Design published research from a sales-outreach agent study. Five findings: show value before setup, break config into small steps, signal progress, use defaults over upfront questions, and clarify capabilities early.
| “ |
Audit your agent's onboarding and remove any configuration step that appears before the user sees one useful output. — Designer's Takeaway |
| Aug 21 |
Stark becomes the first accessibility connector in Claude's directory
Stark's Claude connector lets you scan Figma files, URLs, source code, and Storybook libraries for accessibility violations inside a Claude conversation, then remediate issues and auto-create Stark projects without leaving the chat.
| “ |
Run an accessibility scan on your current Figma file through the Stark connector before your next dev handoff. — Designer's Takeaway |
| Aug 21 |
Auto layout gets two new spacing modes: Around and Evenly
Figma auto spacing now offers three options: Between (existing default), Around, and Evenly. The new modes map directly to CSS justify-content values, closing a long gap between Figma layouts and production CSS.
| “ |
Update your component library to use Around or Evenly wherever your dev team currently patches auto layout gaps manually in code. — Designer's Takeaway |
| Aug 21 |
NN/g study: users rate AI-generated images on par with stock photos
NN/g tested AI-generated images against stock photography without telling participants which was which. Perception scores were statistically equivalent, so AI images carry no built-in credibility penalty when users don't know the source.
| “ |
Use AI-generated images in low-stakes UI contexts where stock licensing is a bottleneck, and document the sourcing decision in your team's responsible-use policy. — Designer's Takeaway |
| Aug 17 |
GitHub argues canvas interfaces make agentic work visible and steerable where chat loses it in the scroll
GitHub's post makes the case that chat works for stating intent, but agentic work needs a canvas where state, decisions, and progress stay visible and can be redirected without re-prompting from scratch.
| “ |
Prototype a canvas view alongside the chat view for any multi-step agentic feature and test whether users can recover mid-task without starting over. — Designer's Takeaway |
Steal this week
Stark + Claude's Accessibility scanning inside a Claude conversation
Embedding remediation at the point of AI conversation cuts the round-trip between spotting and fixing accessibility issues before handoff.
Pattern deep-dive
Guided Learning
Agent onboarding, canvas visibility, and accessibility tooling all ask the same thing: show value before asking users to configure anything.
Use it when: your product asks users to set up before they see a result
Stop shipping AI slop
Turn your design into Claude skills
Drop a screenshot. See which of the 38 patterns you are missing and take them away as Claude Code skills. Free, no signup for the first audit.