Agent skills spread across design and chat tools

Agent capabilities go mainstream

Figma made the clearest statement yet that its agent platform is a first-class surface. The company added skill discovery, creation, and sharing for the Figma agent, including Community discovery and custom skill authoring — a meaningful step beyond the curated skills that shipped with the agent's launch. For teams building repeatable workflows inside Figma, the ability to find and publish skills through the Community ecosystem mirrors the plugin marketplace model that helped Figma's integrations thrive.

Even more significant for developers is the Figma MCP server now running Weave tools from Codex, Claude, or Cursor. This bridges Figma's automation layer directly into the three most-used AI coding environments. A developer in Cursor can now trigger a Weave tool that updates design tokens or regenerates prototypes without leaving their editor. The combination of custom skills plus MCP access means the agent's capabilities are no longer confined to the Figma browser — they're accessible wherever AI-assisted workflows happen.

Supporting this expansion, Code Connect 1.5.3 shipped a --unique flag for figma connect preview that de-duplicates outputs, plus an InstanceHandle that now exposes the Figma node ID matching the Plugin API's SceneNode.id. That node ID exposure matters for anyone building tooling that needs to correlate design instances with their underlying scene graph positions.

Typography goes responsive

Figma also added text wrap options with two new settings: Balance and Pretty. Both can be applied to a text layer, a text style, or an individual paragraph. Balance evens out line lengths for a tidier look across breakpoints, while Pretty enables things like hanging punctuation and better paragraph breaks. For design systems teams, the ability to set these at the text style level means responsiveness can be standardized across every component that uses that style — a small change with outsized impact on how consistently text reflows between mobile and desktop frames.

Planning gets clearer ownership

Linear upgraded initiatives with team leader assignment and private visibility. Assigning a leading team to an initiative now makes responsibility explicit — useful for strategy work that spans multiple squads. Initiatives led by private teams become visible only to members, creating a safe space for confidential roadmap planning that shouldn't leak to the broader org. Linear also extended its MCP server to support Okta-managed employee access for Enterprise workspaces with SAML, so permissions carry over without per-user sign-in.

SDK polish across the board

The Notion JS SDK shipped three releases worth noting. v5.25.0 added a filter_properties parameter to page creation and update calls, matching the existing behavior on pages.retrieve() — a performance win for applications that create pages with dozens of properties but only need a few in the response. v5.25.1 tightened isFullDataSource and isFullDatabase type guards to also require the title field, preventing incorrect narrowing of partial objects. And v5.25.2 added a does_not_equal condition to verification property filters, rounding out the SDK's query capabilities for compliance-style workflows.

Elsewhere, Slack 26.08.20 fixed HDR video playback on iOS, and Notion v1.7.328 was a routine bug-fix release. The Discord August 11 changelog rounded out the week's quieter updates.

The through-line this week is boundaries coming down: Figma's agent skills now reach into coding tools, Linear's initiatives can span public and private spaces, and Notion's SDK keeps closing gaps between what the API accepts and what power users expect.