Video yükleniyor...

Video Yüklenemedi

Bu video yüklenirken bir sorun oluştu. Bu geçici bir ağ sorunundan kaynaklanıyor olabilir veya video kullanılamıyor olabilir.

Ana Sayfaya Dön

I got tired of hand-writing React animations. So I built a Motion Compiler: a Figma-like canvas that turns Scene IR into deterministic React Native code!🚀 🎯 Scenes + advanced editors 📱 One-click Expo Snack 🔓 100% client-side. Free. OSS. 🌐 WYSIWYG → Web, iOS, Android ⬇️ 🧵

Saúl

5,886 subscribers

26,073 görüntüleme • 1 ay önce •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

so i got tired of googling "free UI click sound mp3" every time i needed sounds for a project built soundcn - 700+ free UI (gaming, notification, retro, voiceover) sounds you can drop into any react app with one command: npx shadcn add @soundcn/click-soft no npm packages, no audio files to manage. just a .ts file with inline base64 audio. zero deps

so i got tired of googling "free UI click sound mp3" every time i needed sounds for a project built soundcn - 700+ free UI (gaming, notification, retro, voiceover) sounds you can drop into any react app with one command: npx shadcn add @soundcn/click-soft no npm packages, no audio files to manage. just a .ts file with inline base64 audio. zero deps

KapishDima

61,858 görüntüleme • 5 ay önce

This weekend, I explored a mobile game idea with my kids (they suggested a mobile pokemon-like game) so I had them coming up with ideas for the creatures and I try to visualise them with ChatGPT Images 2.0 and vibe coded a small prototype on Cursor to play around with. The art direction of the creatures are in vinyl toy matte style so it has this toy-like aesthetic quality that I quite like! For a mobile app/game, I went with Expo + React Native to create this mobile app so that I have one code-base for both Android and iOS. So far I'm pretty impressed with Expo's live mobile app preview feature! Being able to easily preview the mobile app on my phone in seconds is a big plus.

This weekend, I explored a mobile game idea with my kids (they suggested a mobile pokemon-like game) so I had them coming up with ideas for the creatures and I try to visualise them with ChatGPT Images 2.0 and vibe coded a small prototype on Cursor to play around with. The art direction of the creatures are in vinyl toy matte style so it has this toy-like aesthetic quality that I quite like! For a mobile app/game, I went with Expo + React Native to create this mobile app so that I have one code-base for both Android and iOS. So far I'm pretty impressed with Expo's live mobile app preview feature! Being able to easily preview the mobile app on my phone in seconds is a big plus.

Danny Limanseta

37,093 görüntüleme • 2 ay önce

Stumbled on Vercel’s creative design team page and instantly fell in love with the design, animations, and micro-interactions. So I decided to take a shot at it, recreating the experience for a fictional company called Varxell, with my own spin on everything except the design itself + I didn’t touch any of their assets. Everything was hand-coded from scratch, and every single asset was recreated in Figma. It was a fun challenge. Built with: • React • TypeScript • Vite • Framer Motion Live site: • • Repo: • Every page functionality and animation was implemented as a reusable hook, with internal JSDoc to make it easy to reuse in your own projects or remix however you like. Got any questions? Feel free to shoot me a DM

Stumbled on Vercel’s creative design team page and instantly fell in love with the design, animations, and micro-interactions. So I decided to take a shot at it, recreating the experience for a fictional company called Varxell, with my own spin on everything except the design itself + I didn’t touch any of their assets. Everything was hand-coded from scratch, and every single asset was recreated in Figma. It was a fun challenge. Built with: • React • TypeScript • Vite • Framer Motion Live site: • • Repo: • Every page functionality and animation was implemented as a reusable hook, with internal JSDoc to make it easy to reuse in your own projects or remix however you like. Got any questions? Feel free to shoot me a DM

David Herbert👨🏽‍💻🚀

23,755 görüntüleme • 1 yıl önce

Let's build a Deepseek Wrapper (Mobile App) without writing a single line of code! Everyone is talking about building web apps with AI, but no one is talking about building mobile apps. This video tutorial and @senior_swc template (built by ) will help you get starting building an app on iOS. This is react native so it's also compatible with Android and Web (But we will cover this in a future video). The point of this video is to get some experience in the simulator and to start building an app. In a video, soon, we will take the app we've built, test it on our phone, and put it on Test-Flight! (Without writing ANY code!) Just a warning: The DeepSeek API has been tough to rely on. So I decided to add Gemini into my app as a backup, which you can do as well (with any AI model) The code for template is on the next tweet. Timestamps: 00:00 Introduction 01:35 Setting Up Xcode and iPhone Simulator 02:29 Downloading and Configuring Cursor 04:10 Forking the Template and Initial Setup 06:10 Implementing Authentication with Clerk 08:23 Adding DeepSeek API and Testing 13:35 Enhancing the App with SupaData API 19:00 Using the Serp API to fetch video links 23:00 Figuring things out 27:30 Woohoo!!! Perplexitube Shout out to Galaxies-dev on GitHub, who's repo (chatgpt-clone-react-native), we very helpful in building this template quickly.

Let's build a Deepseek Wrapper (Mobile App) without writing a single line of code! Everyone is talking about building web apps with AI, but no one is talking about building mobile apps. This video tutorial and @senior_swc template (built by ) will help you get starting building an app on iOS. This is react native so it's also compatible with Android and Web (But we will cover this in a future video). The point of this video is to get some experience in the simulator and to start building an app. In a video, soon, we will take the app we've built, test it on our phone, and put it on Test-Flight! (Without writing ANY code!) Just a warning: The DeepSeek API has been tough to rely on. So I decided to add Gemini into my app as a backup, which you can do as well (with any AI model) The code for template is on the next tweet. Timestamps: 00:00 Introduction 01:35 Setting Up Xcode and iPhone Simulator 02:29 Downloading and Configuring Cursor 04:10 Forking the Template and Initial Setup 06:10 Implementing Authentication with Clerk 08:23 Adding DeepSeek API and Testing 13:35 Enhancing the App with SupaData API 19:00 Using the Serp API to fetch video links 23:00 Figuring things out 27:30 Woohoo!!! Perplexitube Shout out to Galaxies-dev on GitHub, who's repo (chatgpt-clone-react-native), we very helpful in building this template quickly.

Riley Brown

128,580 görüntüleme • 1 yıl önce

