Figma AI

Figma AI AI

Figma AI AI

Figma AI AI

Figma AI AI

Figma AI AI

Figma AI AI

Figma AI AI

Figma AI AI

Figma AI AI

Figma AI AI

I think the biggest mistake beginners make with vibe coding is jumping directly into:

I think the biggest mistake beginners make with vibe coding is jumping directly into: “build me this app” That’s exactly what I did at the start. The result? Endless loops of errors, generic designs, broken architecture, AI changing random files, and eventually a project nobody really understands anymore. After months of using Cursor/Copilot/ChatGPT, I realized AI coding works MUCH better when you slow down before coding. What helped me most: First: clarify the idea in your own head. Discuss the idea with ChatGPT/Claude BEFORE touching code. Ask the LLM to ask YOU questions until the idea becomes clear. Create a small PRD before building anything. If possible, design rough UI ideas first (Figma/Dribbble helped me a lot). Big lesson: AI is not a replacement for product thinking. Another huge thing: Create rules for your IDE agent. For example: don’t touch files without asking, comment functions properly, explain WHY changes are made, ask before refactoring, never rename important files automatically. Also: KEEP A CHANGELOG. Seriously. After long sessions, AI starts forgetting context or creating confusing logic. A changelog helps both you and the AI understand what already changed. I also keep small .md files for: project memory, security audits, completed fixes, architecture notes. This becomes super useful when switching chats, IDEs, or models later. And one more thing nobody told me: When the chat starts feeling slow, messy, or confused… it’s usually context overload. Starting a fresh chat with organized context often gives WAY better results than continuing a broken conversation forever. AI coding became much easier once I stopped treating AI like magic and started treating it like a junior teammate that needs structure. submitted by /u/Embarrassed_Leg_6330 [link] [comments]

Am I the only one who feels like AI got us 90% of the way there and then just stopped?

