Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Just got a preview of MagicPath's new Figma integration… 2026 is about to close the entire loop on design and code. From the code quality to the pixel placement - this is the snappiest loop I’ve ever used. Not exaggerating. I think Pietro Schirano just figured it out.

designertom's profile picture

Tommy Geoco 🇺🇸

18,592 subscribers

25,030 Aufrufe • vor 8 Monaten •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

For years, the design industry has talked about "design vs code" And tools (including Figma!) have forced a choice. But this is a false debate. Code isn't the opposite of design. Code is a material for design. So we're bringing code to the Figma canvas with Code Layers.
0:20

For years, the design industry has talked about "design vs code" And tools (including Figma!) have forced a choice. But this is a false debate. Code isn't the opposite of design. Code is a material for design. So we're bringing code to the Figma canvas with Code Layers.

Dylan Field

97,538 Aufrufe • vor 2 Monaten

The Figma MCP is insanely good. First time I used it felt like AGI. Feed designs to the MCP, done. It reads frames, components, variables, layout, and generates close to pixel perfect code. I one-shotted my design in this 150 second video with Devin.
2:47

The Figma MCP is insanely good. First time I used it felt like AGI. Feed designs to the MCP, done. It reads frames, components, variables, layout, and generates close to pixel perfect code. I one-shotted my design in this 150 second video with Devin.

nader dabit

119,262 Aufrufe • vor 7 Monaten

Design → code → canvas → feedback → repeat. The Figma MCP server is now bidirectional. GitHub Copilot users can pull design context into code and push working UI back to the Figma canvas, all from Visual Studio Code . No handoffs or context switching. Just flow.
1:40

Design → code → canvas → feedback → repeat. The Figma MCP server is now bidirectional. GitHub Copilot users can pull design context into code and push working UI back to the Figma canvas, all from Visual Studio Code . No handoffs or context switching. Just flow.

Mario Rodriguez

106,156 Aufrufe • vor 6 Monaten

Figma to AI back to Figma This is a great loop for design explorations and gain back full control of the results. You can ask Aura to create new components, icons, graphics and entire screens based on existing design systems. All fully layered, nested and based on your prompt.
0:45

Figma to AI back to Figma This is a great loop for design explorations and gain back full control of the results. You can ask Aura to create new components, icons, graphics and entire screens based on existing design systems. All fully layered, nested and based on your prompt.

Meng To

75,736 Aufrufe • vor 1 Jahr

🚨 Anthropic CEO Dario Amodei just dropped a massive timeline update at Davos 2026: “I have engineers within Anthropic who say ‘I don’t write any code anymore. I just let the model write the code, I edit it’... - the creator of Claude code recently also said “100% of his contributions to Claude code were written by Claude code” for the month of December Dario then goes onto say: “We might be 6 to 12 months away from when the model is doing most, maybe all of what SWEs do end-to-end.” If the recursive self-improvement loop closes this year, the curve is about to go vertical.
1:41

🚨 Anthropic CEO Dario Amodei just dropped a massive timeline update at Davos 2026: “I have engineers within Anthropic who say ‘I don’t write any code anymore. I just let the model write the code, I edit it’... - the creator of Claude code recently also said “100% of his contributions to Claude code were written by Claude code” for the month of December Dario then goes onto say: “We might be 6 to 12 months away from when the model is doing most, maybe all of what SWEs do end-to-end.” If the recursive self-improvement loop closes this year, the curve is about to go vertical.

Chris

680,690 Aufrufe • vor 8 Monaten

damn its so easy to go from design -> code with Figma MCP + Claude Code. literally just one click of a button, and the code is ready! still a lot of polishing to do, but this has helped us make development ~50% faster 😁
1:19

damn its so easy to go from design -> code with Figma MCP + Claude Code. literally just one click of a button, and the code is ready! still a lot of polishing to do, but this has helped us make development ~50% faster 😁

Marcel

54,670 Aufrufe • vor 7 Monaten

"The work is done, and here’s the video to prove it." 🎥 Watching these agents run their own browser tests and provide screen recordings of the finished task is a massive win for transparency. It's not just about writing code; it's about closing the feedback loop automatically.
1:02

