正在加载视频...

视频加载失败

I hated how bad agents are at design I hated how Codex can't access Mobbin So I created Lazyweb - 257k+ screens (apps/web) - 6 opinionated design research skills - 1 MCP (Claude/Codex) 100% Free...AI native...no rate limits...no subscriptions.. Enjoy (and tell a friend) 🫡

352,869 次观看 • 2 个月前 •via X (Twitter)

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

Claude Fable 5 + Claude Design is f*cking insane 🤯 Anthropic just dropped its most intelligent model ever, and the first thing I pointed it at was email design. I built a complete email campaign design in Claude Design, and the difference is night and day: tighter layouts, cleaner hierarchy, on-brand from the first generation. All inside Claude Design with Fable 5. Perfect for DTC brands and agencies who are still paying email agencies $3-5K/month for campaign designs that take 2 weeks to ship. If your campaign calendar is packed but every new email means briefing a designer, waiting on mockups, sending notes, and waiting again... This workflow eliminates the entire bottleneck: → Load your brand design system into Claude Design once (colors, fonts, logo, button styling) → Switch the model to Claude Fable 5 — Anthropic's new state-of-the-art model with the best vision of any AI → Prompt the campaign email section by section: header, hero, headline, offer block, CTA → Fable 5 nails layout and brand details that older models fumbled → Iterate inline — swap images, adjust styling, color-pick directly in the canvas → Export the finished email and hand off to your ESP No briefing a designer. No 2-week turnaround on a single campaign. No paying an agency $4K/month for 4 emails. What you get: → Campaign emails designed in minutes, not weeks → A reusable design system every new email pulls from automatically → Noticeably smarter design decisions from Fable 5's upgraded vision → Full inline editing before anything touches your ESP Built 100% with Claude Design + Claude Fable 5. I recorded a full walkthrough showing exactly how this works. Want it for free? > Like this post > Comment "FABLE" And I'll send it over (must be following so I can DM)

Mike Futia

42,556 次观看 • 1 个月前

Claude Design + Shopify is f*cking ridiculous 🤯 You can now publish pages from Claude Design → Claude Code → Shopify. Built 100% with Claude Design, Claude Code, and the Shopify CLI. Perfect for DTC brands and agencies who want to skip the design → dev handoff entirely. Here's how it works: → Design any landing page in Claude Design → Export as a zip and drop it into Claude Code → Install the Shopify + Shopify AI Toolkit plugins → Prompt Claude to convert the HTML into a Shopify page template + push to live theme → Claude uploads the images, deploys the files, and creates a published page No more handing designs off to a dev and waiting 2 weeks for a Shopify page. What you get: - A workflow that turns any Claude Design page into a real Shopify page template - Editable sections so your marketing team can swap copy, images, and CTAs without code - Images uploaded straight to Shopify Files automatically - A files-only deploy that only touches what's new in your live theme - A repeatable pipeline you can use every time you design a new landing page This is essentially the design-to-deploy pipeline brands have been waiting for. I put together a step-by-step playbook for going from Claude Design → published Shopify page. Every install, every plugin, every command, and the exact prompt that runs the whole thing. Want the playbook for free? > Like this post > Comment "SHOP" And I'll send it over (must be following so I can DM)

Mike Futia

56,183 次观看 • 2 个月前

HTML Artifacts are a big part of how I work with agents now. Artifacts can be more than just static files. When combined with agents, they can take action or help you take action. This unlocks all kinds of interesting ways to work with agents. This is clearly the future. Check out this writing and scheduler artifact I built in a few minutes. It uses a bit of HTML and JS. All the data is in markdown (Obsidian vaults), so the agent can access and modify it at any time. No DB needed. No sophisticated functionalities. The agent decides all that for me based on the skills, context, and memory it has access to. The best part about this simple stack is that all the important information stays with me. This has allowed me to build a recursive self-improving system and automations that can better tap into coding agents like Codex or Claude Code. I could have paid or built an entire app for scheduling posts, and there are so many of them out there. But I don't need to. I've realized a simple artifact does the job. And the simplicity of it is actually an advantage. Very little maintenance for very high returns on personalization, time, and efficiency. The other benefit of this is that I can add features as I please. That level of personalization feels magical, and we should all be pursuing more of it. All of this just keeps compounding. Of course, this example is just about writing. But I have similar artifacts for research, design, experimentation, evaluation, and so much more. And no, I didn't actually publish the post example I shared in the clip. It was just for demonstration purposes. I actually spend more time than this when writing together with agents. Lastly, having built my own agent orchestrator tool has made me realize that simplifying the tool stack is a superpower. If you are curious about how all this works, I will do a live session next week:

elvis

18,374 次观看 • 2 个月前

