Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

Vercel just shipped featuring WGSL modules, we can share shaders and it will resolve deps. that's why I'm building same concept that shadcn/ui but for shaders. pick a shader you like, adjust and your agent will copy the files.

Ξma Lorenzo

2,206 subscribers

14,352 views • 1 month ago •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

We just added over 700 shader presets into Wonder! You can now attach any SVGs, images and work with really unique shaders all inside of a canvas. We’re very excited to partner with shaders for this launch 🚀 Try it now at

We just added over 700 shader presets into Wonder! You can now attach any SVGs, images and work with really unique shaders all inside of a canvas. We’re very excited to partner with shaders for this launch 🚀 Try it now at

Wonder

39,079 views • 3 months ago

Based on the WWDC 2026 leaks, I tried to recreate the iOS 27 revamped Siri interaction inside the Dynamic Island in swift ui with lots of different settings and some custom shaders. And yeah, if it’s like that, it will be kinda boring going from a rainbow like ui to a monochrome one.

Based on the WWDC 2026 leaks, I tried to recreate the iOS 27 revamped Siri interaction inside the Dynamic Island in swift ui with lots of different settings and some custom shaders. And yeah, if it’s like that, it will be kinda boring going from a rainbow like ui to a monochrome one.

Tykra

38,717 views • 4 months ago

Introducing Themes. Hand-picked colors that you can copy and paste into your apps. This builds on top of the Styles API. Pick a style with some sane defaults, add your colors and make it yours.

Introducing Themes. Hand-picked colors that you can copy and paste into your apps. This builds on top of the Styles API. Pick a style with some sane defaults, add your colors and make it yours.

shadcn

182,650 views • 3 years ago

chan: "we all share the same dream, we all share the same thoughts, feelings, heart. it might sound a little cringey but we really love each other like family and just that itself, i'm really grateful of"

chan: "we all share the same dream, we all share the same thoughts, feelings, heart. it might sound a little cringey but we really love each other like family and just that itself, i'm really grateful of"

비니

158,267 views • 2 years ago

I keep seeing the same pattern with Three.js games, shaders, p5.js, and now 3D UI. Give a coding agent a strong reference, the live URL, and the source repo. It can study the mechanics, recreate them, and give you a working place to experiment. For this one, I turned a Trevor Noah-inspired book interaction into fictional manuals for Codex, Claude Code, and Cursor. X post: GitHub: Original site:

I keep seeing the same pattern with Three.js games, shaders, p5.js, and now 3D UI. Give a coding agent a strong reference, the live URL, and the source repo. It can study the mechanics, recreate them, and give you a working place to experiment. For this one, I turned a Trevor Noah-inspired book interaction into fictional manuals for Codex, Claude Code, and Cursor. X post: GitHub: Original site:

Meng To

181,281 views • 2 months ago

Pierre Poilievre will approve a pipeline to the West Coast and that's the end of it. "I will thank them for their input. My decision, and I'm telling Canadians before an election (?) so they can vote on it; I will approve a pipeline. Nobody has a veto." That's the bottom line. We need to get building and not babysit everyone's feelings. Mark Carney can do the same but he is choosing not to. Pierre is committing to get it done.

Pierre Poilievre will approve a pipeline to the West Coast and that's the end of it. "I will thank them for their input. My decision, and I'm telling Canadians before an election (?) so they can vote on it; I will approve a pipeline. Nobody has a veto." That's the bottom line. We need to get building and not babysit everyone's feelings. Mark Carney can do the same but he is choosing not to. Pierre is committing to get it done.

Kirk Lubimov

61,165 views • 9 months ago