Thoughts on transferable skills. I was surprised reading the comments to Riley’s question about best UI animation tool for web. To anyone interested in diving into motion design I would strongly recommend - aim to become a motion expert, not Jitter/Rive/Lottie specialist. If you start from the foundations, jumping into any animation tool will feel like a walk in the park. Keyframes, easing functions, transformations - same concepts are shared between all of them. Getting to know the foundations on the web means starting with CSS, Tailwind or React Motion. I’m often creating small motion concepts in Figma (see video) and then recreating them manually in code. Any language, it doesn’t matter because principles are the same. I recently made the switch to Swift and built a small animation tool for myself (see video) that I’ll discard after I’m done with the motion. This level of comfortableness with motion gives you unmatched flexibility. From that point, tools are just interfaces for expressing something you already deeply understand. This is not about performance or technical optimizations (Lottie files can outperform CSS equivalents), tools mentioned above really are great - it’s about developing transferable creative skill that lets you think across any medium, platform or tool.

Thoughts on transferable skills. I was surprised reading the comments to Riley’s question about best UI animation tool for web. To anyone interested in diving into motion design I would strongly recommend - aim to become a motion expert, not Jitter/Rive/Lottie specialist. If you start from the foundations, jumping into any animation tool will feel like a walk in the park. Keyframes, easing functions, transformations - same concepts are shared between all of them. Getting to know the foundations on the web means starting with CSS, Tailwind or React Motion. I’m often creating small motion concepts in Figma (see video) and then recreating them manually in code. Any language, it doesn’t matter because principles are the same. I recently made the switch to Swift and built a small animation tool for myself (see video) that I’ll discard after I’m done with the motion. This level of comfortableness with motion gives you unmatched flexibility. From that point, tools are just interfaces for expressing something you already deeply understand. This is not about performance or technical optimizations (Lottie files can outperform CSS equivalents), tools mentioned above really are great - it’s about developing transferable creative skill that lets you think across any medium, platform or tool.

Natko Hasic

64,045 görüntüleme • 1 yıl önce