Claude Design is f*cking cracked for landing pages 🤯 Find any competitor's e-com lander → feed it to Claude Design w/ your brand's design system → get back a fully rebuilt version in your brand, your copy, your design. All inside Claude Design. Perfect for DTC brands and agencies who are still paying freelancers to build advertorial pages from scratch. If you're finding landers that have been running on Meta for 6+ months and want to test the same structure for your brand —> Briefing a designer, waiting a week, getting back a flat mockup, giving notes, waiting again... Claude Design eliminates the entire loop: → Use Go Full Pag to screenshot the full competitor lander → Feed it to Claude Design with your design system → Prompt it to extract the exact section structure and rebuild it for your brand → It rewrites all copy, applies your fonts, colors, and layout → Iterate section by section — send a screenshot of what you want to fix, it fixes it → Drop in your product images and founder photos as you go No designer. No back-and-forth briefs. No starting from scratch. What you get: -> Full production-ready lander built around a proven structure that's already converting on Meta -> Live elements (countdown timers, animated sections) auto-generated -> Mobile and desktop versions you can refine with plain-English prompts -> A repeatable system — new competitor, new screenshots, same pipeline I put together a full playbook breaking down the exact process — the prompts, the section-by-section editing approach, and how to set this up for any competitor lander. Want it completely for free? > Like this post > Comment "CLONE" And I'll send it over (must be following so I can DM)

Mike Futia

37,592 次观看 • 1 个月前

Claude Code + Google Stitch 2.0 is f*cking cracked 🤯 Google just dropped a free AI design agent that solves Claude Code's biggest weakness: frontend design. One screenshot of a high-converting landing page → a production-ready site for your brand in minutes. All inside Google Stitch + Claude Code. Perfect for DTC brands and agencies who are building advertorial pages and product launch pages for Meta but burning days on designer back-and-forth. If you're running Meta ads and need 5-10 different landing pages testing different hooks, angles, and offers — each one targeting a different audience and pain point — you know the bottleneck isn't the ads. It's the pages. Briefing designers, waiting for revisions, paying $2-5K per page. Stitch eliminates the design bottleneck: → Find a high-converting advertorial that's scaling on Meta → Screenshot it and drop it into Stitch (powered by Gemini 3.1) → Stitch redesigns it with your brand's colors, fonts, and imagery using Nano Banana 2 → Edit sections visually — headlines, CTAs, layouts — without touching code → Export the code and paste it into Claude Code → Claude builds the full production site and deploys to Vercel or Netlify in 60 seconds No designer. No $3K per landing page. No Claude Code frontend that looks like a template from 2019. What you get: → Designer-quality landing pages and advertorials built in minutes, not weeks → Visual editing so you actually see the design before you code it → Nano Banana 2 generating on-brand product imagery and hero shots → A repeatable system — new angle, new page, same pipeline Built 100% with Google Stitch 2.0 + Claude Code. I put together a full playbook showing the exact workflow: how to find winning pages, redesign them in Stitch, and deploy with Claude Code. Want it for free? > Like this post > Comment "STITCH" And I'll send it over (must be following so I can DM)

Mike Futia

125,557 次观看 • 3 个月前

I just built a complete SEO audit plugin in Claude Code that replaces your $200/mo Ahrefs subscription 🤯 One Claude Plugin audits any store: technical SEO, product schema, content, Core Web Vitals, and AI-search readiness. Parallel agents, a 0-100 score, and a dashboard that renders right in the panel. All inside Claude Code. So I pointed it at Ridge .com, one of the sharpest DTC operators out there. It came back 56/100, and what stood out wasn't a knock on them at all: Ridge has a better AI-commerce setup than 99% of stores. A real llms.txt, an agent-discovery sitemap, a live MCP endpoint, genuinely ahead of the curve. And even on a store that dialed-in, the audit surfaced fixable gaps in ~90 seconds: → Room to add product structured data → A mobile Core Web Vitals score worth tightening → A thin meta description on a high-traffic collection Perfect for e-comm operators and SEO agencies who are sick of paying $200/mo for tools that bury the real issues, running quarterly audits that take a week, and shipping reports nobody can act on. So I put together the full playbook to build your own. The complete guide to building this Plugin in Claude Code: branded to you, tuned to exactly how you audit, repeatable across every client. The kind of audit you run in minutes and hand over as a deliverable that looks like it cost thousands. What's inside: → The architecture (orchestrator + parallel sub-agents) → How to fetch any store past Cloudflare → The 0-100 scoring + falsifiable-findings framework → How to ship the HTML dashboard for client demos → The full build, start to finish Want the playbook for free? > Like this post > Comment "SEO" And I'll send it over (must be following so I can DM)

Mike Futia

55,266 次观看 • 1 个月前