LangGraph. CrewAI. Agno. Which one to pick? The good news is that this will not matter soon! Finally, we have a full picture of how the industry is solving this with just three open protocols that work across ALL frameworks. It's not about picking the best framework. Instead, it's about understanding how protocols create interoperability. The Agent Protocol Landscape shows how three complementary protocols are creating a universal language for Agents: > AG-UI (Agent-User Interaction): - The bi-directional connection between agentic backends and frontends. - This is how agents become truly interactive inside your apps, not just as chatbots, but collaborative co-workers. > MCP (Model Context Protocol): - The standard for how agents connect to tools, data, and workflows. > A2A (Agent-to-Agent): - The protocol for multi-agent coordination. - How agents delegate tasks and share intent across systems. These aren't competing standards. They're layers of the same stack and have handshakes with each other. So instead of building point-to-point integrations, you build to protocols. Moreover, you can integrate LangGraph, CrewAI, or Agno into the same frontend, without rewriting your UI logic. These protocols let everything work together. For instance: - Your LangGraph agent pulls data via MCP. - It delegates analysis to a CrewAI agent via A2A. - Results stream to your React app via AG-UI. - Users see real-time collaboration in your interface. This way, you can focus on building agent capabilities instead of integration mechanics. The protocols handle interoperability automatically. CopilotKit unifies this entire stack into one framework so you can build "Cursor for X" style apps without implementing each protocol from scratch. It gives you all three protocols, generative UI support, and production-ready infrastructure in one framework. I have shared this playbook in the replies! It breaks down handshakes, misconceptions, and real examples and shows exactly how to start building.

LangGraph. CrewAI. Agno. Which one to pick? The good news is that this will not matter soon! Finally, we have a full picture of how the industry is solving this with just three open protocols that work across ALL frameworks. It's not about picking the best framework. Instead, it's about understanding how protocols create interoperability. The Agent Protocol Landscape shows how three complementary protocols are creating a universal language for Agents: > AG-UI (Agent-User Interaction): - The bi-directional connection between agentic backends and frontends. - This is how agents become truly interactive inside your apps, not just as chatbots, but collaborative co-workers. > MCP (Model Context Protocol): - The standard for how agents connect to tools, data, and workflows. > A2A (Agent-to-Agent): - The protocol for multi-agent coordination. - How agents delegate tasks and share intent across systems. These aren't competing standards. They're layers of the same stack and have handshakes with each other. So instead of building point-to-point integrations, you build to protocols. Moreover, you can integrate LangGraph, CrewAI, or Agno into the same frontend, without rewriting your UI logic. These protocols let everything work together. For instance: - Your LangGraph agent pulls data via MCP. - It delegates analysis to a CrewAI agent via A2A. - Results stream to your React app via AG-UI. - Users see real-time collaboration in your interface. This way, you can focus on building agent capabilities instead of integration mechanics. The protocols handle interoperability automatically. CopilotKit unifies this entire stack into one framework so you can build "Cursor for X" style apps without implementing each protocol from scratch. It gives you all three protocols, generative UI support, and production-ready infrastructure in one framework. I have shared this playbook in the replies! It breaks down handshakes, misconceptions, and real examples and shows exactly how to start building.

Avi Chawla

31,074 views • 10 months ago

I found a component library with 250+ animations that will make your frontend look insane. And it's completely FREE ! >Ready to use components with animations built in >Copy and drop straight into your project >The kind of UI that makes your app look like a $50K build Your frontend will never look the same.

I found a component library with 250+ animations that will make your frontend look insane. And it's completely FREE ! >Ready to use components with animations built in >Copy and drop straight into your project >The kind of UI that makes your app look like a $50K build Your frontend will never look the same.

Harshil Tomar

187,342 views • 2 months ago

It's obvious that building won't be the bottleneck anymore. It will be distribution That's why Rork Max can easily build apps & games for iMessage and help you crack viral growth

It's obvious that building won't be the bottleneck anymore. It will be distribution That's why Rork Max can easily build apps & games for iMessage and help you crack viral growth

Rork

84,722 views • 7 months ago

It's true, most AI coding tools make you do the grunt testing and debugging work. That's why we invested in researching and building a state-of-the-art app testing tool. Replit Agent 3 will spin up a browser and test your app end-to-end.

It's true, most AI coding tools make you do the grunt testing and debugging work. That's why we invested in researching and building a state-of-the-art app testing tool. Replit Agent 3 will spin up a browser and test your app end-to-end.

