正在加载视频...

视频加载失败

返回首页

ONE PROMPT AND ONE BUTTON NOW BUILDS A FULL SYSTEM, DATABASE, BACKEND, AND FRONTEND INCLUDED Most people still picture AI as something you ask questions to, then copy the answer into your own code by hand. A builder wired Claude into Obsidian through MCP instead, so a single written...

0xWast3's profile picture

wast3

3,511 subscribers

20,348 次观看 • 1 个月前 •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 条评论

暂无评论

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

相关视频

THE GUY RUNNING CLAUDE CODE AT ANTHROPIC JUST SAID HE DOESN’T PROMPT AI ANYMORE. He writes loops. That’s a huge difference. A prompt tells Claude what to do once. A loop gives Claude a goal. Then Claude keeps checking its own work… Finding mistakes. Writing its next prompt. Trying again. Over and over… Until it actually reaches the target you defined. But here’s what most people miss. A loop is only as smart as the context you give it. That’s exactly why Claude Repositories matter. I broke down how to connect your entire codebase so Claude can actually reason across your project instead of a single file. Full guide below
1:36

THE GUY RUNNING CLAUDE CODE AT ANTHROPIC JUST SAID HE DOESN’T PROMPT AI ANYMORE. He writes loops. That’s a huge difference. A prompt tells Claude what to do once. A loop gives Claude a goal. Then Claude keeps checking its own work… Finding mistakes. Writing its next prompt. Trying again. Over and over… Until it actually reaches the target you defined. But here’s what most people miss. A loop is only as smart as the context you give it. That’s exactly why Claude Repositories matter. I broke down how to connect your entire codebase so Claude can actually reason across your project instead of a single file. Full guide below

kiosa

16,808 次观看 • 1 个月前

I tested Genspark new AI Developer: an L4 agent that builds a working app from an idea. You can choose any model (including Claude), and it runs in your browser and in the app—including planning, code, testing, and fixes. The output looks like it was done by a senior developer. I used Prompt to build a functional newsflash page that creates and curates a newsletter for me by adding a few links! It's revolutionary. Prompt in the comments. Genspark
0:34

I tested Genspark new AI Developer: an L4 agent that builds a working app from an idea. You can choose any model (including Claude), and it runs in your browser and in the app—including planning, code, testing, and fixes. The output looks like it was done by a senior developer. I used Prompt to build a functional newsflash page that creates and curates a newsletter for me by adding a few links! It's revolutionary. Prompt in the comments. Genspark

Chubby♨️

235,727 次观看 • 1 年前

most people spend hours describing what they want to Claude Code this guy just browsed a catalog of thousands of animated UI components, found one he liked, and hit "copy prompt" that's it. the prompt goes into Claude Code and it builds it. > 21st(.)dev - a library of community-made components built for React, Next.js, Tailwind > every component has a ready-made prompt attached > you pick the effect, copy, paste, done no describing animations from scratch. no explaining what "smooth scroll" or "hover glow" means. someone already figured out the exact prompt that produces it. gap between people who know this exists and people who don't is measured in hours per project full walkthrough in the article below
0:41

most people spend hours describing what they want to Claude Code this guy just browsed a catalog of thousands of animated UI components, found one he liked, and hit "copy prompt" that's it. the prompt goes into Claude Code and it builds it. > 21st(.)dev - a library of community-made components built for React, Next.js, Tailwind > every component has a ready-made prompt attached > you pick the effect, copy, paste, done no describing animations from scratch. no explaining what "smooth scroll" or "hover glow" means. someone already figured out the exact prompt that produces it. gap between people who know this exists and people who don't is measured in hours per project full walkthrough in the article below

monokern

64,484 次观看 • 1 个月前

Claude Code creator, Boris Cherny: "Forget everything you learned about computer science theory, now you just explain to the model what you need and it does the rest." 32 minutes of the head of Claude Code showing exactly how he builds now. He gave Claude one prompt two weeks ago and it's still running, spawning thousands of agents on its own. The people winning right now aren't writing more code, they're building loops that run without them. Watch it, then go deeper with the graph engineering guide that combines agents and loops below.
31:58

Claude Code creator, Boris Cherny: "Forget everything you learned about computer science theory, now you just explain to the model what you need and it does the rest." 32 minutes of the head of Claude Code showing exactly how he builds now. He gave Claude one prompt two weeks ago and it's still running, spawning thousands of agents on its own. The people winning right now aren't writing more code, they're building loops that run without them. Watch it, then go deeper with the graph engineering guide that combines agents and loops below.

