Loading video...

Video Failed to Load

Go Home

As no-code design tools become more common, so do the pitfalls. You know what they look like - the purple gradients, annoying hover effects, sections that fade as you scroll. So how do you avoid a site that feels vibe coded while still taking advantage of these new tools?...

84,834 views • 8 months ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Magic Patterns (W23) is one of the fastest-growing design tools in AI, helping product teams turn ideas into interactive, code-backed prototypes in minutes. Alex Danilowicz and his co-founder, both front-end engineers, built Magic Patterns to solve a problem they had themselves: finding a better way to turn ideas into something visual. They were among the first teams building prompt-to-design tools back in 2023. In this episode of Design Review, Alex joins YC’s Aaron Epstein to demo Magic Patterns and its new MagicOS canvas, where teams can bring together prompts, images, PRDs, and other context to explore ideas visually. Then they review a handful of startup websites to break down what makes a site feel “vibe coded,” where founders go wrong, and how to make AI-generated design feel more intentional. 02:11 — From YC Pivot to Product-Market Fit 03:44 — Staying Ahead as AI Design Tools Improve 04:37 — Demo: Designing With Magic Patterns 09:52 — MagicOS 11:23 — Designing With Context on a Canvas 14:50 — How to Get Better Results From AI Design Tools 15:35 — How Far Can AI-Generated Design Go? 18:17 — Website Review 1: Ego 23:59 — Website Review 2: Sentient OS 32:01 — Website Review 3: Cerenovus 36:59 — Website Review 4: Slashy 43:33 — How to Develop Better Design Taste 44:20 — Why Everyone at Magic Patterns Talks to Users 45:07 — Balancing Speed and Design Quality 46:07 — The Future of Design and Magic Patterns

Y Combinator

35,565 views • 21 days ago

These are my essential AI coding skills I use to keep code quality high and not bloated when AI writes and merges my code for me. This is video 5 of 7 in my “how to become a 10x ai-native developer” series, and in the first 4 videos I talked about how I use cloud agents be a 24/7 on call engineer for me that fixes bugs for me while I sleep by using verification skills to verify all the code changes actually work as intended and how they merge the code for me without me reviewing the code, and as a result I have a lot of code being merged without my supervision. I know a lot of you are wondering, how do you keep the code quality high when letting AI write so much code? I do so by deferring to skills to do that. I use the cursor team’s thermo nuclear code quality review (excessive, I know) in conjunction with framework specific tools like a react best practices skill and with , one of my personal favorites, the ponytail skill. Highly recommend you check out the ponytail.dev website which is the home for the skill it is so funny and I’ll show a little screenshot right here, but essentially I have these sets of skills to point out common pitfalls of overly verbose and complicated code and I tell all my coding agents to run these skills before making the PR and sometimes I tell them to run these simplification skills multiple times in a row. Due to the non deterministic nature of LLMs, forcing them to run these simplification skills multiple times allow these models to uncover new simplification methods that it didn’t catch the previous try. #coding #ai #developer

YourAverageTechBro

171,500 views • 1 month ago