Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

How I turned Claude 4 into my personal browser-controlling AI agent: 1/ Downloaded Claude Desktop (free) → Available for Mac and Windows → No subscription required 2/ Set up MCP configuration → Copy-paste simple config file → Enable browser control permissions 3/ Connected to browser extension → Chrome extension...

44,004 Aufrufe • vor 1 Jahr •via X (Twitter)

3 Kommentare

Profilbild von TanyaGoodman
TanyaGoodmanvor 1 Jahr

He's great and his analysis is great. @GavinBrookswin 🌂 💦

Profilbild von Arsalan
Arsalanvor 1 Jahr

This setup is next-level.

Profilbild von Qodo
Qodovor 1 Jahr

Fewer bugs, more shipping. Qodo’s Agentic AI handles testing, reviews, and code generation—so you can focus on building.

Ähnliche Videos

This is a very nice description of the problem. I think the first part of the solution is to not give into the hyper productivity hype: running a gazillion things in parallel. There's likely only a handful of humans that have the mental make-up to survive the permanent context switches. You can train your brain to become better at it, but there's a limit to that, and I found that it will lead to much worse outcomes in terms of output quality of both you and your clanker. I'm no neuroscientist, but I would assume there's a hard limit on how many things your brain can juggle at a time, probably made worse by the complexity that is code. I generally don't do more than 2-3 things in parallel. I use virtual desktops as "bundle of things that belong to a task", so terminals + editor + browser. Works fine, doesn't need any special OS support, expose on the virtual desktop let's me quickly switch to the task specific app I need. I also have a little pi extension that shows me what GH issue/PR the clanker session is about, with a link I can click to open the issue/PR in the browser. Plus 1 virtual desktop for entertainment, so the brain can get some rest. (better alternative: get up and walk a bit every 45 minutes) Video: - First desktop: pi session for a PR, extension shows me what PR I work on, can click to open in browser, aux terminal for random BS, editor, browser. Yes, I could split instead of having two terminal windows. I'm old. - Second desktop: clawdbot pi session, aux terminal for testing, editor, browser - Third desktop: entertainment booth

Mario Zechner

40,284 Aufrufe • vor 5 Monaten

Figma Capture + Claude Fable 5 = clone any competitor's landing page in minutes 🤯 Figma just dropped a Chrome extension that copy/pastes any live website into Figma as editable layers. Point Claude Code — running the new Fable 5 model — at the capture, and it rebuilds the whole page in YOUR brand: structure, copy, design system, photography. All inside Claude Code. Perfect for DTC brands and agencies who keep losing weeks rebuilding proven landers from scratch. If you're still cloning competitor pages the old way, You're screenshotting their site and praying the AI guesses the structure right. You're rebuilding sections by hand because the fonts and spacing never come out true. You're paying a designer $3K to recreate a page that already exists. This workflow eliminates the entire loop: → Capture the competitor's landing page with Figma's new Chrome extension — editable layers, not screenshots → Claude Code reads the page structure through the Figma MCP: every section, every headline, in order → It rebuilds the page in YOUR brand — your colors, your fonts, your voice (it even respects your banned-words list) → GPT Image 2 generates on-brand product photography from the layer names → Claude places every image automatically — finished page, ready to ship No screenshots. No guessing at structure. No design invoice. What you get: → A pixel-structured clone of any proven lander, rebuilt in your brand → Every line of copy rewritten in your voice → 16 on-brand images generated and placed for ~$2 in API costs → Start to finish in about 15 minutes Built 100% with Figma + Claude Code on Claude Fable 5. I put together a step-by-step playbook showing you exactly how to set it up. Want access for free? > Like this post > Comment "CLONE" And I'll send it over (must be following so I can DM)

Mike Futia

46,198 Aufrufe • vor 1 Monat