Anatoli Kopadze

47,071 次观看 • 19 天前

i just built a 4-agent software team. everything runs from Telegram and gets managed on a kanban board. a project manager who plans the work, a backend developer, a frontend developer, and a tester. the PM reads a goal, breaks it into linked tasks, and assigns each to the right agent. the thing that makes them a team instead of four strangers is a shared kanban board. every task is a row that survives crashes, and when an agent finishes, it writes a summary of what it built and what the next agent needs to know. the next agent reads that summary before it starts. so the frontend developer never has to guess the API shape, and the tester knows exactly what to verify. the hardest part was not the coordination. it was building an agent that could actually act like a backend engineer. a backend engineer stands up a database, wires auth, manages storage, deploys functions, and keeps all of it consistent while the rest of the team builds on top. an agent doing this from scratch drowns. it burns its context window remembering which tables exist and which endpoint it created three steps ago, and the work degrades fast. so the backend agent needs a backend built for agents, not for humans clicking through a dashboard. that is where InsForge came in. it is an open-source, agent-native backend, and i added it to my backend developer agent as a skill. a skill is a step-by-step guide that teaches the agent how to do a specific kind of work. with InsForge installed, the agent stopped improvising infrastructure and followed a reliable path: create the project, define the database, set up auth, deploy functions. to test the whole team, i had them build a working Google Docs clone, AI features included. the backend agent spun up the full service on its own. database tables, user auth, document handling, and edge functions running real TypeScript, all in one dashboard. the frontend agent read that summary and built the UI on top of it, and the tester closed the loop. the result was a backend an agent could reason about end to end, instead of one it kept getting lost inside. if you are building an AI backend engineer, InsForge is worth a look, it's 100% open-source. InsForge GitHub: (don't forget to star 🌟) the full article on Hermes Kanban: Mission Control for your Agents is quoted below.
0:22

i just built a 4-agent software team. everything runs from Telegram and gets managed on a kanban board. a project manager who plans the work, a backend developer, a frontend developer, and a tester. the PM reads a goal, breaks it into linked tasks, and assigns each to the right agent. the thing that makes them a team instead of four strangers is a shared kanban board. every task is a row that survives crashes, and when an agent finishes, it writes a summary of what it built and what the next agent needs to know. the next agent reads that summary before it starts. so the frontend developer never has to guess the API shape, and the tester knows exactly what to verify. the hardest part was not the coordination. it was building an agent that could actually act like a backend engineer. a backend engineer stands up a database, wires auth, manages storage, deploys functions, and keeps all of it consistent while the rest of the team builds on top. an agent doing this from scratch drowns. it burns its context window remembering which tables exist and which endpoint it created three steps ago, and the work degrades fast. so the backend agent needs a backend built for agents, not for humans clicking through a dashboard. that is where InsForge came in. it is an open-source, agent-native backend, and i added it to my backend developer agent as a skill. a skill is a step-by-step guide that teaches the agent how to do a specific kind of work. with InsForge installed, the agent stopped improvising infrastructure and followed a reliable path: create the project, define the database, set up auth, deploy functions. to test the whole team, i had them build a working Google Docs clone, AI features included. the backend agent spun up the full service on its own. database tables, user auth, document handling, and edge functions running real TypeScript, all in one dashboard. the frontend agent read that summary and built the UI on top of it, and the tester closed the loop. the result was a backend an agent could reason about end to end, instead of one it kept getting lost inside. if you are building an AI backend engineer, InsForge is worth a look, it's 100% open-source. InsForge GitHub: (don't forget to star 🌟) the full article on Hermes Kanban: Mission Control for your Agents is quoted below.

Akshay 🚀

122,548 次观看 • 2 个月前

Cat Wu, head of product for Claude Code at Anthropic: "you can build almost anything with Claude from a single prompt now" one prompt gets you a working screen, not YOUR product Claude Code has never seen your design system, so it guesses the look fresh every time. how to hand Claude Code that system is in the article. better than the $300 design course in your tabs, and this one's free.
12:14

