Julian Pasquale

on the atlas — 14

• Behavioral Onboarding with Mixpanel + Userflow: A Playbook1 savers
• ELECCIONES en ESTADOS UNIDOS: LA IZQUIERDA en ASCENSO | Juan ELMAN en DEMASIADA PRESIÓN - YouTube1 savers
• Copia de Clases Youtube Orden.docx - Documentos de Google1 savers
• Ridd 🤿 en X: "I just had my aha moment with @paper 🙌 This is pretty much exactly what I want my design workflow to look like moving forward https://t.co/EvCmHc4cck" / X1 savers
• Sketch Implement Design Skill for AI Agents · Sketch1 savers
• Sign Up | LinkedIn24 savers
• Las leyes de la interfaz. | Hipermediaciones1 savers
• From Claude Code to Figma: Turning Production Code into Editable Figma Designs | Figma Blog1 savers
• Dylan Field en X: "Claude Code to Figma Design" / X1 savers
• Felix Lee en X: "Figma to Claude Code: The Designer's Playbook" / X1 savers
• Owen Roe en X: "You cannot make this up They are focusing more on flattening code and bringing frontend INTO A CANVAS instead of turning the canvas into code My goat is washed beyond belief 💔💔" / X1 savers
• Tom Johnson en X: "This is incredible. I'm seeing people bashing this but I'm pretty sure they've never had to go through the pain of working and trying to recreate complex web apps in Figma to tweak layouts and try new variants -- remove cards, update copy, try different information density, etc." / X1 savers
• guiseiz en X: "AI makes starting easy. The hard part is figuring out what to do next. Code is great for converging: one change, one refresh, one idea at a time. The canvas is where you diverge: lay it all out, see the options, think together. We built a way to go from Claude Code" / X1 savers
• Mark Gadala-Maria en X: "Claude Code in Figma isn't a feature. It's a hostile takeover of the entire dev handoff industry. Every "design-to-code" tool for the past decade has tried to make developers' lives easier. Figma just said "what if we made developers optional?" Here's what nobody's saying: the" / X1 savers

highlights — 12

• I just had my aha moment with

  Ridd 🤿 en X: "I just had my aha moment with @paper 🙌 This is pretty much exactly what I want my design workflow to look like moving forward https://t.co/EvCmHc4cck" / X

• they inspect your design, extract the visual hierarchy, gather colors and typography, export any needed assets, and then write the implementation. The skill works with our MCP server to query your Sketch documents directly. When you share a Sketch link with a frame URL, agents can automatically select and focus on that specific frame as the implementation target. The skill also includes guardrails for handling large documents and correctly exporting assets.

  Sketch Implement Design Skill for AI Agents · Sketch

• By enabling Claude to write and execute code directly within the Figma environment, we can now generate, modify, and iterate on designs in real-time. This isn’t just about automation—it’s about fundamentally changing how we approach UX testing and rapid prototyping.

  Sign Up | LinkedIn

• To be fair, it wasn’t slow in an absolute sense it took around 12 minutes. The reason it felt slow is mainly because we’ve become accustomed to near instant AI responses.

  Sign Up | LinkedIn

• Maeda no es sólo un gran diseñador: también es uno de los grandes pensadores del diseño. Sus diez leyes se pueden reducir a un único principio: “la simplicidad consiste en sustraer lo que es obvio y añadir lo específico”.

  Las leyes de la interfaz. | Hipermediaciones

• With Figma Make you can turn prompts into working prototypes, and with Copy design , you can bring any Make preview directly onto the design canvas for further iteration. Claude Code to Figma applies that same idea to code-first workflows, converting built interfaces into editable design artifacts. Different starting points, same outcome—faster creation followed by deeper exploration.

  From Claude Code to Figma: Turning Production Code into Editable Figma Designs | Figma Blog

• Our point of view is that the design canvas is better at navigating lots of possibilities than prompting in an IDE / ADE. With the canvas you can think divergently and see the big picture by comparing approaches side by side. You can also use direct manipulation to edit details. Finally, after you've explored options and polished the design, you can simply use the Figma MCP to pull design changes back into your codebase.

  Dylan Field en X: "Claude Code to Figma Design" / X

• 1. NAME LAYERS LIKE CSS CLASSES nav-links ✓ Group 5 ✗ 2. WORK SECTION BY SECTION Hero → Features → Testimonials → Footer (Don't ask for entire page at once) 3. REFERENCE FIGMA DIRECTLY "Look at the card in the Features section" (Not: "Create a card with rounded corners") 4. EXPORT ASSETS FIRST Images need manual export → /public folder Then tell Claude: "Hero image is at /public/hero.png" 5. SHARE YOUR STACK UPFRONT "I'm using Next.js 14 + Tailwind + TypeScript" (Claude will match your conventions)

  Felix Lee en X: "Figma to Claude Code: The Designer's Playbook" / X

• They are focusing more on flattening code and bringing frontend INTO A CANVAS instead of turning the canvas into code

  Owen Roe en X: "You cannot make this up They are focusing more on flattening code and bringing frontend INTO A CANVAS instead of turning the canvas into code My goat is washed beyond belief 💔💔" / X

• I just recreated basically all of the data-heavy core UI of Vercel (something that was nearly impossible to do before) with ACTUAL data in less than 5 minutes.

  Tom Johnson en X: "This is incredible. I'm seeing people bashing this but I'm pretty sure they've never had to go through the pain of working and trying to recreate complex web apps in Figma to tweak layouts and try new variants -- remove cards, update copy, try different information density, etc." / X

• Code is great for converging: one change, one refresh, one idea at a time. The canvas is where you diverge: lay it all out, see the options, think together.

  guiseiz en X: "AI makes starting easy. The hard part is figuring out what to do next. Code is great for converging: one change, one refresh, one idea at a time. The canvas is where you diverge: lay it all out, see the options, think together. We built a way to go from Claude Code" / X

• Los desarrolladores que celebran esto como "¡por fin, especificaciones precisas!" no entienden la idea. No están consiguiendo mejores entregas. Están eliminando la entrega por completo. Ese archivo de Figma ya no necesita que lo interpretes. Se interpreta solo.

  Mark Gadala-Maria en X: "Claude Code in Figma isn't a feature. It's a hostile takeover of the entire dev handoff industry. Every "design-to-code" tool for the past decade has tried to make developers' lives easier. Figma just said "what if we made developers optional?" Here's what nobody's saying: the" / X