how to use claude code + 3 MCPs + 2 AI tools to go from cold idea to live A/B test in 1 session (full workflow): 1. connect ideabrowser as an MCP. pull your project context like ICP, positioning, offer, growth strategy directly into the terminal. 2. use ideabrowser skills to generate a lead magnet concept tailored to your niche. it builds the strategy doc and saves it as a file. 3. open paper (connected to claude code). design your landing page visually and iterate on hero, sections, components. design and code stay in sync. dont necessarily need figma here. 4. deploy the landing page. wire up humblytics for analytics like traffic, scroll depth, heat maps, funnel tracking, full attribution. 5. run a no-code A/B experiment directly from claude code. it dynamically swaps your headline on the live site. 6. store the results back into Idea Browser (pro plan) so your agent compounds context over time. every future decision is informed by past data. 7. everyone can build landing pages now. the gap is knowing what to test, how to get customers, and how to optimize. this stack/workflowcloses that gap. amirmxt showed me this live and i can't stop thinking about the arbitrage. 99.999% of people don't know this stack exists. it's like when 5 cent facebook ads were around, arbritrage is all over again. episode is finally live on The Startup Ideas Podcast (SIP) 🧃 (full demo there) this one is different. send it to a friend who likes ideas and automating businesses. 100% free to watch this and get your creative juices flowing (let me know what you want me to cover next) watch

GREG ISENBERG

57,852 Aufrufe • vor 3 Monaten

REAL ESTATE PEOPLE WILL HATE HIM FOR THIS. HE BUILT A CLAUDE AGENT THAT TURNS ANY LISTING INTO A SELLABLE VIDEO ON ITS OWN Playbook: connect Claude to a video generator, paste a listing, get a cinematic tour of every room, sell it to the agent But typing the prompt for every listing doesn't scale. He turned it into a skill his Claude runs on its own Here's how to build the automated version: 1. Connect the video engine once. In Claude, go to Customize, Connectors, Add Custom Connector, name it Higgsfield, and paste the server URL from higgsfield. ai/mcp. Authenticate through your account. No API keys. Now Claude can generate video straight from chat 2. Turn the workflow into a skill. Instead of pasting the same prompt every time, have Claude build a skill. Tell it: "Create a skill called listing-to-video. When I give it a listing URL, scrape the room photos, generate a cinematic clip of each room with Higgsfield, and save them to a folder." Now the whole process is one command, not a wall of text 3. Let the agent run the listing. Hand it a URL and say "run listing-to-video on this." It pulls the photos, fires each room through the video model, and brings the clips back. You wrote the prompt once, inside the skill. You never write it again 4. Stitch and deliver. Drop the clips together into one tour. Send a free sample to the listing's agent, then charge per video or a monthly rate for ongoing listings 5. Scale it with your team. Add a skill that drafts the outreach email and one that builds a simple landing page for the agent. Now one operator runs sourcing, production, and pitching from a single Claude session The edge isn't generating one video. It's building the skill once so every future listing runs itself Bookmark this

Yarchi

54,531 Aufrufe • vor 1 Monat

Claude Code + computer use is f*cking cracked 🤯 Build a landing page → Claude opens Chrome, looks at it, spots every issue, and fixes it — without you describing a single thing. All inside Claude Code. Perfect for DTC brands and agencies who are still vibe-coding landing pages and advertorials in Claude Code, then manually opening them in Chrome, spotting 15 things wrong, and describing every visual issue back to Claude one at a time. If you're building pages in Claude Code and your workflow looks like this — build the page, open it in Chrome, spot broken spacing, go back to Claude, type "the CTA button is too low and the hero image is cut off," wait for the fix, open Chrome again, find 3 new issues, describe those too ... Claude Code + computer use eliminates the entire loop: → Claude writes the full landing page or advertorial → Opens Chrome and navigates to it → Spots layout issues, broken spacing, off-brand colors, missing elements → Fixes everything and re-checks until the page looks right → Tests your Shopify product pages by clicking through like a real customer → Walks through your checkout flow and flags friction before customers hit it → You only see the finished, visually verified result No describing what you see on screen. No "the CTA button needs more contrast" back-and-forth. No being the eyeballs for an AI that can't see. What you get: → Landing pages and advertorials Claude builds AND visually QAs before you ever look at them → Product pages Claude clicks through — testing layout, images, and CTAs like a real user → HTML dashboards Claude opens and verifies the charts actually render → Checkout flows Claude walks through step by step to catch friction → All of it happening in one session — build, test, fix, done One prompt. Claude builds it, checks it, and fixes it. You just review the finished page. I put together a full playbook with the exact setup, the prompts, and 5 DTC workflows that use Claude Code + computer use. Want it for free? > Like this post > Comment "CLAUDE" And I'll send it over (must be following so I can DM)

Mike Futia

19,079 Aufrufe • vor 3 Monaten