Cat Wu, head of product for Claude Code at Anthropic: "you can build almost anything with Claude from a single prompt now" one prompt gets you a working screen, not YOUR product Claude Code has never seen your design system, so it guesses the look fresh every time. how to hand Claude Code that system is in the article. better than the $300 design course in your tabs, and this one's free.

Mnimiy

113,663 次观看 • 2 个月前

Claude Code is now a full video editor! Our new plugin opens a full built-in NLE right inside the Claude desktop app, where you and your agent can edit together, effortlessly. If you're already paying for Claude, you get this one for FREE. It's available now. Start using it in 1 minute, by pasting this prompt into any Claude Code chat: "Read to install and use the ChatCut plugin"
0:44

Claude Code is now a full video editor! Our new plugin opens a full built-in NLE right inside the Claude desktop app, where you and your agent can edit together, effortlessly. If you're already paying for Claude, you get this one for FREE. It's available now. Start using it in 1 minute, by pasting this prompt into any Claude Code chat: "Read to install and use the ChatCut plugin"

ChatCut

226,918 次观看 • 24 天前

DELETE FIGMA. ONE MCP CONNECTOR TURNS CLAUDE CODE INTO A GOD-MODE STUDIO IN 30 MINUTES. The exact setup, step by step, no jokes: > open connectors, add a custom connector, drop in the Higgsfield MCP > open a Claude Code session and paste one prompt > it generates the first frame, the last frame, and the motion between them > then wires the result straight into an animated hero section for your site > 30 minutes end to end, nothing rendered by hand The bigger thing hiding here: MCP means the model rents hands. it doesn't know how to animate, so it hires a tool that does, mid-task, without you switching tabs. The ceiling of what one prompt ships isn't the model anymore, it's how many hands you've plugged into it. The method underneath (the goal, the rules, the bar, the loop) is in the article below, and it works with any connector you add next.
0:32

DELETE FIGMA. ONE MCP CONNECTOR TURNS CLAUDE CODE INTO A GOD-MODE STUDIO IN 30 MINUTES. The exact setup, step by step, no jokes: > open connectors, add a custom connector, drop in the Higgsfield MCP > open a Claude Code session and paste one prompt > it generates the first frame, the last frame, and the motion between them > then wires the result straight into an animated hero section for your site > 30 minutes end to end, nothing rendered by hand The bigger thing hiding here: MCP means the model rents hands. it doesn't know how to animate, so it hires a tool that does, mid-task, without you switching tabs. The ceiling of what one prompt ships isn't the model anymore, it's how many hands you've plugged into it. The method underneath (the goal, the rules, the bar, the loop) is in the article below, and it works with any connector you add next.

Miraqle

38,373 次观看 • 1 个月前

Anthropic engineer: «You're not supposed to sit and re-prompt Claude all day. You build one loop, and it does the work while you sleep.» • 00:00 - Build your first agent that runs on its own • 05:02 - The loop that fixes its own mistakes • 16:43 - Why Claude forgets you between chats, and the fix You can learn it in one afternoon. 30 minutes here replace what most people spend a year figuring out. Watch it today, then read the guide on building loops below.
31:18

Anthropic engineer: «You're not supposed to sit and re-prompt Claude all day. You build one loop, and it does the work while you sleep.» • 00:00 - Build your first agent that runs on its own • 05:02 - The loop that fixes its own mistakes • 16:43 - Why Claude forgets you between chats, and the fix You can learn it in one afternoon. 30 minutes here replace what most people spend a year figuring out. Watch it today, then read the guide on building loops below.

Raytar

28,046 次观看 • 1 个月前

I wanted to better understand how Claude Code is wired under the hood, so I captured its API requests and pulled out the system prompt and tool definitions. Also posting the full thing as a gist below if you want to dig in!
1:22

I wanted to better understand how Claude Code is wired under the hood, so I captured its API requests and pulled out the system prompt and tool definitions. Also posting the full thing as a gist below if you want to dig in!

Sergey Karayev

85,545 次观看 • 1 年前

Boris Cherny, the engineer who built Claude Code: "I don't talk to an agent anymore. I talk to a loop" a prompt is one instruction you babysit. a loop is a goal the AI works toward on its own: > it plans > does the work > checks itself > fixes what's weak > and repeats until it's done you step out, the work keeps going that's the shift the best engineers quietly moved to. most people hear a line like that and have no idea what it means in practice this breaks it down without the hype: what a loop actually is, when it's worth building, when it's a money trap, and how to run one yourself today watch his clip, then read the article below
0:40