"The work is done, and here’s the video to prove it." 🎥 Watching these agents run their own browser tests and provide screen recordings of the finished task is a massive win for transparency. It's not just about writing code; it's about closing the feedback loop automatically.

Google Antigravity

72,325 Aufrufe • vor 7 Monaten

Introducing ralph-research plugin. I just adopted the ralph-loop for implementing papers. Mindblown how good this works already. The entire plugin was one-shotted by Claude Code, but it can already code AI paper concepts and run experiments in a self-improving loop. Wild!
0:50

Introducing ralph-research plugin. I just adopted the ralph-loop for implementing papers. Mindblown how good this works already. The entire plugin was one-shotted by Claude Code, but it can already code AI paper concepts and run experiments in a self-improving loop. Wild!

elvis

221,360 Aufrufe • vor 8 Monaten

not even exaggerating when i say this is one of the best songs ever… i have NO idea what woozi put in it but it’s so perfect to loop
2:15

not even exaggerating when i say this is one of the best songs ever… i have NO idea what woozi put in it but it’s so perfect to loop

misa

197,470 Aufrufe • vor 1 Jahr

Andrej Karpathy: "The future is not writing code. The future is writing the loops that write the code. The leverage point has moved one floor up." This is the shift that defines the next era of coding and quant building. 1 hour of pure insight on agentic AI coding and loop engineering from the OpenAI co-founder who just joined Anthropic to build self improving Claude. Worth more than every $500 vibe coding course combined. Watch it, then read the full guide on how to build your first self improving quant trading loop below.
1:04:50

Andrej Karpathy: "The future is not writing code. The future is writing the loops that write the code. The leverage point has moved one floor up." This is the shift that defines the next era of coding and quant building. 1 hour of pure insight on agentic AI coding and loop engineering from the OpenAI co-founder who just joined Anthropic to build self improving Claude. Worth more than every $500 vibe coding course combined. Watch it, then read the full guide on how to build your first self improving quant trading loop below.

Roan

38,070 Aufrufe • vor 3 Monaten

A TURING AWARD WINNER STOOD UP AND TOLD A ROOM OF ENGINEERS THAT ALMOST NONE OF THEM DO THE ONE THING THAT ACTUALLY SEPARATES REAL ENGINEERING FROM TYPING, THEY WRITE CODE BUT THEY NEVER WRITE THE BLUEPRINT 56 minutes from Leslie Lamport -- Turing Award winner, creator of the tech behind almost every distributed system on earth. -> His claim: architects draw plans before a brick is laid. Programmers just start coding and hope. That gap is where complex systems quietly break. 04:10 -- A blueprint for software is called a spec. Write what the system must DO before touching how it does it. 10:13 -- Thinking above the code is the skill. The language is just the last, easiest step. 43:23 -- What programmers should really know isn't syntax. It's thinking clearly enough that "done" actually means done. 48:15 -- Thinking is hard, so we skip it. We jump straight to code because typing feels like progress. And this is exactly the wall the new "Loop engineering" hype is about to hit -- people now design loops of agents that write and check code while they walk away. But an unattended loop with no spec just ships broken work faster. Lamport is the missing half: the discipline that makes it safe to leave a loop running at all. You thought the leverage moved into better prompts and better loops. This is the man showing it moved above the code, where almost no one is willing to think. Save this. Read it before you trust a single agent loop ↓
56:47

A TURING AWARD WINNER STOOD UP AND TOLD A ROOM OF ENGINEERS THAT ALMOST NONE OF THEM DO THE ONE THING THAT ACTUALLY SEPARATES REAL ENGINEERING FROM TYPING, THEY WRITE CODE BUT THEY NEVER WRITE THE BLUEPRINT 56 minutes from Leslie Lamport -- Turing Award winner, creator of the tech behind almost every distributed system on earth. -> His claim: architects draw plans before a brick is laid. Programmers just start coding and hope. That gap is where complex systems quietly break. 04:10 -- A blueprint for software is called a spec. Write what the system must DO before touching how it does it. 10:13 -- Thinking above the code is the skill. The language is just the last, easiest step. 43:23 -- What programmers should really know isn't syntax. It's thinking clearly enough that "done" actually means done. 48:15 -- Thinking is hard, so we skip it. We jump straight to code because typing feels like progress. And this is exactly the wall the new "Loop engineering" hype is about to hit -- people now design loops of agents that write and check code while they walk away. But an unattended loop with no spec just ships broken work faster. Lamport is the missing half: the discipline that makes it safe to leave a loop running at all. You thought the leverage moved into better prompts and better loops. This is the man showing it moved above the code, where almost no one is willing to think. Save this. Read it before you trust a single agent loop ↓

