AI UX DAILY
Thursday, September 17, 2026
4 stories · curated for designers
The stories
Today in AI Products
| via TLDR Design |
Figma's AI builds and publishes custom plugins from plain-language descriptions
Figma's AI agent now generates fully coded plugins from a text prompt — bulk-restyling icons, generating type ramps, flagging broken flows — and designers can publish them to the Figma Community.
| “ |
Write down your three most repetitive Figma chores and try generating a plugin for each one this week. — Designer's Takeaway |
| via TLDR Design |
Meta's Muse agent navigates websites by reading the accessibility tree, not the DOM
Meta launched Muse, a consumer agent that browses, fills forms, books travel, and makes payments. It reads pages via accessibility-tree snapshots, making semantic structure the primary signal for agent navigation.
| “ |
Audit your product's accessibility tree in a screen reader or browser DevTools to see what Muse-style agents would actually encounter on your screens. — Designer's Takeaway |
| Sep 16 |
Google Home now lets Claude, ChatGPT, and other agents control connected devices
Google launched early access to a Home MCP server. Any AI agent can now control smart home devices, review camera summaries, and act on home activity data via natural language, using the Model Context Protocol.
| “ |
Map which smart home actions users currently confirm manually and decide which ones need an explicit confirmation screen when an agent triggers them instead. — Designer's Takeaway |
| Sep 16 |
Figma opens Weave tool publishing to the Community
Designers can now build custom Weave tools and share them directly to the Figma Community, making AI-powered canvas tools available for anyone to install and run without leaving Figma Design.
| “ |
Browse the first wave of published Weave tools this week and note which workflow gaps they address — that gap list is your own plugin backlog. — Designer's Takeaway |
Today's Idea
Agents read your structure, not your visuals
Meta's Muse and Google Home MCP both act on semantic structure and accessibility data rather than what the screen looks like. Start treating your accessibility tree as a first-class design output, the same way you treat visual hierarchy.
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.