Here are a few things you probably did not know about Reddit's iOS and Android apps: they are ~2.5M lines of code each, with 500+ screens, and a total of 200 native mobile engineers work on the both of them (including a dedicated iOS and Android mobile platform team) But a few years ago, things looked very different - and Reddit quietly rebuilt their native apps from 2021. Today's conversation goes through what happened and how, with three engineers from Reddit’s mobile platform team who led this work: Lauren Darcey (Head of Mobile Platform), Brandon Kobilansky (iOS Platform Lead), and Eric Kuck (Principal Android Engineer) Watch or listen: • YouTube: • Spotify: • Apple: --- Brought to you by: • Graphite (we've moved to @graphite) — The AI developer productivity platform • Sentry — Error and performance monitoring for developers. Get 150k errors (three months of Team Plan) for free at --- Three of my takeaways from this episode: 𝟭. 𝗣𝗼𝗼𝗿 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿 𝗲𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲 𝗰𝗮𝗻 𝘀𝗹𝗼𝘄 𝗱𝗼𝘄𝗻 𝗮 𝗰𝗼𝗺𝗽𝗮𝗻𝘆 – 𝘀𝗼 𝗽𝗮𝘆 𝗮𝘁𝘁𝗲𝗻𝘁𝗶𝗼𝗻! One of the reasons Reddit started investing heavily in modernizing its mobile stack was that the “old stack” was slowing down developers. Reddit’s platform team got proof of this simply by asking native engineers about the biggest development-related challenges they face. 𝟮. 𝗣𝗹𝗮𝘁𝗳𝗼𝗿𝗺 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 𝗶𝘀 𝗵𝗮𝗿𝗱 𝘄𝗼𝗿𝗸. Advice from Brandon for anyone looking to work on a platform team: "You should try to work at a tech company for a year or two and actually see what happens after you ship a system — and then the assumptions change! You then have to figure out how to keep this thing going. You get a bunch of software design intuition because you have to like re-evaluate your assumptions for an incredibly long time. If you can do that, you're probably ready for platform stuff." 𝟯. 𝗚𝗲𝗻𝗔𝗜 𝗰𝗼𝗱𝗶𝗻𝗴 𝘁𝗼𝗼𝗹𝘀 𝗳𝗲𝗲𝗹 𝗹𝗶𝗸𝗲 𝘁𝗵𝗲𝘆 𝗮𝗿𝗲 𝗻𝗼𝘁 “𝘁𝗵𝗲𝗿𝗲” 𝘆𝗲𝘁 𝘄𝗶𝘁𝗵 𝗻𝗮𝘁𝗶𝘃𝗲 𝗺𝗼𝗯𝗶𝗹𝗲. LLMs integrated into IDEs seem to be increasingly helpful with backend, fullstack, web and even cross-platform (React Native / Expo) projects. However, Reddit’s mobile team shared that they get a moderate boost from the Apple and Android Studio LLM additions. Native mobile development is distinctively different from web, fullstack and backend coding – and it seems that these IDEs with AI functionality have not done much to optimize for the expereince of native mobile engineers. Over time, this will likely change – but it’s a reminder that there are differences between fullstack, backend and native mobile development.(I wrote a book reflecting on more of the challenges unique to native mobile titled Building Mobile Apps at Scale)

Here are a few things you probably did not know about Reddit's iOS and Android apps: they are ~2.5M lines of code each, with 500+ screens, and a total of 200 native mobile engineers work on the both of them (including a dedicated iOS and Android mobile platform team) But a few years ago, things looked very different - and Reddit quietly rebuilt their native apps from 2021. Today's conversation goes through what happened and how, with three engineers from Reddit’s mobile platform team who led this work: Lauren Darcey (Head of Mobile Platform), Brandon Kobilansky (iOS Platform Lead), and Eric Kuck (Principal Android Engineer) Watch or listen: • YouTube: • Spotify: • Apple: --- Brought to you by: • Graphite (we've moved to @graphite) — The AI developer productivity platform • Sentry — Error and performance monitoring for developers. Get 150k errors (three months of Team Plan) for free at --- Three of my takeaways from this episode: 𝟭. 𝗣𝗼𝗼𝗿 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿 𝗲𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲 𝗰𝗮𝗻 𝘀𝗹𝗼𝘄 𝗱𝗼𝘄𝗻 𝗮 𝗰𝗼𝗺𝗽𝗮𝗻𝘆 – 𝘀𝗼 𝗽𝗮𝘆 𝗮𝘁𝘁𝗲𝗻𝘁𝗶𝗼𝗻! One of the reasons Reddit started investing heavily in modernizing its mobile stack was that the “old stack” was slowing down developers. Reddit’s platform team got proof of this simply by asking native engineers about the biggest development-related challenges they face. 𝟮. 𝗣𝗹𝗮𝘁𝗳𝗼𝗿𝗺 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 𝗶𝘀 𝗵𝗮𝗿𝗱 𝘄𝗼𝗿𝗸. Advice from Brandon for anyone looking to work on a platform team: "You should try to work at a tech company for a year or two and actually see what happens after you ship a system — and then the assumptions change! You then have to figure out how to keep this thing going. You get a bunch of software design intuition because you have to like re-evaluate your assumptions for an incredibly long time. If you can do that, you're probably ready for platform stuff." 𝟯. 𝗚𝗲𝗻𝗔𝗜 𝗰𝗼𝗱𝗶𝗻𝗴 𝘁𝗼𝗼𝗹𝘀 𝗳𝗲𝗲𝗹 𝗹𝗶𝗸𝗲 𝘁𝗵𝗲𝘆 𝗮𝗿𝗲 𝗻𝗼𝘁 “𝘁𝗵𝗲𝗿𝗲” 𝘆𝗲𝘁 𝘄𝗶𝘁𝗵 𝗻𝗮𝘁𝗶𝘃𝗲 𝗺𝗼𝗯𝗶𝗹𝗲. LLMs integrated into IDEs seem to be increasingly helpful with backend, fullstack, web and even cross-platform (React Native / Expo) projects. However, Reddit’s mobile team shared that they get a moderate boost from the Apple and Android Studio LLM additions. Native mobile development is distinctively different from web, fullstack and backend coding – and it seems that these IDEs with AI functionality have not done much to optimize for the expereince of native mobile engineers. Over time, this will likely change – but it’s a reminder that there are differences between fullstack, backend and native mobile development.(I wrote a book reflecting on more of the challenges unique to native mobile titled Building Mobile Apps at Scale)

Gergely Orosz

67,225 görüntüleme • 1 yıl önce

I JUST BUILT AN ENTIRE APP IN 10 MIN THAT PEOPLE WOULD PAY $100/MO TO ACCESS i gave perplexity computer one prompt and it built me an app that scans X, reddit, and forums for people literally asking for what you sell stuff like “anyone know a good…”, “looking for help with…”, “what’s the best tool for…” you drop in keywords and it tracks all of it in real time, then ranks each post based on how likely that person is to actually buy it turns every post into a lead with a summary, link, and intent score so you instantly know what’s worth responding to then you click once and it writes the DM, the reply, the cold email, even a content idea based on that post so instead of searching, thinking, rewriting, switching tabs… it’s just see signal → click → send i can save leads, track what i’ve responded to, and run multiple keyword streams at once i can’t code and this thing is basically a full lead gen engine + content machine in one dashboard comment "COMPUTER" and i'll send the exact prompt I used

I JUST BUILT AN ENTIRE APP IN 10 MIN THAT PEOPLE WOULD PAY $100/MO TO ACCESS i gave perplexity computer one prompt and it built me an app that scans X, reddit, and forums for people literally asking for what you sell stuff like “anyone know a good…”, “looking for help with…”, “what’s the best tool for…” you drop in keywords and it tracks all of it in real time, then ranks each post based on how likely that person is to actually buy it turns every post into a lead with a summary, link, and intent score so you instantly know what’s worth responding to then you click once and it writes the DM, the reply, the cold email, even a content idea based on that post so instead of searching, thinking, rewriting, switching tabs… it’s just see signal → click → send i can save leads, track what i’ve responded to, and run multiple keyword streams at once i can’t code and this thing is basically a full lead gen engine + content machine in one dashboard comment "COMPUTER" and i'll send the exact prompt I used

Ryan Hart

32,122 görüntüleme • 3 ay önce

Speaking of graphs... here is something I wanted to build since 3 months, and finally had the chance to, thanks to Pi I often have these sequence of prompts that emerge while I work. Not just sequences but conditionals that necessitate control flow For example, one workflow that resembles socratic questioning: 1. Discuss some problem 2. "What is the most elegant and long-term production ready solution for this?" -> Agent replies 3. "Is that the holy grail?" 4. Agent can reply "yes it is, basically" or "no, it is not, it is instead ..." 5. If yes, continue to "autoimplement". If no, think about it and decide what to do And "autoimplement" is a single prompt of 6-7 sequential steps, which I've been meaning to make more deterministic as well But I wasn't sure how to build it I had previously built acpx workflows to be a swiss army knife, "something like n8n, but can drive codex through deterministic steps, nodes in a graph. or claude code. or pi. it uses acp..." But it had one problem. It was run from outside the harness, like a CI orchestrator I wanted to integrate acpx into pi. Because pi was the only CLI that could enable building of such a thing. But I wasn't sure how to reconcile a general ACP-based tool into a single coding agent I was being too accommodative of all the other harnesses, claude code, codex. I was trying to be too general I have changed my mind since then ACP is great and lets you integrate a harness into other software in cool ways But maybe, if a harness is proprietary, does not accept outside contributions, or does not even *support ACP*, maybe, it does not deserve cool features 😤 (they know who they are) So I ripped out ACP, and built it natively, only for pi No need for a web viewer... Just view it in a native widget, right inside pi! I cannot put into words how awesome it is to be able to do this! I am still tinkering, discovering. It is at osolmaz/pi-workflows if you want to take a look

Speaking of graphs... here is something I wanted to build since 3 months, and finally had the chance to, thanks to Pi I often have these sequence of prompts that emerge while I work. Not just sequences but conditionals that necessitate control flow For example, one workflow that resembles socratic questioning: 1. Discuss some problem 2. "What is the most elegant and long-term production ready solution for this?" -> Agent replies 3. "Is that the holy grail?" 4. Agent can reply "yes it is, basically" or "no, it is not, it is instead ..." 5. If yes, continue to "autoimplement". If no, think about it and decide what to do And "autoimplement" is a single prompt of 6-7 sequential steps, which I've been meaning to make more deterministic as well But I wasn't sure how to build it I had previously built acpx workflows to be a swiss army knife, "something like n8n, but can drive codex through deterministic steps, nodes in a graph. or claude code. or pi. it uses acp..." But it had one problem. It was run from outside the harness, like a CI orchestrator I wanted to integrate acpx into pi. Because pi was the only CLI that could enable building of such a thing. But I wasn't sure how to reconcile a general ACP-based tool into a single coding agent I was being too accommodative of all the other harnesses, claude code, codex. I was trying to be too general I have changed my mind since then ACP is great and lets you integrate a harness into other software in cool ways But maybe, if a harness is proprietary, does not accept outside contributions, or does not even support ACP, maybe, it does not deserve cool features 😤 (they know who they are) So I ripped out ACP, and built it natively, only for pi No need for a web viewer... Just view it in a native widget, right inside pi! I cannot put into words how awesome it is to be able to do this! I am still tinkering, discovering. It is at osolmaz/pi-workflows if you want to take a look

Onur Solmaz

16,970 görüntüleme • 6 gün önce

I just built a content engine in Claude Code that writes blog posts in your brand's exact voice 🤯 One Claude plugin runs the whole content workflow: brand voice, research, writing, AI-slop scoring, and repurposing into social. It writes in YOUR voice, refuses to fabricate stats, and scores every draft 0-100. All inside Claude Code. So I pointed it at Grüns, one of the sharpest DTC brands out there. I fed it their homepage. In seconds it built a brand-voice profile, their playful anti-hype tone, the "Rip. Tip. Enjoy." cadence, the AG1-switcher audience, the 4.8★/100k-review proof. Then I asked for one post: "why your gut health controls your skin, hair, and energy." It came back publish-ready and scored 89/100 on the first pass: → Answer-first, with question headings AI engines can quote → Zero AI-slop phrases (no "unlock," no "in today's fast-paced world") → And it refused to invent a single stat, the fastest way to get a supplement brand demoted It sounded like Grüns wrote it, not ChatGPT. Perfect for e-comm operators and agencies who are sick of AI tools that all sound identical, $300 freelance posts that still need a rewrite, and content that reads like the slop Google now punishes. So I put together the full playbook to build your own. The complete guide to building this content engine in Claude Code: branded to you, tuned to your voice, repeatable across every client. The kind of post you'd pay a freelancer $300 for, written in minutes, in the brand's actual voice. What's inside: → The architecture (orchestrator + writer/editor/researcher agents) → How to capture any brand's voice into a reusable profile → The 0-100 scoring + AI-slop detection framework → The one-post-to-a-week-of-social repurposing loop → The full build, start to finish Want the playbook for free? > Like this post > Comment "CONTENT" And I'll send it over (must be following so I can DM)

Mike Futia

23,672 görüntüleme • 1 ay önce

tired: Claude Code ports my personal website to a new framework wired: Claude Code generates a command center UI where I can execute the port! with live feedback, including a side-by-side preview of old / new site 😎 this is an example of what I call an "AI HUD" -- a "heads-up display" that gives me visibility into what's going on. i can see: - what terminal commands are running - what files are being created on disk - a live running preview of the old / new website (!) this HUD was actually my third attempt at doing this task, and I liked it the best. here's why I landed there: I wanted to move from middleman to astro for my personal site. These are both static site generators that output html, so I suspected an AI agent could do a good job with a port -- since it could compare old / new build output and try to match. Attempt 1: Agent I just had Claude Code do the port. It went pretty well. But it was hard for me to review what had happened! The git diff was dozens of new files and it was hard to tell how they mapped to the old site. I think the LLM also tried directly writing some files rather than doing deterministic copying, which felt dangerous. Attempt 2: Script I realized a better approach was to have Claude Code write a script that would do the port. The script would execute shell commands like "copy all the markdown files from this directory into this other directory in the new site". This worked much better because I could review the *process* rather than the *results*. Still, even with a nicely commented script, it felt like I was doing a lot of work to review. I wondered: how could I make it ridiculously easy to review this? Attempt 3: HUD Enter the command center! This is an entire web app that I had Claude build just for this one task. I can click buttons to run each step of the port, and watch the new website gradually materialize. It has a node server that runs on my local machine that executes commands on my filesystem and coordinates dev servers for the old/new site. And then a web UI that talks to that server to visualize terminal commands, file trees, and live running previews. It's a HUD because I feel like I can ambiently see everything that the port process is doing 🧐 Was this whole thing worth making for this one-time task? I'm not sure, maybe it was overkill 😅 But it did help me feel more confident that I understood what was going on, and total time was still less than it would have taken me to do the whole port by hand! One way to look at this experience is: "AI can put absurd amounts of effort into a pull request description." What do I mean by that? Well, a PR description is a way to communicate a code change to a human. Typically we do that by writing a bit of text, because that's all we have time for. But given more time and effort, we can do better! An interactive command center / HUD can help a person understand what a code change is actually doing. Historically you'd never imagine investing the effort to do that for a single PR. But now it's within the realm of possibility. So, next time you have an agent do something for you, and you wish you understood better what it was doing, consider: instead of just asking for textual descriptions, maybe ask the agent to make you a HUD!

tired: Claude Code ports my personal website to a new framework wired: Claude Code generates a command center UI where I can execute the port! with live feedback, including a side-by-side preview of old / new site 😎 this is an example of what I call an "AI HUD" -- a "heads-up display" that gives me visibility into what's going on. i can see: - what terminal commands are running - what files are being created on disk - a live running preview of the old / new website (!) this HUD was actually my third attempt at doing this task, and I liked it the best. here's why I landed there: I wanted to move from middleman to astro for my personal site. These are both static site generators that output html, so I suspected an AI agent could do a good job with a port -- since it could compare old / new build output and try to match. Attempt 1: Agent I just had Claude Code do the port. It went pretty well. But it was hard for me to review what had happened! The git diff was dozens of new files and it was hard to tell how they mapped to the old site. I think the LLM also tried directly writing some files rather than doing deterministic copying, which felt dangerous. Attempt 2: Script I realized a better approach was to have Claude Code write a script that would do the port. The script would execute shell commands like "copy all the markdown files from this directory into this other directory in the new site". This worked much better because I could review the process rather than the results. Still, even with a nicely commented script, it felt like I was doing a lot of work to review. I wondered: how could I make it ridiculously easy to review this? Attempt 3: HUD Enter the command center! This is an entire web app that I had Claude build just for this one task. I can click buttons to run each step of the port, and watch the new website gradually materialize. It has a node server that runs on my local machine that executes commands on my filesystem and coordinates dev servers for the old/new site. And then a web UI that talks to that server to visualize terminal commands, file trees, and live running previews. It's a HUD because I feel like I can ambiently see everything that the port process is doing 🧐 Was this whole thing worth making for this one-time task? I'm not sure, maybe it was overkill 😅 But it did help me feel more confident that I understood what was going on, and total time was still less than it would have taken me to do the whole port by hand! One way to look at this experience is: "AI can put absurd amounts of effort into a pull request description." What do I mean by that? Well, a PR description is a way to communicate a code change to a human. Typically we do that by writing a bit of text, because that's all we have time for. But given more time and effort, we can do better! An interactive command center / HUD can help a person understand what a code change is actually doing. Historically you'd never imagine investing the effort to do that for a single PR. But now it's within the realm of possibility. So, next time you have an agent do something for you, and you wish you understood better what it was doing, consider: instead of just asking for textual descriptions, maybe ask the agent to make you a HUD!

Geoffrey Litt

63,101 görüntüleme • 11 ay önce

For months, I've been quietly building a prototype of something just because I want it to exist. Papyrus is a word processor, editor, proofreader, fact-checker, deep researcher, brainstorming partner, all in one. It takes your rough draft and helps you skip three revisions. Now I'm considering pivoting my whole team to build it out, but first, I need your vote. You email is your vote. LINK IN COMMENTS. I don't even care if you use some email you never look at and just use for sign ups. To me one email is one vote and says, go ahead and build this damn thing out and make it awesome. I built it because today's apps are the bloated dial-ups of writing (Word, GDocs). They've got a hundred freaking buttons I don't need and bury the ones I do need. Or they're AI marketing slop toys that promise to read my mind and pump out garbage. They just don't get the real work of writing and they don't get me. I want a clean, focused space with a real AI co-pilot. I don't need it to do the all the writing for me, just like I don't need Claude Code to do all the code for me. I want to work with it. I want a writing partner that acts like a full writing team on-call 24X7: proofreading, fact-checking, and running deep research in the background while I focus on the hard parts. I'm tired of cutting and pasting between a dozen tools so I started writing this thing. But won't the big guys just build something like this? Sure. But it will just bolt your ass into their ecosystem. Google Docs will force Gemini on you. Whatever office suite OpenAI pumps out will only use GPT. I want to use any model. Open or closed. They're commodities. The app is the thing. I want the best tool for the job, GPT-5, Kimi, Qwen, Claude, whatever comes tomorrow. I want a fluid, flexible workspace. I'm building this thing for people who've got critical thinking and who build, who don't want to outsource every damn thing to the machine. So if that's you and you believe this should exist, I really need your vote. Tell me to build it and I'll go all-in and make it a reality. Thanks for giving me a moment of your time.

For months, I've been quietly building a prototype of something just because I want it to exist. Papyrus is a word processor, editor, proofreader, fact-checker, deep researcher, brainstorming partner, all in one. It takes your rough draft and helps you skip three revisions. Now I'm considering pivoting my whole team to build it out, but first, I need your vote. You email is your vote. LINK IN COMMENTS. I don't even care if you use some email you never look at and just use for sign ups. To me one email is one vote and says, go ahead and build this damn thing out and make it awesome. I built it because today's apps are the bloated dial-ups of writing (Word, GDocs). They've got a hundred freaking buttons I don't need and bury the ones I do need. Or they're AI marketing slop toys that promise to read my mind and pump out garbage. They just don't get the real work of writing and they don't get me. I want a clean, focused space with a real AI co-pilot. I don't need it to do the all the writing for me, just like I don't need Claude Code to do all the code for me. I want to work with it. I want a writing partner that acts like a full writing team on-call 24X7: proofreading, fact-checking, and running deep research in the background while I focus on the hard parts. I'm tired of cutting and pasting between a dozen tools so I started writing this thing. But won't the big guys just build something like this? Sure. But it will just bolt your ass into their ecosystem. Google Docs will force Gemini on you. Whatever office suite OpenAI pumps out will only use GPT. I want to use any model. Open or closed. They're commodities. The app is the thing. I want the best tool for the job, GPT-5, Kimi, Qwen, Claude, whatever comes tomorrow. I want a fluid, flexible workspace. I'm building this thing for people who've got critical thinking and who build, who don't want to outsource every damn thing to the machine. So if that's you and you believe this should exist, I really need your vote. Tell me to build it and I'll go all-in and make it a reality. Thanks for giving me a moment of your time.

Daniel Jeffries

20,811 görüntüleme • 11 ay önce

Why did so many languages copy async/await from C#? Anders Hejlsberg(Anders Hejlsberg) - creator of TypeScript, C# & Turbo Pascal - on what they got right with the design: #1 - async/await was designed to solve a common problem in the event-loop model: "A lot of languages are built around cooperative multitasking in the sense that they have an event loop that sits and dispatches events. Then you handle the event and then you yield back to the event handler loop. And it all runs in a single thread cooperatively. The problem with that is if you then want to do some long running work: how do I stop in the middle of this piece of long running work and yield back to the event loop cooperatively? And then when my result is ready, I can come back and continue executing here." #2 - state machines are the solution, but hard to build: "Well, in order to do that in an inverted architecture like that, you have to build a state machine. State machines are notoriously hard for people to implement because you've got to move all of your state off of the stack into objects. And then you have this big case statement that envelopes your entire logic. It's a nightmare to figure out. But, the transformation from serially executing code into a state machine, its continuation-passing-style translation is actually one that you can do in a machine-based fashion." #3 - compilers are good at writing state machines: "You can have the compiler write the state machine if you introduce syntax that allows you to indicate where you want to yield. And that's what await is. Await is basically saying, I want to yield here, and I want to yield this promise, and then when the promise completes, I want you to come back here and continue executing. Then the compiler writes a state machine around it and it actually turns it into this big switch statement and moves all of the state that survives across the await into something that's heap allocated. So it can be brought back. And doing all of that work is something that compilers are great at. And so that was sort of the idea that we have this new style of programming where we're using promises or the equivalent of promises and the ability to yield and then we have callbacks. But trying to write your program in that style, that's also what JavaScript suffered from a lot. It's like all this callback style stuff. With Async and Await, you get the illusion that you're just writing normal sequential code and then the compiler does the painful transformation for you. That turns out to be really useful."

Why did so many languages copy async/await from C#? Anders Hejlsberg(Anders Hejlsberg) - creator of TypeScript, C# & Turbo Pascal - on what they got right with the design: #1 - async/await was designed to solve a common problem in the event-loop model: "A lot of languages are built around cooperative multitasking in the sense that they have an event loop that sits and dispatches events. Then you handle the event and then you yield back to the event handler loop. And it all runs in a single thread cooperatively. The problem with that is if you then want to do some long running work: how do I stop in the middle of this piece of long running work and yield back to the event loop cooperatively? And then when my result is ready, I can come back and continue executing here." #2 - state machines are the solution, but hard to build: "Well, in order to do that in an inverted architecture like that, you have to build a state machine. State machines are notoriously hard for people to implement because you've got to move all of your state off of the stack into objects. And then you have this big case statement that envelopes your entire logic. It's a nightmare to figure out. But, the transformation from serially executing code into a state machine, its continuation-passing-style translation is actually one that you can do in a machine-based fashion." #3 - compilers are good at writing state machines: "You can have the compiler write the state machine if you introduce syntax that allows you to indicate where you want to yield. And that's what await is. Await is basically saying, I want to yield here, and I want to yield this promise, and then when the promise completes, I want you to come back here and continue executing. Then the compiler writes a state machine around it and it actually turns it into this big switch statement and moves all of the state that survives across the await into something that's heap allocated. So it can be brought back. And doing all of that work is something that compilers are great at. And so that was sort of the idea that we have this new style of programming where we're using promises or the equivalent of promises and the ability to yield and then we have callbacks. But trying to write your program in that style, that's also what JavaScript suffered from a lot. It's like all this callback style stuff. With Async and Await, you get the illusion that you're just writing normal sequential code and then the compiler does the painful transformation for you. That turns out to be really useful."

The Pragmatic Engineer

13,258 görüntüleme • 1 ay önce

Still relying on AI tools that can’t turn your ideas into real, working apps? Most can write code snippets but fall apart when it’s time to actually build something complete. That’s where Replit ⠕ changes everything. I simply asked it: “Build a responsive calculator app with a clean UI in light/dark mode.” Within minutes, it built the entire app with a beautiful UI, logic, light/dark mode, animations, and full responsiveness. Literally no setup. No debugging headache. Just vibe coding. Here’s why Replit stands out 👇 ✅ Build in Plain English: Just describe what you want and Replit turns it into a production-ready app. ✅ All-in-One Platform: Code, AI help, hosting, auth, and database, everything you need, already built in. ✅ Vibe Code Anywhere: Build on the go with the Replit mobile app for iOS & Android. ✅ Connected Ecosystem: Integrate with tools you already use like Notion, Slack, Google Drive, Dropbox, and more. ✅ Design to Live App: Import directly from Figma and bring your ideas to life in minutes. No micromanaging. No chaos. Just you, your idea, and Replit doing the heavy lifting. 👉 Try it now: 🎁 Get $10 credit when you purchase Replit Core via my referral link. → #Replit #VibeCoding #AIApps #NoCode #BuildWithReplit #AItools #ReplitCore

Still relying on AI tools that can’t turn your ideas into real, working apps? Most can write code snippets but fall apart when it’s time to actually build something complete. That’s where Replit ⠕ changes everything. I simply asked it: “Build a responsive calculator app with a clean UI in light/dark mode.” Within minutes, it built the entire app with a beautiful UI, logic, light/dark mode, animations, and full responsiveness. Literally no setup. No debugging headache. Just vibe coding. Here’s why Replit stands out 👇 ✅ Build in Plain English: Just describe what you want and Replit turns it into a production-ready app. ✅ All-in-One Platform: Code, AI help, hosting, auth, and database, everything you need, already built in. ✅ Vibe Code Anywhere: Build on the go with the Replit mobile app for iOS & Android. ✅ Connected Ecosystem: Integrate with tools you already use like Notion, Slack, Google Drive, Dropbox, and more. ✅ Design to Live App: Import directly from Figma and bring your ideas to life in minutes. No micromanaging. No chaos. Just you, your idea, and Replit doing the heavy lifting. 👉 Try it now: 🎁 Get $10 credit when you purchase Replit Core via my referral link. → #Replit #VibeCoding #AIApps #NoCode #BuildWithReplit #AItools #ReplitCore

Manish Kumar Shah

52,314 görüntüleme • 8 ay önce

I just built a Reddit research agent in Claude Code that turns real customer complaints into ad angles 🤯 It scrapes the threads where people actually rant about your category, reads every post and comment, and hands you back a dashboard of pain points, exact customer phrases, and ready-to-test ad angles. All inside Claude Code. Perfect for DTC brands and agencies who want ad angles pulled from real customer language, not guessed in a vacuum. Reddit is the most honest focus group on earth. People say things there they'd never put in a survey or a review with a brand watching. So if you're writing hooks off your own assumptions — or digging through Reddit by hand, opening tab after tab, pasting quotes into a doc... This agent runs the entire loop: → Give it a product or category + a couple of subreddits → It searches Reddit for the threads where people actually discuss the problem → Pulls every post and comment → Claude reads all of it and finds the patterns → Builds a dashboard: pain points, desires, objections, and swipe-worthy phrases No manual scrolling. No pasting quotes into docs. No guessing what your customers actually care about. What you get: → Ranked customer pain points, each with a real verbatim quote → The exact language your customers use, ready to drop into ad copy → Objections and buying triggers pulled straight from the threads → 8-10 ready-to-test ad angles built from all of it Built 100% in Claude Code. Want the skill file for free? > Like this post > Comment "REDDIT" And I'll send it over (must be following so I can DM)

Mike Futia

45,624 görüntüleme • 1 ay önce

just built something fun: and it’s 100% free for founders story time - back in college i built a dating app. making ok money from ads, nothing crazy. one day, random email hits our help inbox: "interested in acquiring your site, wanna chat?” It was a brazilian company. It was only by some random chance that I was in that support inbox. Thank god. turned into life-changing exit offer (at least it felt like that at the time). classic right place right time situation. got me thinking: why isn't there an easy way for buyers to find sellers? Wouldn’t it be cool to sell your business to someone just browsing? so i built offerbutton - one line of code that lets anyone make an offer to buy your business: that's it. embed it, forget it, wait for offers. built this entire thing with v0/cursor because everyone said "ai coding isn't ready for real products" prove them wrong i guess? Offerbutton is perfect for: - indie hackers with projects - creators with media properties - saas founders testing exit interest - anyone building in public works for deals $1k to $10m+. 100% free to embed. no fees. no commitment. It’s free for now for the first people who install it. try it: oh, and here is a video i made with AI mostly. I had fun doing it. why i think offerbutton could be cool too many great products die because founders/buyers never find each other. let's fix that. who's got something to sell?

just built something fun: and it’s 100% free for founders story time - back in college i built a dating app. making ok money from ads, nothing crazy. one day, random email hits our help inbox: "interested in acquiring your site, wanna chat?” It was a brazilian company. It was only by some random chance that I was in that support inbox. Thank god. turned into life-changing exit offer (at least it felt like that at the time). classic right place right time situation. got me thinking: why isn't there an easy way for buyers to find sellers? Wouldn’t it be cool to sell your business to someone just browsing? so i built offerbutton - one line of code that lets anyone make an offer to buy your business: that's it. embed it, forget it, wait for offers. built this entire thing with v0/cursor because everyone said "ai coding isn't ready for real products" prove them wrong i guess? Offerbutton is perfect for: - indie hackers with projects - creators with media properties - saas founders testing exit interest - anyone building in public works for deals $1k to $10m+. 100% free to embed. no fees. no commitment. It’s free for now for the first people who install it. try it: oh, and here is a video i made with AI mostly. I had fun doing it. why i think offerbutton could be cool too many great products die because founders/buyers never find each other. let's fix that. who's got something to sell?

GREG ISENBERG

129,422 görüntüleme • 1 yıl önce

everyone in iOS development should watch this. seriously, it might change the whole industry. i pointed claude code at a live ios device running on revyl, typed "test everything," and walked away. here's what's actually happening: ① you don't write the tests. no scripts, no selectors, no test plan. i never told it which screens to open or what to check. it read the app, decided what mattered, and tested it. the entire instruction was "test everything." ② it built its own test team. it looked at the app, clocked that it's basically four mini apps (rides, delivery, services, account), and split itself into 4 agents, one per surface. scoping coverage like that is usually a person's whole afternoon. it did it in seconds, unprompted. ③ all four ran at the same time, each on its own live device. this is where revyl comes in. every agent gets its own live ios session in the cloud, so four running apps get tested in parallel instead of taking turns on one simulator. serial testing turns coverage into a time tax. running all of it at once removes the tax. ④ it tests like a person, not like a script. each agent drives the app the way a user would, taps through the flows, and visually checks each screen against what it expected to see. nothing is pinned to a brittle element id, so renaming a button doesn't take down half your suite. that one detail is the most annoying thing about how we test today, and it just quietly goes away. ⑤ no xcuitest, no sims melting your laptop. i didn't write a single xcuitest script, and there were no simulators booting on my machine. the agents run on cloud devices, so coverage stops being capped by what your laptop can handle. the part that got me isn't that an agent tested an app. it's that i never told it how. i handed it a device and an intent, and it figured out the scoping, the parallelizing, and the driving on its own. if you still write and maintain mobile ui tests by hand, i'm not sure that lasts the year.

everyone in iOS development should watch this. seriously, it might change the whole industry. i pointed claude code at a live ios device running on revyl, typed "test everything," and walked away. here's what's actually happening: ① you don't write the tests. no scripts, no selectors, no test plan. i never told it which screens to open or what to check. it read the app, decided what mattered, and tested it. the entire instruction was "test everything." ② it built its own test team. it looked at the app, clocked that it's basically four mini apps (rides, delivery, services, account), and split itself into 4 agents, one per surface. scoping coverage like that is usually a person's whole afternoon. it did it in seconds, unprompted. ③ all four ran at the same time, each on its own live device. this is where revyl comes in. every agent gets its own live ios session in the cloud, so four running apps get tested in parallel instead of taking turns on one simulator. serial testing turns coverage into a time tax. running all of it at once removes the tax. ④ it tests like a person, not like a script. each agent drives the app the way a user would, taps through the flows, and visually checks each screen against what it expected to see. nothing is pinned to a brittle element id, so renaming a button doesn't take down half your suite. that one detail is the most annoying thing about how we test today, and it just quietly goes away. ⑤ no xcuitest, no sims melting your laptop. i didn't write a single xcuitest script, and there were no simulators booting on my machine. the agents run on cloud devices, so coverage stops being capped by what your laptop can handle. the part that got me isn't that an agent tested an app. it's that i never told it how. i handed it a device and an intent, and it figured out the scoping, the parallelizing, and the driving on its own. if you still write and maintain mobile ui tests by hand, i'm not sure that lasts the year.

Landseer Enga

23,963 görüntüleme • 1 ay önce

I've been building a music player with Next.js for fun. Here's a quick demo of how it works (it's open source!) • Demo: • Code: If you want to learn more about how it's built, here's more details ↓ I'm using Postgres (with Drizzle) to store information about the songs and playlists. Audio and image files are stored in Vercel Blob (object storage), and the URLs are then referenced in the database. For the UI, I'm using shadcn/ui (so Tailwind CSS and Radix). This made it easy to copy/paste in some nice components, like the dropdown menus. I built the entire first version of the UI in v0 and then iterated from there, feeding it my Drizzle schema as a source in the project and having it scaffold some of the boilerplate for me: I added support for keyboard navigation (using arrow keys) or vim motions (j/k to go up/down, and h/l to go between playlists and tracks). Also, space to toggle the now playing song, and / to focus the search input. The search function has a nice utility to highlight the currently searched text on the page in yellow. Then, I was exploring how to pass metadata from my application to macOS or iOS. Turns out there's an API for that – MediaSession. Web apps can share metadata about what media is playing (title, artist, album artwork) and sync play/pause/seek with system media controls. Works across modern browsers — even integrates with iOS dynamic island and shows up on lock screens: I set up my app like a PWA – it has a manifest.json file, so it can be installed to my iOS home screen or added to my dock on macOS. On iOS, it then uses the full screen height `100dvh` (dynamic viewport) and has padding on the bottom for the safe area with the `env()` CSS function. Finally, I was able to use the Vercel AI SDK in a script to clean up the metadata on audio files I downloaded from YouTube. Bonus: I even was able to dogfood the React Compiler, which helped me fix a performance bug! That's all! It's fun to make personal software:

I've been building a music player with Next.js for fun. Here's a quick demo of how it works (it's open source!) • Demo: • Code: If you want to learn more about how it's built, here's more details ↓ I'm using Postgres (with Drizzle) to store information about the songs and playlists. Audio and image files are stored in Vercel Blob (object storage), and the URLs are then referenced in the database. For the UI, I'm using shadcn/ui (so Tailwind CSS and Radix). This made it easy to copy/paste in some nice components, like the dropdown menus. I built the entire first version of the UI in v0 and then iterated from there, feeding it my Drizzle schema as a source in the project and having it scaffold some of the boilerplate for me: I added support for keyboard navigation (using arrow keys) or vim motions (j/k to go up/down, and h/l to go between playlists and tracks). Also, space to toggle the now playing song, and / to focus the search input. The search function has a nice utility to highlight the currently searched text on the page in yellow. Then, I was exploring how to pass metadata from my application to macOS or iOS. Turns out there's an API for that – MediaSession. Web apps can share metadata about what media is playing (title, artist, album artwork) and sync play/pause/seek with system media controls. Works across modern browsers — even integrates with iOS dynamic island and shows up on lock screens: I set up my app like a PWA – it has a manifest.json file, so it can be installed to my iOS home screen or added to my dock on macOS. On iOS, it then uses the full screen height `100dvh` (dynamic viewport) and has padding on the bottom for the safe area with the `env()` CSS function. Finally, I was able to use the Vercel AI SDK in a script to clean up the metadata on audio files I downloaded from YouTube. Bonus: I even was able to dogfood the React Compiler, which helped me fix a performance bug! That's all! It's fun to make personal software:

Lee Robinson

118,242 görüntüleme • 1 yıl önce

I just vibe-coded a complete SEO Agency In a Box with Claude Code. One keyword in → full research, competitor analysis, SEO-optimized article, metadata, and AI graphics out. All on auto-pilot. Perfect for SEO agencies and DTC brands who are tired of spending an entire day producing a single piece of SEO content. Creating quality SEO content is a huge pain. You're reading competitor articles one by one, trying to find content gaps, writing drafts from scratch, then going back to optimize everything before you even think about graphics or metadata. This vibe-coded tool solves it: → Set up your brand once (value prop, tone of voice, writing samples) → Enter a topic and keywords → SERP API + Firecrawl scrape and analyze the top-ranking competitors → Gemini generates a full research plan with intent, gaps, and strategic positioning → Claude writes the article based on your brand guidelines and the research → Nano Banana Pro generates thumbnail and in-blog images → SEO metadata (title, description, slug) created automatically What this outputs: - Full competitive research and content brief - SEO-optimized articles with internal links and proper formatting - AI-generated images and thumbnail - Meta title, description, and slugs - Batch mode for multiple articles at once - Content rewrite mode for existing URLs that aren't ranking - LinkedIn and X repurposing built in Built 100% in Claude Code. (I'm giving away the prompts) I recorded a full walkthrough showing exactly how every part of this works, and I'm including ALL of the prompts I used for Claude Code. Want access for free? > Like this post > Comment "SEO" And I'll send it over (must be following so I can DM)

Mike Futia

68,435 görüntüleme • 5 ay önce

It has been a long time since I made a video. I am sharing a deep dive into 2fac, a new 2FA app I built to replace Authy. What makes this project special is its massive scope, running natively across Android, iOS, watchOS, desktop, CLI, browser extensions, and the web. Building this many features across so many platforms was only possible through agentic coding. Huge thanks to Copilot, Claude, OpenCode, and Pi for completely changing how I write software. Here is what is covered in the video. In the pre-AI world, so many features, taking it to such a polished state (ui, design, relialibility of how it works, and quality of code too, you can take a look for yourelf) single handedly, that too working on spare time on the side from a day job, was simply not possible for non 10x, mid engineers like me 00:00:00 Project Overview & Motivation 00:03:31 Android App Demo 00:04:19 iOS & watchOS App Demo 00:05:32 Desktop App Demo 00:06:05 System Tray Integration 00:07:05 CLI Demo 00:08:44 Browser Extension Demo 00:10:00 Web App (PWA) Demo 00:11:40 Secure Unlock & Passkeys 00:16:30 GitHub Repo & Release Plans 00:17:30 CI/CD Pipeline Setup 00:19:00 AI Agentic Coding Workflow 00:23:50 Production Usage Warning 00:26:00 Custom AI Agent Skills 00:28:30 Automated Planning & Roadmaps 00:31:14 UI Testing with Maestro 00:35:12 Creating Custom AI Agents 00:38:34 Codebase Test Coverage 00:41:30 AI-Driven TDD

It has been a long time since I made a video. I am sharing a deep dive into 2fac, a new 2FA app I built to replace Authy. What makes this project special is its massive scope, running natively across Android, iOS, watchOS, desktop, CLI, browser extensions, and the web. Building this many features across so many platforms was only possible through agentic coding. Huge thanks to Copilot, Claude, OpenCode, and Pi for completely changing how I write software. Here is what is covered in the video. In the pre-AI world, so many features, taking it to such a polished state (ui, design, relialibility of how it works, and quality of code too, you can take a look for yourelf) single handedly, that too working on spare time on the side from a day job, was simply not possible for non 10x, mid engineers like me 00:00:00 Project Overview & Motivation 00:03:31 Android App Demo 00:04:19 iOS & watchOS App Demo 00:05:32 Desktop App Demo 00:06:05 System Tray Integration 00:07:05 CLI Demo 00:08:44 Browser Extension Demo 00:10:00 Web App (PWA) Demo 00:11:40 Secure Unlock & Passkeys 00:16:30 GitHub Repo & Release Plans 00:17:30 CI/CD Pipeline Setup 00:19:00 AI Agentic Coding Workflow 00:23:50 Production Usage Warning 00:26:00 Custom AI Agent Skills 00:28:30 Automated Planning & Roadmaps 00:31:14 UI Testing with Maestro 00:35:12 Creating Custom AI Agents 00:38:34 Codebase Test Coverage 00:41:30 AI-Driven TDD

Arnav Gupta

109,380 görüntüleme • 4 ay önce