Amjad Masad

110,113 views • 10 months ago

In less than 24 hours we will announce what we have been building behind the scenes. ⏳ Something you can actually use. Something that makes the $SAAR story feel complete instead of just another ticker on a screen. ⚡ It will be fun. It will be loud. And once it is out, you will understand why we kept it quiet. 👀 Lock in. Tomorrow it will be live . 🚀💎

In less than 24 hours we will announce what we have been building behind the scenes. ⏳ Something you can actually use. Something that makes the $SAAR story feel complete instead of just another ticker on a screen. ⚡ It will be fun. It will be loud. And once it is out, you will understand why we kept it quiet. 👀 Lock in. Tomorrow it will be live . 🚀💎

SAAR

19,626 views • 14 days ago

ALRIGHT, ALRIGHT...that's not just a meme. Who else can relate? If you want some RLT, drop your most creative answer, and we will pick 10 random winners. Go! 👇

ALRIGHT, ALRIGHT...that's not just a meme. Who else can relate? If you want some RLT, drop your most creative answer, and we will pick 10 random winners. Go! 👇

RollerCoin 🐹

11,177 views • 2 months ago

If you're building apps with and bolt.new, chances are that you're using Supabase Edge Functions. They can be tricky to debug, so I created a guide for the Buildcamp students who are currently on the bootcamp. I'm happy to share this with you guys if it helps? It a repeatable process that gets me through 100% of my edge function problems. Just like this post and comment "Bugs" and I'll ping you a copy.

If you're building apps with and bolt.new, chances are that you're using Supabase Edge Functions. They can be tricky to debug, so I created a guide for the Buildcamp students who are currently on the bootcamp. I'm happy to share this with you guys if it helps? It a repeatable process that gets me through 100% of my edge function problems. Just like this post and comment "Bugs" and I'll ping you a copy.

Gregory John

54,790 views • 1 year ago

We just updated our internal market research system It's the ONE THING that will make your ads, copy and landing pages 100x better And the best thing is that it takes only 30 minutes Like + Comment "research" and I'll DM the guide to you (must follow)

We just updated our internal market research system It's the ONE THING that will make your ads, copy and landing pages 100x better And the best thing is that it takes only 30 minutes Like + Comment "research" and I'll DM the guide to you (must follow)

🍀 Federico Bartoli

10,898 views • 5 months ago

more frontend vibecoding tips (results below): WHY YOUR VIBECODED FRONTENDS ALL LOOK THE SAME AND SUCK: when asked to make a frontend, the agent/llm will default to the center/average of its training data (in a very loose sense). through the training process, the model essentially converges on some default UI style. it's very capable of doing things that are different from this style, but you have to ask! for instance, ChatGPT tends to reply in the same tone for all users untill you interact with it and instruct it differently ("be sassy", "eli5"). the second reason is that most of us are not good at coming up with designs and describing them precisely (see my tweet on a crash course in common components, which i'll link below). treat frontend generation just like any other eng task! you need to provide a good detailed spec. TIPS: 1. give ur agent screenshots of designs you like (you may not know the right words to describe them but the agent will! a pic = 1000 words) where to find ui inspo? Behance, Dribbble, Mobbin (Mobbin is paid but worth it!) 2. ask ur agent for proposals, this helps "seed" different directions so the final frontend stands out. don't be afraid to go back and forth. 3. ban certain tendencies: no Inter/Roboto, no shadcn (controversial), no gradients, no emojis 4. encourage the agent to be extreme and make bold decisions, not safe ones. i think that the underlying models tend to get taught during RL/fine-tuning to make conservative choices that produce reasonable but boring frontends 5. give ur agent Figma MCP. the best results will come if you mockup your vision in Figma first. 6. Ideally choose an agent with vision capabilities TLDR: Most people are tremendously underusing agents for frontend design. They are much better than you might expect.