slash1s

15,371 Aufrufe • vor 2 Monaten

The person who built Claude Code just explained how he is using it "Now I just have an army of agents that are doing stuff" Only 18 minutes, the best Claude guide on the internet right now. Boris Cherny covered: > how Claude Code is moving beyond just engineers > routines for CI, code review, and daily workflows > why the loop is the next big leap > working with hundreds of agents at once everything is already running through agents, ignoring this is not an option that's exactly why I wrote a full guide on how to build one yourself with Claude Code article below
17:28

The person who built Claude Code just explained how he is using it "Now I just have an army of agents that are doing stuff" Only 18 minutes, the best Claude guide on the internet right now. Boris Cherny covered: > how Claude Code is moving beyond just engineers > routines for CI, code review, and daily workflows > why the loop is the next big leap > working with hundreds of agents at once everything is already running through agents, ignoring this is not an option that's exactly why I wrote a full guide on how to build one yourself with Claude Code article below

Anatoli Kopadze

16,858 Aufrufe • vor 3 Monaten

This is insane! I just used the new Claude Code Playground plugin to level up my Nano Banana Image generator skill. My skill has a self-improving loop, but with the playground skill, I can also pass precise annotations to nano banana as it improves the images. It's so good!
0:24

This is insane! I just used the new Claude Code Playground plugin to level up my Nano Banana Image generator skill. My skill has a self-improving loop, but with the playground skill, I can also pass precise annotations to nano banana as it improves the images. It's so good!

elvis

287,012 Aufrufe • vor 7 Monaten

comparison of o1 vs sonnet for converting a Figma design to code is the extra time and cost worth it?
1:03

comparison of o1 vs sonnet for converting a Figma design to code is the extra time and cost worth it?

Steve (Builder.io)

196,560 Aufrufe • vor 1 Jahr

That gap between design and production? Closed. 🔁 GitHub Copilot, Visual Studio Code, and Figma now create a continuous loop. With the bidirectional Figma MCP server, Copilot users can: 🔹 Pull design context into code 🔹 Push working UI back to the canvas Connect your canvas and stay in the flow. 👇
1:40

That gap between design and production? Closed. 🔁 GitHub Copilot, Visual Studio Code, and Figma now create a continuous loop. With the bidirectional Figma MCP server, Copilot users can: 🔹 Pull design context into code 🔹 Push working UI back to the canvas Connect your canvas and stay in the flow. 👇

GitHub

113,297 Aufrufe • vor 6 Monaten

Dario Amodei just told software engineers exactly how long they have. Six to twelve months. Amodei: “I have engineers within Anthropic who say I don’t write any code anymore. I just let the model write the code, I edit it, I do the things around it.” The people building the most powerful AI in history have already stopped writing code. That is not a forecast. That is the current working condition inside the lab closest to the frontier. Amodei: “We might be six to 12 months away from when the model is doing most, maybe all, of what SWEs do end-to-end.” The tech industry spent a decade making software engineers its highest-paid, most protected class. That era has a last day now. When a model can execute an entire software build end-to-end, the ability to write syntax stops being a skill. It becomes a credential for a job that no longer exists. Amodei: “And then it’s a question of how fast does that loop close.” That is the sentence everyone skipped. The code was never the hard part. The hard part was everything around it. The model just learned everything around it. Writing the code is already nearly gone. Testing is next. Deployment is next. When all three collapse into a single autonomous execution loop, the machine no longer needs a human in the chain at all. The corporation or sovereign state that closes that loop first does not gain a competitive advantage. It gains a category of speed that biological engineers cannot match, track, or reverse. That is not disruption. That is replacement at a systems level. Amodei is not describing a future disruption. He is describing the current state of his own building. The loop is already closing. The only question is whether you are inside it or outside it when it seals.
0:27