Boris Cherny, the engineer who built Claude Code: "I don't talk to an agent anymore. I talk to a loop" a prompt is one instruction you babysit. a loop is a goal the AI works toward on its own: > it plans > does the work > checks itself > fixes what's weak > and repeats until it's done you step out, the work keeps going that's the shift the best engineers quietly moved to. most people hear a line like that and have no idea what it means in practice this breaks it down without the hype: what a loop actually is, when it's worth building, when it's a money trap, and how to run one yourself today watch his clip, then read the article below

Dep

20,909 次观看 • 1 个月前

Boris Cherny (Claude Code's creator): I deleted my IDE in November and hasn't opened it since. I writes more code than ever. his actual words on stage: I don't prompt Claude anymore. I have loops that are running. They're the ones prompting Claude. My job is to write loops. the progression he described: → a year ago: writing code by hand with autocomplete → then: running 5-10 Claudes in parallel, prompting each one → now: he doesn't prompt at all - he writes the loops that prompt Claude what it's already done inside Anthropic: • ~3x more code shipped per engineer (he says that number is already outdated and higher) • Cowork - a full product - built in ~8 days, 100% with Claude Code • designers, the finance guy, even the chief of staff now ship code his advice to founders: give everyone as many tokens as possible, and underfund every project on purpose - 2 engineers + a pile of tokens instead of 4. the roles are melting into one "builder." Watch this, than read the article below
28:49

Boris Cherny (Claude Code's creator): I deleted my IDE in November and hasn't opened it since. I writes more code than ever. his actual words on stage: I don't prompt Claude anymore. I have loops that are running. They're the ones prompting Claude. My job is to write loops. the progression he described: → a year ago: writing code by hand with autocomplete → then: running 5-10 Claudes in parallel, prompting each one → now: he doesn't prompt at all - he writes the loops that prompt Claude what it's already done inside Anthropic: • ~3x more code shipped per engineer (he says that number is already outdated and higher) • Cowork - a full product - built in ~8 days, 100% with Claude Code • designers, the finance guy, even the chief of staff now ship code his advice to founders: give everyone as many tokens as possible, and underfund every project on purpose - 2 engineers + a pile of tokens instead of 4. the roles are melting into one "builder." Watch this, than read the article below

Morty

136,663 次观看 • 2 个月前

Someone just posted the full blueprint for an AI swarm that does the job of a 200-person quant research team. Six agents. Running 24/7. Finding brand-new alpha while you sleep. Citadel needs 100 PhDs to do this. Two Sigma needs 200. This does it with six bots and one laptop. Two ways to play this - spend a weekend building your own swarm, or copy the wallet of one that's already up $2M: Boris Cherny runs Claude Code at Anthropic. Two weeks ago he said: "I don't prompt Claude anymore. I have loops running that prompt Claude. My job is to write loops" Alpha research is just a pipeline. So instead of sitting in it, you hand each stage to its own agent: > one reads every new research paper overnight and pulls out the trade idea > one builds the features and cleans the data > one backtests it over 20 years, costs and slippage included > one runs the hard stats and kills anything overfit > one checks it still works in every market regime > one strips out plain momentum and value to see if any real edge is left Each of those six is a job a fund pays a $600,000-a-year quant to do. He runs all six for the price of an API bill. The rule that makes it work: the agent that builds a signal never gets to approve it. A separate, stronger agent tries to kill it first. Whatever survives all six by morning is real, new alpha. One trader's already running this exact swarm on Polymarket. That $2M wallet is public, every trade on-chain. The full build is in the post below - six agents, the tool that runs them, and the five mistakes that kill most people. Bookmark & read this before it's buried.
0:41

Someone just posted the full blueprint for an AI swarm that does the job of a 200-person quant research team. Six agents. Running 24/7. Finding brand-new alpha while you sleep. Citadel needs 100 PhDs to do this. Two Sigma needs 200. This does it with six bots and one laptop. Two ways to play this - spend a weekend building your own swarm, or copy the wallet of one that's already up $2M: Boris Cherny runs Claude Code at Anthropic. Two weeks ago he said: "I don't prompt Claude anymore. I have loops running that prompt Claude. My job is to write loops" Alpha research is just a pipeline. So instead of sitting in it, you hand each stage to its own agent: > one reads every new research paper overnight and pulls out the trade idea > one builds the features and cleans the data > one backtests it over 20 years, costs and slippage included > one runs the hard stats and kills anything overfit > one checks it still works in every market regime > one strips out plain momentum and value to see if any real edge is left Each of those six is a job a fund pays a $600,000-a-year quant to do. He runs all six for the price of an API bill. The rule that makes it work: the agent that builds a signal never gets to approve it. A separate, stronger agent tries to kill it first. Whatever survives all six by morning is real, new alpha. One trader's already running this exact swarm on Polymarket. That $2M wallet is public, every trade on-chain. The full build is in the post below - six agents, the tool that runs them, and the five mistakes that kill most people. Bookmark & read this before it's buried.

cvxv666

103,734 次观看 • 1 个月前

You don’t need a dev team anymore. You need one prompt. Zoer takes your idea and turns it into a fully working app, not just code, but a real product you can use. Here’s what it handles for you: • Database (already structured) • Backend (logic + APIs) • Frontend (clean, production-ready UI) • Auth (Google + email login) • Deployment (live in one click) Most AI tools stop at “here’s your code.” Zoer goes further: It builds the entire system and puts it live. From: “build me a CRM / SaaS / tool” To: A real, working product you can open, test, and share. Try it → No setup. No configs. No extra tools. This is what building should feel like in 2026.
0:53

You don’t need a dev team anymore. You need one prompt. Zoer takes your idea and turns it into a fully working app, not just code, but a real product you can use. Here’s what it handles for you: • Database (already structured) • Backend (logic + APIs) • Frontend (clean, production-ready UI) • Auth (Google + email login) • Deployment (live in one click) Most AI tools stop at “here’s your code.” Zoer goes further: It builds the entire system and puts it live. From: “build me a CRM / SaaS / tool” To: A real, working product you can open, test, and share. Try it → No setup. No configs. No extra tools. This is what building should feel like in 2026.

Tanvir

18,160 次观看 • 3 个月前

Creator and head of Claude Code, Anthropic: "I don't prompt Claude anymore. I have loops running that prompt Claude and decide what to do. My job is to write loops." He hasn't hand-written a line of code since November. 100% is Claude Code now. Still ships 10 to 30 pull requests a day. He breaks down his actual workflow in the 1h28m podcast. Loops writing 100% of the code. Engineer leveling up, or automated out?
30:22

Creator and head of Claude Code, Anthropic: "I don't prompt Claude anymore. I have loops running that prompt Claude and decide what to do. My job is to write loops." He hasn't hand-written a line of code since November. 100% is Claude Code now. Still ships 10 to 30 pull requests a day. He breaks down his actual workflow in the 1h28m podcast. Loops writing 100% of the code. Engineer leveling up, or automated out?

shmidt

521,927 次观看 • 1 个月前

A DEVELOPER CONNECTED CLAUDE CODE TO OBSIDIAN SO HIS AI AGENT WOULD STOP FORGETTING THE PROJECT EVERY MORNING. Every coding session used to start the same way. Claude would understand the repo, fix the bug, explain the architecture, and then the moment the session ended, all of that context disappeared. Same codebase. Same decisions. Same architecture. Same mistakes repeated again. So he added a memory layer. Instead of treating Claude Code like a smart terminal, he connected it to a local Obsidian vault through MCP. Now Claude can read the repo, open the vault, create notes, link concepts, and write important decisions back into the system. When it studies the codebase, it does not just answer once and forget. It creates notes for the major services, maps how the architecture works, links auth to the database, connects APIs to storage, and records why certain migrations or design choices exist. Obsidian becomes the project graph. Now when he asks why something was built a certain way, Claude does not guess from the current prompt. It reads the decision notes. When he starts a new branch, Claude checks the active context file. When the work is done, it updates what changed, what is blocked, and what the next agent needs to know before touching the repo. That is the real loop: read context, write code, capture decisions, update memory. Most people are still using AI coding tools like disposable chat windows. Ask, patch, close, forget. This setup turns Claude Code into infrastructure. The repo gets a memory layer that survives every session, and multiple AI agents can work from the same project map without stepping on each other. The unlock is not better prompting. The unlock is giving the agent somewhere to remember what it already learned.
4:19

A DEVELOPER CONNECTED CLAUDE CODE TO OBSIDIAN SO HIS AI AGENT WOULD STOP FORGETTING THE PROJECT EVERY MORNING. Every coding session used to start the same way. Claude would understand the repo, fix the bug, explain the architecture, and then the moment the session ended, all of that context disappeared. Same codebase. Same decisions. Same architecture. Same mistakes repeated again. So he added a memory layer. Instead of treating Claude Code like a smart terminal, he connected it to a local Obsidian vault through MCP. Now Claude can read the repo, open the vault, create notes, link concepts, and write important decisions back into the system. When it studies the codebase, it does not just answer once and forget. It creates notes for the major services, maps how the architecture works, links auth to the database, connects APIs to storage, and records why certain migrations or design choices exist. Obsidian becomes the project graph. Now when he asks why something was built a certain way, Claude does not guess from the current prompt. It reads the decision notes. When he starts a new branch, Claude checks the active context file. When the work is done, it updates what changed, what is blocked, and what the next agent needs to know before touching the repo. That is the real loop: read context, write code, capture decisions, update memory. Most people are still using AI coding tools like disposable chat windows. Ask, patch, close, forget. This setup turns Claude Code into infrastructure. The repo gets a memory layer that survives every session, and multiple AI agents can work from the same project map without stepping on each other. The unlock is not better prompting. The unlock is giving the agent somewhere to remember what it already learned.

DegenCalls

20,124 次观看 • 1 个月前

Head of Claude Code Boris Cherny at Anthropic's annual developer conference in San Francisco on how his life changed in the last 6 months with AI writing all the code. "About six months ago what happened is all the code that I used to have written by hand now Claude writes. And I just prompt Claude. So I talk to Claude and I'm like, hey, let's build this feature. It builds a feature and it tests it. And then it shows me. And I'm like, yeah, that's good. Or no, wait, make this change. And then it makes the change. " --- From 'CNBC Television' YT channel (link in comment)
0:42

Head of Claude Code Boris Cherny at Anthropic's annual developer conference in San Francisco on how his life changed in the last 6 months with AI writing all the code. "About six months ago what happened is all the code that I used to have written by hand now Claude writes. And I just prompt Claude. So I talk to Claude and I'm like, hey, let's build this feature. It builds a feature and it tests it. And then it shows me. And I'm like, yeah, that's good. Or no, wait, make this change. And then it makes the change. " --- From 'CNBC Television' YT channel (link in comment)

Rohan Paul

99,075 次观看 • 2 个月前

There's a built-in agent inside Claude Code you can invoke just by telling Claude to use the claude-code-guide agent Save this... you'll need it It's not a local file in your project. It's a built-in subagent defined in Claude Code's system itself. It answers questions about Claude Code CLI, the Agent SDK, and the Claude API. It uses Glob, Grep, Read, WebFetch, and WebSearch, but can't edit or write files. Its only job is to answer questions.
0:22

There's a built-in agent inside Claude Code you can invoke just by telling Claude to use the claude-code-guide agent Save this... you'll need it It's not a local file in your project. It's a built-in subagent defined in Claude Code's system itself. It answers questions about Claude Code CLI, the Agent SDK, and the Claude API. It uses Glob, Grep, Read, WebFetch, and WebSearch, but can't edit or write files. Its only job is to answer questions.

Daniel San

57,240 次观看 • 5 个月前

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
0:42

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,840 次观看 • 2 个月前

Claude Code is terrible at UI design and everyone knows it so this guy fixed it by building an MCP that gives Claude its own AI design tool instead of going back and forth between a design platform and your code editor, Claude now creates the designs itself and drops them straight into your codebase the MCP has full context of your existing design system and project so everything it generates actually matches what you already have. one command to set up and it installs the MCP and skill files so Claude instantly knows how to use it if you're tired of the same Inter font, purple gradient, card grid layout on every project, this is definitely worth trying
0:58

Claude Code is terrible at UI design and everyone knows it so this guy fixed it by building an MCP that gives Claude its own AI design tool instead of going back and forth between a design platform and your code editor, Claude now creates the designs itself and drops them straight into your codebase the MCP has full context of your existing design system and project so everything it generates actually matches what you already have. one command to set up and it installs the MCP and skill files so Claude instantly knows how to use it if you're tired of the same Inter font, purple gradient, card grid layout on every project, this is definitely worth trying

Om Patel

401,101 次观看 • 4 个月前