more frontend vibecoding tips (results below): WHY YOUR VIBECODED FRONTENDS ALL LOOK THE SAME AND SUCK: when asked to make a frontend, the agent/llm will default to the center/average of its training data (in a very loose sense). through the training process, the model essentially converges on some default UI style. it's very capable of doing things that are different from this style, but you have to ask! for instance, ChatGPT tends to reply in the same tone for all users untill you interact with it and instruct it differently ("be sassy", "eli5"). the second reason is that most of us are not good at coming up with designs and describing them precisely (see my tweet on a crash course in common components, which i'll link below). treat frontend generation just like any other eng task! you need to provide a good detailed spec. TIPS: 1. give ur agent screenshots of designs you like (you may not know the right words to describe them but the agent will! a pic = 1000 words) where to find ui inspo? Behance, Dribbble, Mobbin (Mobbin is paid but worth it!) 2. ask ur agent for proposals, this helps "seed" different directions so the final frontend stands out. don't be afraid to go back and forth. 3. ban certain tendencies: no Inter/Roboto, no shadcn (controversial), no gradients, no emojis 4. encourage the agent to be extreme and make bold decisions, not safe ones. i think that the underlying models tend to get taught during RL/fine-tuning to make conservative choices that produce reasonable but boring frontends 5. give ur agent Figma MCP. the best results will come if you mockup your vision in Figma first. 6. Ideally choose an agent with vision capabilities TLDR: Most people are tremendously underusing agents for frontend design. They are much better than you might expect.

andrew gao

64,712 views • 7 months ago

Getting a bunch of questions about this! It's a full gpu rendering pipeline with built in shader editor for Rive, which can interleave 2D + 3D. Think WebGPU (minus compute, for now) that runs anywhere, not just the browser. You can implement anything at all. Cell shading. Background blurs. Deformation effects. And yes, even Rive vector components as textures. Shaders are precompiled and ship with your .riv. Minimal runtime size impact. Still WIP.

Getting a bunch of questions about this! It's a full gpu rendering pipeline with built in shader editor for Rive, which can interleave 2D + 3D. Think WebGPU (minus compute, for now) that runs anywhere, not just the browser. You can implement anything at all. Cell shading. Background blurs. Deformation effects. And yes, even Rive vector components as textures. Shaders are precompiled and ship with your .riv. Minimal runtime size impact. Still WIP.

Guido Rosso

22,346 views • 6 months ago

Just like that… the end. 11 years of service and not even a proper goodbye, “the only people that will remember you worked overtime for your job, will be your children and family.”

Just like that… the end. 11 years of service and not even a proper goodbye, “the only people that will remember you worked overtime for your job, will be your children and family.”

EMKWAN

64,989 views • 3 years ago

Vibe coding apps that require you to store and manage large files just got easier, with Replit ⠕ App Storage. ✨ My favorite example in this category are any PDF analysis apps: create a fully customized AI synthesizer in just a few prompts. App Storage is Replit's Object Storage solution (like Amazon S3 or Google CS). But don't worry if those words sound foreign to you, Agent will set this up for you automatically if your app needs it. On that note, this Agent capability is just the beginning of our efforts to make building apps with databases and storage easier: 👇

Vibe coding apps that require you to store and manage large files just got easier, with Replit ⠕ App Storage. ✨ My favorite example in this category are any PDF analysis apps: create a fully customized AI synthesizer in just a few prompts. App Storage is Replit's Object Storage solution (like Amazon S3 or Google CS). But don't worry if those words sound foreign to you, Agent will set this up for you automatically if your app needs it. On that note, this Agent capability is just the beginning of our efforts to make building apps with databases and storage easier: 👇

vic

27,313 views • 1 year ago

Housing is a complex and difficult problem that's been building for 40 years. The idea that you can solve it quickly and easily - it's just disingenous. But we’re focused on a comprehensive approach that is tackling the problem from every single angle.

Housing is a complex and difficult problem that's been building for 40 years. The idea that you can solve it quickly and easily - it's just disingenous. But we’re focused on a comprehensive approach that is tackling the problem from every single angle.

Clare O'Neil MP

53,204 views • 4 months ago