Dario Amodei just told software engineers exactly how long they have. Six to twelve months. Amodei: “I have engineers within Anthropic who say I don’t write any code anymore. I just let the model write the code, I edit it, I do the things around it.” The people building the most powerful AI in history have already stopped writing code. That is not a forecast. That is the current working condition inside the lab closest to the frontier. Amodei: “We might be six to 12 months away from when the model is doing most, maybe all, of what SWEs do end-to-end.” The tech industry spent a decade making software engineers its highest-paid, most protected class. That era has a last day now. When a model can execute an entire software build end-to-end, the ability to write syntax stops being a skill. It becomes a credential for a job that no longer exists. Amodei: “And then it’s a question of how fast does that loop close.” That is the sentence everyone skipped. The code was never the hard part. The hard part was everything around it. The model just learned everything around it. Writing the code is already nearly gone. Testing is next. Deployment is next. When all three collapse into a single autonomous execution loop, the machine no longer needs a human in the chain at all. The corporation or sovereign state that closes that loop first does not gain a competitive advantage. It gains a category of speed that biological engineers cannot match, track, or reverse. That is not disruption. That is replacement at a systems level. Amodei is not describing a future disruption. He is describing the current state of his own building. The loop is already closing. The only question is whether you are inside it or outside it when it seals.

Dustin

318,698 Aufrufe • vor 6 Monaten

I’ve been watching this on loop for two days and I legitimately think this is one of the best covers of any song I’ve ever heard. It gets better every time.
2:19

I’ve been watching this on loop for two days and I legitimately think this is one of the best covers of any song I’ve ever heard. It gets better every time.

David Blattman

10,549 Aufrufe • vor 3 Jahren

The new Screenshot to Code from Vercel v0 is insane. I just took a screenshot of a pricing table and it was converted into code using AI in seconds! It even outputs the code and allows you to modify any specific parts.
0:20

The new Screenshot to Code from Vercel v0 is insane. I just took a screenshot of a pricing table and it was converted into code using AI in seconds! It even outputs the code and allows you to modify any specific parts.

Alvaro Cintas

378,059 Aufrufe • vor 2 Jahren

After testing every AI toolchain for a year, this is the only workflow I'm endorsing: Figma → Claude Code (Sonnet 4.5) Here's how I'm building Lorelight: 1. Design the happy path in Figma 2. Feed it to Claude Code via Figma MCP 3. Get a strong foundation in 15 minutes 4. Spend the next 50+ hours iterating (still design work) The design/dev loop that used to be isolated is finally closing. I even built a complete design system in within minutes. Custom components, living documentation, accessibility rules all from the Figma designs. If you're measuring the effectiveness of these tools by whether they can "one-shot" a design, you're consuming too many AI hype commercials. Log off. Then go actually build something with your hands. With AI. With your taste. Stop trying to "one-shot" good shit. And go make stuff with the new tools. For designers who want to ship real products, this is the stack that's getting it done.
2:00

After testing every AI toolchain for a year, this is the only workflow I'm endorsing: Figma → Claude Code (Sonnet 4.5) Here's how I'm building Lorelight: 1. Design the happy path in Figma 2. Feed it to Claude Code via Figma MCP 3. Get a strong foundation in 15 minutes 4. Spend the next 50+ hours iterating (still design work) The design/dev loop that used to be isolated is finally closing. I even built a complete design system in within minutes. Custom components, living documentation, accessibility rules all from the Figma designs. If you're measuring the effectiveness of these tools by whether they can "one-shot" a design, you're consuming too many AI hype commercials. Log off. Then go actually build something with your hands. With AI. With your taste. Stop trying to "one-shot" good shit. And go make stuff with the new tools. For designers who want to ship real products, this is the stack that's getting it done.

Tommy Geoco

22,905 Aufrufe • vor 11 Monaten