From a design comment to a filed ticket.

Jarvis (getjarvis.eu), a screen-aware desktop AI assistant, files a Figma comment as a Linear ticket and posts to Slack. Open the Figma file, press Cmd+/ on macOS or Ctrl+/ on Windows, and ask for a ticket plus a channel update. It reads the comment thread on screen, so nothing has to be copied by hand. Open the Figma file, press the hotkey, and say "file this comment as a bug and tell the design channel." Jarvis reads the comment and surrounding frame context, creates a Linear issue with a descriptive title and a link back to the Figma node, then posts a short update to your chosen Slack channel with the ticket URL. It routes the steps across frontier models from Anthropic, OpenAI, and Google, and remembers your Linear team and Slack channel via persistent memory. Connectors authorize over OAuth, so credentials stay private. It runs on the free plan (40 requests/week), then Pro at $16/month. Jarvis previews the ticket and the Slack message before anything is created or sent.

This Figma-to-Linear-to-Slack chain is built for design-to-engineering handoff. Jarvis reads the specific Figma comment you reference — the feedback text and which frame or component it sits on — and turns it into a Linear issue: a clear title, the comment body as description, and a deep link back to the exact Figma node so engineers land on the right spot. It then writes a concise Slack update to the channel you name, pasting the Linear URL so the team sees that the feedback is now tracked. The whole sequence runs from one sentence in the floating bar, with the open Figma file as the screen-aware anchor.

Design teams route work predictably, and Jarvis captures that. The first run, name the Linear team that owns this product surface and the Slack channel where design updates go. Jarvis saves those as user-controlled memory, so future comments flow to the same team and channel automatically. You can change or clear these defaults from settings whenever the routing changes. Because Jarvis carries the Figma frame context into the Linear description and the ticket link into the Slack post, the resulting issue is specific — it names the screen and the requested change — rather than a vague "fix the design" stub that a triager would have to chase down.

Integrations