I've been using Claude heavily for the past year now and it's genuinely changed how I work. I'm generating dashboards, reports, interactive tools, documents, mockups, things that would have taken me DAYS in Figma or PowerPoint and I wouldn't have made anything half as good, and all are built in minutes now and they actually look better. But there's this one thing that happens every single time that makes me feel like I'm losing my mind. I generate something. It's beautiful. It works exactly the way I wanted. And then I need to share it with someone. And I just... can't. Not really... If I send the artifact link, it doesn't always render properly, and it's not easy to continue working with it, and then you have the org/non-org restrictions. Half the people I work with don't use Claude. My clients definitely don't. So I download the HTML file, attach it to a message, they download it, open it locally (that's if they know what to do with an HTML file). So I end up taking screenshots, or I screen record it like an animal. I had a moment last week where I generated this genuinely impressive interactive report (charts, filters, the whole thing) and my only real option to share it was to send a file called something like claude-artifact-download.html to a client. I wanted to disappear. It's not just HTML either. I've been using markdown files constantly because they're so much faster and cheaper to generate for things that don't need to be fancy. But try opening a .md file on someone else's machine without a dev environment and good luck. It renders as raw text with asterisks everywhere. Meanwhile I can share a Google Doc with one click and anyone on the planet can open it in two seconds! I feel like we have these incredibly powerful creation tools and then the moment something needs to leave the AI interface it's 2005 again. Does anyone have a workflow that actually solves this? Or am I just missing something obvious? Genuinely curious how other people are handling this because every workaround I've found feels like a hack. submitted by /u/HummusAlltheWay [link] [comments]

HTML artifacts are starting to replace Google Docs on my team (But it's missing comments)

Been using Claude to convert long-form work docs (spike readouts, architecture notes, meeting prep) into self-contained interactive HTML pages: inline SVG diagrams, sticky TOC, collapsible sections, tabbed comparisons. Publish to an artifact host, share a URL. The output is genuinely better than the equivalent Google Doc for dense technical content. But there's a glaring gap: no commenting, no suggesting edits, no inline review. Google Docs has 20 years of polish on highlight-and-comment + suggesting mode. Figma nailed comment pins on a canvas. GitHub has line-level PR review. None of those primitives have ported over to the "AI generates a static HTML artifact you share" workflow yet, partly because the artifact renders inside a sandboxed iframe, so the host platform can't just hook selection events the way Docs does on its own DOM. Feels like a real paradigm shift in how docs get made, with a real gap in how they get reviewed. What are people doing? Falling back to Slack threads on the URL? Has anyone actually shipped good commenting on iframe-isolated AI artifacts? submitted by /u/Comprehensive-Ad1819 [link] [comments]

the weirdest thing that worked for me building with claude: i drew coordinates directly onto my template images, and claude can see everything

building a zine-making app (90s/y2k aesthetic, hot pink, chunky outlines, all that). the templates are real designed layouts (y2k chat bubbles, riot grrrl flyer collages, myspace-style pages). each one has multiple zones where the user can drop in their own photos and text. the obvious approach was building every template in code, programmatically defining where the photo slots go. which means every template's look is constrained by what i can build by hand. boring, and the designs would all end up looking like the same grid in different colors. just like other generic apps. what i did instead: designed the templates in figma (some generated with image AI, then cleaned up), exported as flat PNGs, then opened them up and literally drew colored rectangles on top in a separate layer. for example: red for photo slots, blue for text. fed both the design and the annotation image to claude. it extracted the coordinates, generated the editable area definitions, wired up the tap targets. an afternoon of work for what would have been weeks of building a custom layout engine by hand. and the kicker: i can add a new template now by designing it and drawing the boxes. no code change. that's the entire design-tool system for the app and it came from a workaround. the broader pattern i've gotten religion on from this project, and everyone asks me how i design my apps, so here it is: i do the design thinking on paper first, before claude sees anything. i sketch screens by hand. i pick the full color palette before writing a single line. i decide the type hierarchy. i screenshot apps i like and annotate the specific things i want to steal from each one. then i hand claude the constraints and ask for implementation. going the other way like "design me an app, make it look 90s" is the path where you spend three days nudging it toward something that still feels generic. claude is incredible at implementing a specific vision faithfully. it's much weaker at having the vision for you in the first place. once i internalized that the design work was my job and the implementation was its job, my output quality jumped. the unglamorous stuff that also mattered: describing visual problems in terms of weight, hierarchy, and rhythm instead of "this looks off, make it better" pasting in hex codes i picked from real reference photos instead of saying "warm pink" so being specific about which app's spacing i was trying to mimic, not just naming the vibe. the app is zinecore if anyone wants to see what came out of it but the paper-first thing is the part that's actually transferable. https://apps.apple.com/tr/app/zinecore/id6763522374 submitted by /u/ezgar6 [link] [comments]

We’re hosting the biggest Claude Code Prompt-a-thon at the AI x Marketing Summit in SF.

We’re hosting the biggest Claude Code Prompt-a-thon at the AI x Marketing Summit in SF on May 28–29. For 36 hours, you’ll actually build with AI: • Claude Code • Humanic • n8n • MCPs • Figma Make • AI workflows for SEO, ads, lifecycle, outbound, content, and growth You’ll work alongside marketers and operators building real-world AI systems — not just talking about them. The summit includes hands-on workshops, promptathons, networking with AI-native marketers, and sessions from founders, CMOs, and operators shaping the future of marketing. Bring your team to SF. Compete, build, and walk away with top-tier tech. The full agenda is now live — grab your ticket now. Learn more: https://aixmarketingsummit.com/ submitted by /u/Brilliant_Sector_427 [link] [comments]

Thought I’d have to get rich or become a programmer to build my dream tool. 47 days later, I’m launching it thanks to Claude - here’s what I learned

I’m a former non-technical PM that now does startup consulting. Figured out a pretty great workflow as someone who can’t code at all, and wanted to share it in the hopes that it helps someone else on the fence about exploring what’s possible. I’ll share my tips first, and then a little bit about what I built at the end! While I’m not a coder, I’ve worked with engineers and creative teams my entire career, so I’m familiar with the time-honored process of writing strong stories and keeping track of scope. It’s been a while since I shipped something, but I have 11 software launches under my belt. Now it’s time to make it a dozen! I approached the relationship as me as the PM, and Claude as my super fast, over eager engineer who needed some coaching. Takeaways: My biggest tips from this process: Sky is the limit – if you can describe it. You don’t need to be a coder to build now; you don’t have to understand the ins and outs of every technical decision; but you DO have to have intent, a vision, and a reasonable willingness to understand how the parts relate to the whole. Claude needs to have as little space as possible in which to bounce around. What I mean by that is what I started hitting at with #1 – if you have a clear vision of what you want to build down to the ins and outs of specific features, it will be dramatically easier to build. On Day 1 of development, I had a basic list-style PM tool built after 3 hours. That wasn’t me being a wizard at prompting – it was leaning on my 16 years of domain knowledge and knowing exactly how to describe what I wanted. And that brings me to my next tip… You must learn to reign Claude in, and catch it when it starts to bounce around. There were several instances, particularly with respect to visual bugs (fades, visual location, tooltips, etc.), where Claude just could not understand what I was asking. I developed a rule: Claude gets two chances to fix it, and then if that doesn’t work, we roll back and change approach, usually doing a diagnostic with logs. This always ended up ultimately solving the problem. Claude needs specifics – and if you can’t provide them, you will eventually hit a wall. Having another contributor who could give advice was immensely valuable. A good friend of mine who is an SWE helped me out at a top level. They wanted to learn more about Claude Code and what was possible, and I needed help understanding specific architectural implications of what was being done. It ended up being great – the constraints (limited time on their end) helped us use the tool powerfully to solve key issues, rather than having to do it by hand. My friend was also the first to help me ask better questions of what Claude was doing, and developing that instinct to go from “it just works, good enough” to asking “Explain in detail how this affects feature X” was critical. Use Claude Desktop App for planning and strategy, and Claude Code to execute. You hear of this process a lot, but specifically what I did was have a core chat session in “Chat Claude” where I designed features and talked it through, got it to challenge ideas, and iterate. Then, when I was happy with a feature design, I got Chat Claude to write a feature spec with the explicit instruction that it should be a document Claude Code could read and then implement. This process ended up working enormously well; features that were very complex ended up being quick builds once I handed off to Claude Code, and I needed less time for back-and-forth implementation guessing because it had a “source of truth” to operate from. The exact workflow was: 1) I tell Chat Claude what I want to build in a core chat session that’s top-level strategy and planning, 2) we iterate back and forth, and then 3) it summarizes what we did and then builds a “spec” document that I then 4) hand over to Claude Code, and tell it to read the spec, ask questions, and propose a plan before building, and then we’re off to the races! The velocity can be mind-bending. I vividly recall my first week building – I was so mentally exhausted! It was hard to wrap my head around going from “This has been in my head for 8 years” to “It’s now being built before my eyes.” I do startup consulting, and this has changed my perspective on how these tools get used – we can accomplish a lot this way, yes, but the other side of that is we may be creating a loop of “hyperproductivity” where instead of freeing up our time from tools like Claude, we’re just filling that additional time with more work instead. Gotta be careful or we’ll just create more work for ourselves instead of gaining time back. Claude was most vicious about human decisions it couldn’t qualify. For example, when I was coming up with a name, everything it came up with was taken or bad. It just couldn’t nail the vibe. 30 minutes the old fashioned way (using the Thesaurus, referencing books I’ve read recently) got me a unique name – and Claude hated it. Claude also hated when that contr

Why I'm enjoying Claude Design as a PM (not for taste, for workflow)

I'm a PM at a small company, we work on apps and web products with a few million users. Our engineering is deep into Claude Code, and I personally lean on Claude Artifacts / Cursor / Gemini almost daily to generate prototypes — mostly so designers and devs can see what I'm proposing instead of reading a wall of text in a PRD. For a long time I had four persistent pain points: No real collaboration. Every round I'd export HTML, we'd meet, discuss, I'd go back to the AI to iterate. I'd end up with 10+ HTML versions floating around. Huge time sink. No way to plug in our design system. (Maybe a skill issue — I haven't gone deep on Pencil or Stitch.) My demos looked ugly enough that our designer would roast them. I wanted prototypes that actually matched our product's visual language. No page-by-page view. Designers and devs had to click through the demo to figure out how many screens there were and how they connected. My designer recently started asking PMs to screenshot every page of a web demo and annotate elements + navigation logic — which honestly felt like a step backward. No fine-grained tweaking. For small changes — copy, a module's proportion, the style of one element — I didn't want to re-prompt and wait for a full regeneration every time. Then I tried Claude Design this week, and it pretty much addressed all four: Org-scoped sharing works. Designers and devs can open the same design and see changes live. No more HTML file graveyard. Design system import is built in. (Though I burned through my entire weekly limit just setting it up 🥲 — actual results next week.) Pages render on a canvas like Figma frames — titled, interactive, and the full flow is visible at a glance. Way easier for the team to grasp the logic without clicking through. The sliders / custom knobs are the real unlock for me. For a lottery page I was prototyping, Claude gave me a control to swap between a spinning wheel, gachapon, and card-draw — all interactive, no re-prompting. This is the thing I've been wanting for a year. So — pretty happy with it as a tool. It obviously hasn't improved my design taste; that's still on me. And the weekly limit is real, plan accordingly. Curious what workflows other PMs / non-designers have landed on for collaborating with designers and devs via AI. Anything I should be trying alongside this? submitted by /u/InfiniteJX [link] [comments]

I created awesome-claude-design using Claude code: DESIGN.md prompts by aesthetic families for Claude Design

Claude Design launched 48 hours ago, and everyone’s cloning the same 60–70 brand DESIGN .md files from a single catalog. I wanted something that matches how designers actually pick: by visual family, not industry. So I put together awesome-claude-design, a meta-resource for Claude Design that groups DESIGN .md files by aesthetic family (editorial minimalism, terminal-core, warm editorial, data-dense pro, cinematic dark, playful color, glass/soft-futurism, neon brutalist, cult/indie), plus remix recipes, prompt packs with full I/O examples, and an anti-slop kit pulled from Anthropic’s frontend aesthetics cookbook. You’ll also find: A launch-week timeline (Opus 4.7 + Claude Design, Figma’s 4.26% close, Reddit threads, X signal) Official Anthropic resources (launch post, claude .ai/design, prompt library, cookbooks) Video teardowns, community hype and pushback, and related OSS projects like SuperDesign and Claude skills repos. Repo: https://github.com/rohitg00/awesome-claude-design This post and the repo were created with Claude for the Claude community, using Claude Design and Claude Code as the primary tools. Curious what other Claude power users want added next: more DESIGN.md families, deeper workflows, or tighter SkillKit integrations? Built end‑to‑end with Claude (Claude Design + Claude Code) for the r/ClaudeAI community. submitted by /u/SeveralSeat2176 [link] [comments]

Top 10 Open Source OpenClaw, Codex, Claude Skills from 1st -15th April

Found some open source Claude skills, some of them are pretty decent to use: 1. cook-the-blog: Give it a company name, get back a full case study in MDX. Does the research, makes the cover image, pushes it to your repo. 2. yc-intent-radar-skill: Pulls fresh YC job listings every day without repeats. Handy if you sell to YC founders. 3. position-me: Drop a website URL, get a teardown on SEO, copy, and UX. Reads like a real audit. 4. humanizer: Strips AI writing tells from your text and even matches your own writing voice if you paste a sample. 5. stop-slop: Cleans AI-sounding stuff out of your writing. No em dashes, no rhetorical questions, no "it's not X, it's Y". 6. meta-ads-skill: Lets Claude run your Meta Ads account. Create campaigns, set targeting, pull insights, all from chat. 7. svg-animations: Helps you make clean animated SVGs. Loading spinners, path draws, morphing shapes, that kind of thing. 8. google-trends-api-skills: Pulls live Google Trends data so you can pick keywords that people actually search. 9. blog-cover-image-cli: Makes blog thumbnails and article headers from a prompt. Skip the Figma step. 10. luma-attendees-scraper: A browser script that exports the attendee list from any Luma event to a CSV. Links to all in comment 👇 submitted by /u/Sam_Tech1 [link] [comments]

An old designer’s perspective on claude design.

I started designing websites in 1999, back when there was no figma, no component libraries, it was just you, a bunch of code and a variety of hacks to make Adobe tools made for print work for the web. Over the past two decades i’ve worked in internal teams for big corporates, at large agencies, and now head an agency of my own. Along the way the field has changed, matured, to an incredible degree: design systems, ux standards, atomic design principles have formalized design, codified it into rules and patterns. When i see claude code or google stitch i too see that it’s initial output is slop. That the high definition nature of the output hides how generic and insubstantial it really is. But thats not the point. The point is that we have turned the bulk of design work into pattern reproduction. I’m not talking about the part where we understand users’ needs, or wrangle with conflicting business requirements. I’m talking about the impopular truth that from an economic perspective the vast majority of ux and visual design is maintaining design systems, cobbling together functionality based on pre-existing functionality with very little variation. Small, often inconsequential variations on color palettes or margins. Nobody wants to say this on linkedin or at a conference, but as an industry, only 5% of us are actually developimg brands from scratch or shifting the product design paradigm. The rest are just reading tickets and assembling components together. And the thing about components, atomic design, and patterns, is: it’s structured, logical, formalized, repetitive. Consistency and adherence are the point. It was designed to be automated. It’s simply training data waiting for AI to come along, and now it’s here. The fact that it doesn’t look like much right now doesn’t negate the fact that it is going to be very, very good at it. Everyone who works on a big product team knows that 90% of the work is patterns and systems. Will there be work for designers next to AI? Sure, for 10% of the current workforce - the ones who were doing the client/stakeholder wrangling bit anyway. But if you’re in the other 90% it might as well be as if design as a discipline has ceased to exist. submitted by /u/undeadcrayon [link] [comments]

Claude Design just launched and Figma dropped 4.26% in a single day, we are witnessing history in real time

I genuinely cannot believe what I'm watching unfold today Anthropic dropped Claude Design this morning , a tool that lets anyone describe what they want and get back a full website, landing page, or presentation. No design skills needed and No Figma subscription. Just... talk to it And the market reacted instantly. Figma stock is down $0.86 (4.26%) today alone. Adobe, Wix, GoDaddy all bled too. Anthropic's own CPO literally resigned from Figma's board three days ago. The writing was on the wall and now it's on the landing page Claude just generated for you. What's making my brain short circuit is the full pipeline this unlocks right now, today. You describe your UI in Claude Design, animate it in Magic Hour, turn it into a motion video with Kling, and voice it over in any language with ElevenLabs. That's an entire creative agency workflow built from prompts by one person in an afternoon. I'm trying to stay grounded here because Figma isn't going anywhere overnight , they own something like 80-90% of the UI/UX market and have years of professional tooling that pros genuinely love but the entry point to design just got demolished. The question clients are going to start asking is "wait, why can't we just describe this to Claude?" and that question is going to be really hard to answer. I've been following AI closely for a while now and this is the first announcement where I felt something shift. Slightly terrified and extremely excited, completely unable to go back to sleep. How is everyone else feeling right now? submitted by /u/Future_Language76833 [link] [comments]

Top 10 Open Source Claude Skills from 1st -15th April

Found some open source Claude skills, some of them are pretty decent to use: 1. cook-the-blog: Give it a company name, get back a full case study in MDX. Does the research, makes the cover image, pushes it to your repo. 2. yc-intent-radar-skill: Pulls fresh YC job listings every day without repeats. Handy if you sell to YC founders. 3. position-me: Drop a website URL, get a teardown on SEO, copy, and UX. Reads like a real audit. 4. humanizer: Strips AI writing tells from your text and even matches your own writing voice if you paste a sample. 5. stop-slop: Cleans AI-sounding stuff out of your writing. No em dashes, no rhetorical questions, no "it's not X, it's Y". 6. meta-ads-skill: Lets Claude run your Meta Ads account. Create campaigns, set targeting, pull insights, all from chat. 7. svg-animations: Helps you make clean animated SVGs. Loading spinners, path draws, morphing shapes, that kind of thing. 8. google-trends-api-skills: Pulls live Google Trends data so you can pick keywords that people actually search. 9. blog-cover-image-cli: Makes blog thumbnails and article headers from a prompt. Skip the Figma step. 10. luma-attendees-scraper: A browser script that exports the attendee list from any Luma event to a CSV. Links to all in comment 👇 submitted by /u/Sam_Tech1 [link] [comments]

I built a Claude Code plugin that extracts any website's full design system

Just type /extract-design https://stripe.com in Claude Code and it pulls the entire design language — colors, fonts, spacing, shadows, components, everything. The main output is a markdown file specifically structured for Claude to understand. So you can extract a site's design, then tell Claude "build me a landing page using this design system" and it actually nails it because it has the exact tokens, scales, and component patterns. It also generates a Tailwind config, shadcn/ui theme, React theme, Figma variables, CSS variables, and a visual HTML preview — all from one command. Other things it does: designlang diff stripe.com vercel.com — compare two sites --depth 5 — crawl multiple pages for a site-wide system --screenshots — captures PNGs of buttons, cards, nav --dark — extracts dark mode too designlang history — track design changes over time Works as an npx tool too: npx designlang https://stripe.com GitHub: https://github.com/Manavarya09/design-extract One command, 8 output files: AI-optimized markdown (feed it to ChatGPT/Claude and it recreates the design) Tailwind config, CSS variables, React theme, shadcn/ui theme Visual HTML preview you can open in your browser Figma Variables JSON for designer handoff W3C design tokens submitted by /u/Cheap_Brother1905 [link] [comments]

Genuinely curious if there are AI Wireframing tools already available ...

I had this through for a while, and I wonder if there's any free product like this already... https://claude.ai/public/artifacts/56801a7c-c173-4cf8-a4e1-a0f5175d1858 Wireframing tool for prototyping apps... As designer, after spending some time trying to vibe code / code an app from scratch, I felt the new approach of going from "needs" directly into "code prototypes" helps me to get something working very quickly, but iterating from that prototype is painful. In my workflow, I wish to be able to define the bird-eye view of an end-to-end product Journey first, before spending more time / tokens on visuals like what we have on Figma / Google Stitch / Lovable, and so on. I wonder is there currently any AI lofi-wireframing tools available, that we could simply clarify on the end-to-end UX flow first? best is that once the scope is clear, I could just share a design token library, then it will be able to hand over to agent to build. Ideally workflow: 1. Conversation to create a Product Requirement 2. Enough context -> creates a mini-wireframe like this 3. Highlight / select / and chat through the end-to-end requirement in black and white 4. Clarify on the use-case and edge cases first. 5. After it is done, take it forward to screen design ( you can have 5 visual variation of the same Home Screen but please keep the agreed upon AI as-is and don't change it ) 6. Generate coded prototype and so on ... Why: Mini-wireframe like these felt faster, likely to burn significantly less tokens to drive the conversation before getting into UI. submitted by /u/Jealous_Incident7978 [link] [comments]

I built a Mac dictation app that injects voice + screenshots + clipboard straight into Claude Code mid-sentence

Hey r/ClaudeAI 👋 I'm Marek, and I've been building a Mac dictation app called Spoke. There are a lot of dictation apps out there and I'm not going to pretend mine is the right one for everyone — but if you do a lot of coding, live in Claude Code, and like tools you can shape to your workflow, I think you'll find this interesting. Short video of the Claude Code part below. The post explains the rest. The basic idea Spoke is built around flows. A flow is a pipeline of composable steps that run on your audio — transcribe, AI-process, inject somewhere. The simplest flow is "transcribe → inject text at cursor" (i.e. every other dictation app). But you can build flows that do a lot more, and the one I want to talk about is the Claude Code flow. Trigger model is up to you per flow: hold-to-talk, or tap-to-start / tap-to-stop. You can bind keyboard shortcuts or mouse buttons (I use mouse 5 for general dictation, right-Cmd for Claude Code). Transcription runs fully on-device. The Claude Code integration (the actual point of this post) Setup is two commands. First, register Spoke as an MCP server: claude mcp add spoke -s user -- /Applications/Spoke.app/Contents/Helpers/claude-channel-bridge (The -s user scope registers Spoke globally so you don't have to re-add it per project.) Then launch Claude Code with the experimental channels flag: claude --dangerously-load-development-channels server:spoke The flag is required for now because channels are still an experimental Claude Code feature. First time you connect a session, Spoke and Claude do a PIN pairing handshake. The channel is signed and authenticated, the key lives in your macOS keychain scoped to that process. Pair once per session, "remember" if you want it permanent. Now here's the part that's hard to explain in text (which is why there's a clip): You hit your trigger key from anywhere — browser, Figma, wherever — and talk to Claude Code without ever focusing the terminal. Voice goes straight into the running session. Standard so far. But Spoke also lets you inject screenshots and clipboard contents inline, mid-sentence. You're talking, you hit the screenshot shortcut, you keep talking, you hit the clipboard shortcut, you keep talking. When the message lands in Claude Code, the attachments are positioned at the exact moment in the sentence where you triggered them. So you can say things like: "Make the page background match this color [screenshot] and use this image as a logo [clipboard] — also add a carousel with these images [clipboard with 4 files selected]." Claude gets a single coherent message with all five attachments in the right slots. It just works. There's a history view in Spoke that shows every transcription with the attachment icons sitting between the words, in the exact positions — so you can see what got sent and where. Useful for debugging your own brain when something didn't land right. Multi-session If you're running multiple Claude Code sessions in parallel (different repos, different terminals), each pairs separately and Spoke pops a picker when you trigger the flow — IP, PID, working directory for each one. Pick which session to send to, or check "remember for this flow" and it sticks. Codex / Ghostty works too The Claude Code flow has an output step you can swap. Instead of routing through the MCP channel, you can route to a Ghostty terminal window — Spoke types into whatever's running there and presses enter. Codex, plain shell, whatever. Same voice + screenshot + clipboard injection model. (Ghostty-only for now because the standard macOS Terminal doesn't expose the APIs I need. If you haven't tried Ghostty — it's Mitchell Hashimoto's terminal, GPU-accelerated, open-source, worth the switch on its own merits.) Link: https://usespoke.app/ Happy to answer any technical questions about the channel protocol, the Parakeet pipeline, the flow architecture, why I made specific tradeoffs — whatever. I built the whole thing solo so I can go deep on any of it. If you try it and hate it, tell me why. If you try it and like it, even better. — Marek submitted by /u/stoprocentdoc [link] [comments]