I had the same thought so I've been playing with it in nanochat. E.g. here's 8 agents (4 claude, 4 codex), with 1 GPU each running nanochat experiments (trying to delete logit softcap without regression). The TLDR is that it doesn't work and it's a mess... but it's still very pretty to look at :) I tried a few setups: 8 independent solo researchers, 1 chief scientist giving work to 8 junior researchers, etc. Each research program is a git branch, each scientist forks it into a feature branch, git worktrees for isolation, simple files for comms, skip Docker/VMs for simplicity atm (I find that instructions are enough to prevent interference). Research org runs in tmux window grids of interactive sessions (like Teams) so that it's pretty to look at, see their individual work, and "take over" if needed, i.e. no -p. But ok the reason it doesn't work so far is that the agents' ideas are just pretty bad out of the box, even at highest intelligence. They don't think carefully though experiment design, they run a bit non-sensical variations, they don't create strong baselines and ablate things properly, they don't carefully control for runtime or flops. (just as an example, an agent yesterday "discovered" that increasing the hidden size of the network improves the validation loss, which is a totally spurious result given that a bigger network will have a lower validation loss in the infinite data regime, but then it also trains for a lot longer, it's not clear why I had to come in to point that out). They are very good at implementing any given well-scoped and described idea but they don't creatively generate them. But the goal is that you are now programming an organization (e.g. a "research org") and its individual agents, so the "source code" is the collection of prompts, skills, tools, etc. and processes that make it up. E.g. a daily standup in the morning is now part of the "org code". And optimizing nanochat pretraining is just one of the many tasks (almost like an eval). Then - given an arbitrary task, how quickly does your research org generate progress on it?

Andrej Karpathy

1,641,461 次观看 • 4 个月前

Building a personal knowledge base for my agents is increasingly where I spend my time these days. Like Andrej Karpathy, I also use Obsidian for my MD vaults. What's different in my approach is that I curate research papers on a daily basis and have actually tuned a Skill for months to find high-signal, relevant papers. I was reviewing and curating papers manually for some time, but now it's all automated as it has gotten so good at capturing what I consider the best of the best. There are so many papers these days, so this is a big deal. You all get to benefit from that with the papers I feature in my timeline and on DAIR.AI. The papers are indexed using tobi lutke qmd cli tool (all of it in markdown files along with useful metadata). So good for semantic search and surfacing insights, unlike anything out there. I am a visual person, so I then started to experiment with how to leverage this personal knowledge base of research papers inside my new interactive artifact generator (mcp tools inside my agent orchestrator system). The result is what you see in the clip. 100s of papers with all sorts of insights visualized. I keep track of research papers daily, so believe me when I tell you that this system is absolutely insane at surfacing insights. This is the result of months of tinkering on how to index research and leverage agent automations for wikification and robust documentation. But this is just the beginning. The visual artifact (which is interactive too) can be changed dynamically as I please. I can prompt my agent to throw any data at it. I can add different views to the data. Different interactions. I feel like this is the most personalized research system I have ever built and used, and it's not even close. The knowledge that the agents are able to surface from this basic setup is already extremely useful as I experiment with new agentic engineering concepts. I feel like this knowledge layer and the higher-level ones I am working on will allow me to maximize other automation tools like autoresearch. The research is only as good as the research questions. And the research questions are only as good as the insights the agents have access to. Where I am spending time now is on how to make this more actionable. I am obsessed about the search problem here. The automations, autoresearch, ralph research loop (I built one months ago) are easier to build but are only as good as what you feed them. Work in progress. More updates soon. Back to building.

elvis

464,070 次观看 • 3 个月前

There’s a feeling of “wtf is a designer anymore” floating around… I felt it while scrolling Reddit after Figma Make was announced 😬 For some people it simply didn’t compute that a code prototype could be a design artifact. But I’ll let you in on a little secret… A few days ago I visited a well-known design leader and he said that in the last 6 months, ~40% of their team's design artifacts are now created in Lovable, Bolt, etc. That’s kind of crazy, right? It's a big reason why Ioana Teleanu (1st AI designer at Miro) said design is "in the middle of an identity crisis" So Ioana and I went deep into this topic during today's episode and I want to share a few ideas I’m still thinking about: ——— We’re in a weird moment in history where there are AI designers and non-AI designers. But this is a blip on the timeline as adoption accelerates. The idea of "AI designer" won't exist in the future Here's what Ioana said 👇 “We’re all gonna be thinking about some sort of AI angle in the way we do our work. I don’t even feel that the AI design role will exist in this explicit format in a couple of years. All the designers will be AI designers” I want to make something clear though... Ioana described herself as generally “change averse” and the type of person who "DOESN'T jump on new things" That’s why her initial approach to AI was a bit less intentional… But now she’s changed her tune: “We have a moral duty to experiment with these technologies because we're designers and we should be curious about the world, and we should be curious about the future.” The cost of ignoring new technology has never been higher So if you’re interested in what it looks like to design AI experiences within your existing product then I think you’ll really enjoy this week's episode Ioana shares a ton of lessons learned from Miro and frameworks for how she helps clients integrate AI effectively 👇

Ridd 🤿

42,098 次观看 • 1 年前