正在加载视频...

视频加载失败

返回首页

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

Today we're launching Jitsu MCP. This is an MCP server that lets your agent run your entire event pipeline directly in Claude Code, Claude Desktop, Cursor, or VS Code. Here's how it works: Add the server: claude mcp add --transport http jitsu Run this prompt: "Route my web stream into ClickHouse, but only purchase and signup events. Send a test event, check Live Events, and if anything errors, find the function in the path and fix it." Approve the OAuth prompt once, and all 26 tools are live Your agent wires the streams, watches Live Events, and rewrites a function when one of them throws. It runs the fix against a real event before shipping it, so nothing is persisted until it works. Every change lands in the audit log tagged mcp, so you can tell what the agent did from what a person did. It's all MIT licensed, and it runs against your own deployment. Jitsu is one of the fastest growing open-source CDPs with 5,000+ GitHub stars. Capturing events is unlimited and free, and delivery is free up to 200k events a month. Comment Jitsu and I'll DM you the exact prompts I run in Claude Code to build an event pipeline end to end.
0:51

Today we're launching Jitsu MCP. This is an MCP server that lets your agent run your entire event pipeline directly in Claude Code, Claude Desktop, Cursor, or VS Code. Here's how it works: Add the server: claude mcp add --transport http jitsu Run this prompt: "Route my web stream into ClickHouse, but only purchase and signup events. Send a test event, check Live Events, and if anything errors, find the function in the path and fix it." Approve the OAuth prompt once, and all 26 tools are live Your agent wires the streams, watches Live Events, and rewrites a function when one of them throws. It runs the fix against a real event before shipping it, so nothing is persisted until it works. Every change lands in the audit log tagged mcp, so you can tell what the agent did from what a person did. It's all MIT licensed, and it runs against your own deployment. Jitsu is one of the fastest growing open-source CDPs with 5,000+ GitHub stars. Capturing events is unlimited and free, and delivery is free up to 200k events a month. Comment Jitsu and I'll DM you the exact prompts I run in Claude Code to build an event pipeline end to end.

Soham Mehta

283,208 次观看 • 2 个月前

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 次观看 • 4 个月前

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

50,081 次观看 • 3 个月前

Bun creator Jarred Sumner rewrote a million lines of code with Claude in 11 days, and every line was checked by two agents that didn't write it I broke down his setup, added one more layer of control on top, and packed it all into one prompt for Opus 5.5 → one agent writes the code → two others, each in its own context, see only the diff and have to prove it doesn't work → a fourth agent checks the checkers, drops false alarms and looks for what they missed → whoever writes doesn't review, and whoever reviews doesn't write → reviewers reject stubs, weakened tests and "explanatory" comments instead of real fixes → if a bug repeats, the agent doesn't patch the code, it adds a rule so it never happens again → it's done only when every test passes and none are skipped Throw it at Opus 5.5 with the task you're scared to hand to an agent, and see how many bugs it catches on its own. The full prompt is in the comments. How to tune it for your own work is in the article below. Save it before it gets lost ↓
0:30

Bun creator Jarred Sumner rewrote a million lines of code with Claude in 11 days, and every line was checked by two agents that didn't write it I broke down his setup, added one more layer of control on top, and packed it all into one prompt for Opus 5.5 → one agent writes the code → two others, each in its own context, see only the diff and have to prove it doesn't work → a fourth agent checks the checkers, drops false alarms and looks for what they missed → whoever writes doesn't review, and whoever reviews doesn't write → reviewers reject stubs, weakened tests and "explanatory" comments instead of real fixes → if a bug repeats, the agent doesn't patch the code, it adds a rule so it never happens again → it's done only when every test passes and none are skipped Throw it at Opus 5.5 with the task you're scared to hand to an agent, and see how many bugs it catches on its own. The full prompt is in the comments. How to tune it for your own work is in the article below. Save it before it gets lost ↓

Hoodie

15,185 次观看 • 7 天前

It is becoming f*cking dangerous: someone published the full prompt for building trading agents. You paste it into Claude Code and it builds the bot while you have lunch No code. Just Ctrl+C / Ctrl+V. One prompt sets up the whole thing: Time: 1 minute Action: copy and paste into Claude Code The main problem with 99% of bots: one strategy for everything. But the market on a calm day and during a crash are two completely different worlds Quant mode: detects the regime (sideways, jittery, dumping) and switches tactics on the fly E-brake: a hard 15% drawdown limit and a risk check before every single order Hardcore backtest: replays the strategy on historical data with fees and slippage, and shows you exactly where it falls apart. a curve that only looks good on the past is the easiest thing in the world to build Nightly analyst: while you sleep it reviews every fill, writes up what went wrong, and hands you the notes in the morning Near-zero code: you paste the prompt and your parameters, Claude writes the engine, and you read the risk layer before anything touches a live account This used to take a whole development team and months of testing. Now it takes a single keyboard shortcut The prompt is below. paper trade it first, then save it
0:22

It is becoming f*cking dangerous: someone published the full prompt for building trading agents. You paste it into Claude Code and it builds the bot while you have lunch No code. Just Ctrl+C / Ctrl+V. One prompt sets up the whole thing: Time: 1 minute Action: copy and paste into Claude Code The main problem with 99% of bots: one strategy for everything. But the market on a calm day and during a crash are two completely different worlds Quant mode: detects the regime (sideways, jittery, dumping) and switches tactics on the fly E-brake: a hard 15% drawdown limit and a risk check before every single order Hardcore backtest: replays the strategy on historical data with fees and slippage, and shows you exactly where it falls apart. a curve that only looks good on the past is the easiest thing in the world to build Nightly analyst: while you sleep it reviews every fill, writes up what went wrong, and hands you the notes in the morning Near-zero code: you paste the prompt and your parameters, Claude writes the engine, and you read the risk layer before anything touches a live account This used to take a whole development team and months of testing. Now it takes a single keyboard shortcut The prompt is below. paper trade it first, then save it

Chen

192,088 次观看 • 27 天前

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 🚀

123,101 次观看 • 5 个月前

🚨 SOMEONE LEAKED THE PROMPT THAT MAKES CLAUDE CODE CREATE ITS OWN SKILLS AND WORK BETTER EVERY DAY WITHOUT YOU TOUCHING ANYTHING No programming. Just paste. A single prompt does it all: Time needed: 2 minutes Actions: copy and paste into Claude Code The mistake 90% of people make with Claude: explaining the same thing to it every day. The same tone, the same steps, the same corrections. And the next day it starts from scratch again. → Detects what you repeat: reviews your project and asks you what tasks you do every week → Creates a skill for each one: instructions, templates, and examples that Claude loads only when it needs them → Tests them before giving them to you: runs each skill with a real case and fixes it if it fails → Learns from your corrections: every time you correct something, it updates the skill so it doesn't repeat the error → Zero code: you tell it what you do and Claude builds its own library of skills Before, this meant writing manuals, templates, and processes for weeks. Now it's just Ctrl+V. Save it before they delete it 🔖 Follow Tomcruise AI for more...
0:24

🚨 SOMEONE LEAKED THE PROMPT THAT MAKES CLAUDE CODE CREATE ITS OWN SKILLS AND WORK BETTER EVERY DAY WITHOUT YOU TOUCHING ANYTHING No programming. Just paste. A single prompt does it all: Time needed: 2 minutes Actions: copy and paste into Claude Code The mistake 90% of people make with Claude: explaining the same thing to it every day. The same tone, the same steps, the same corrections. And the next day it starts from scratch again. → Detects what you repeat: reviews your project and asks you what tasks you do every week → Creates a skill for each one: instructions, templates, and examples that Claude loads only when it needs them → Tests them before giving them to you: runs each skill with a real case and fixes it if it fails → Learns from your corrections: every time you correct something, it updates the skill so it doesn't repeat the error → Zero code: you tell it what you do and Claude builds its own library of skills Before, this meant writing manuals, templates, and processes for weeks. Now it's just Ctrl+V. Save it before they delete it 🔖 Follow Tomcruise AI for more...

Tomcruise AI

38,809 次观看 • 7 天前

YOUR AI AGENT JUST GOT ITS OWN EMAIL Atomic Mail shipped an email API built for agents, not people. One prompt and your agent registers its own inbox, then reads, sends and replies on its own. - Self-signup in ~30 seconds, no human, no CAPTCHA, no card - Plugs into Claude Code, Codex, Cursor and OpenClaw via MCP or one line - Runs on JMAP, a standard models already know - Already running support inboxes and newsletter digests unattended The agents have inboxes now.
0:29

YOUR AI AGENT JUST GOT ITS OWN EMAIL Atomic Mail shipped an email API built for agents, not people. One prompt and your agent registers its own inbox, then reads, sends and replies on its own. - Self-signup in ~30 seconds, no human, no CAPTCHA, no card - Plugs into Claude Code, Codex, Cursor and OpenClaw via MCP or one line - Runs on JMAP, a standard models already know - Already running support inboxes and newsletter digests unattended The agents have inboxes now.

BuBBliK

15,573 次观看 • 4 个月前

It is becoming f*cking dangerous: A prompt for creating trading agents was accidentally leaked online. You paste it into claude code, and it builds a bot while you have lunch No code. Just Ctrl+C / Ctrl+V. One prompt solves everything: Time: 1 minute Action: copy and paste into Claude Code The main problem with 99% of bots: one strategy for everything. But the market on a calm day and during a crash are two completely different worlds Quant mode: detects market conditions (sideways, jittery, dump) and changes tactics on the fly E-brake: a strict 15% drawdown limit and risk checks before every order Hardcore backtest: runs the strategy on historical data and blocks trading if it is not profitable Nightly analyst: while you sleep, it analyzes mistakes and produces ready-to-approve setups Zero Code: type in the prompt, insert your parameters, and Claude handles the rest This used to take a whole development team and months of testing. Now it takes a single keyboard shortcut The prompt is published below, bookmark it so you do not lose it
0:22

It is becoming f*cking dangerous: A prompt for creating trading agents was accidentally leaked online. You paste it into claude code, and it builds a bot while you have lunch No code. Just Ctrl+C / Ctrl+V. One prompt solves everything: Time: 1 minute Action: copy and paste into Claude Code The main problem with 99% of bots: one strategy for everything. But the market on a calm day and during a crash are two completely different worlds Quant mode: detects market conditions (sideways, jittery, dump) and changes tactics on the fly E-brake: a strict 15% drawdown limit and risk checks before every order Hardcore backtest: runs the strategy on historical data and blocks trading if it is not profitable Nightly analyst: while you sleep, it analyzes mistakes and produces ready-to-approve setups Zero Code: type in the prompt, insert your parameters, and Claude handles the rest This used to take a whole development team and months of testing. Now it takes a single keyboard shortcut The prompt is published below, bookmark it so you do not lose it

Bober_smart

118,491 次观看 • 29 天前

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

114,229 次观看 • 5 个月前

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

227,831 次观看 • 3 个月前

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 次观看 • 4 个月前

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

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,851 次观看 • 1 年前

I still don’t understand why people keep building a Claude second brain by hand when these 10 repos already built the whole system They turn your Claude sessions into a wiki, let Claude read and write your vault from your phone, and one of them comes straight from Obsidian’s own CEO 01 llm-wiki → your Claude Code and Codex sessions become a searchable wiki, with an MCP server to query it 02 llm-wiki-claude-skill → one skill file teaches Claude to ingest sources, answer from them, lint the wiki and compile it into clean pages 03 obsidian-skills → Obsidian’s own CEO teaches Claude how Obsidian really works 04 llm-wiki → a Claude Code plugin with init, ingest, compile, query and lint, where every change is committed to git 05 obsidian-dev-second-brain → your tickets, sprints and project docs live in the vault as notes, and Claude keeps them in sync with the code 06 obsidian-mcp-server → 14 tools to read, write, search and surgically edit notes, tags and frontmatter 07 mcpvault → safe vault access with a read-only mode, and Obsidian doesn’t even need to be running 08 obsidian-claude-code-mcp → connect Claude Code to your open vault with one /ide command 09 obsidian-web-mcp → reach your vault from your phone or any MCP client, with OAuth and a Cloudflare Tunnel 10 obsidian-mcp → a git-backed vault with 18 tools, running locally or on AWS Lambda Nobody is going to build your second brain for you, and every chat you close without one is knowledge thrown away. Bookmark this, pick one repo from 01 to 05 and ingest your first source tonight. A month from now you have a wiki, and everyone who skipped it is still opening a blank chat.
0:22

I still don’t understand why people keep building a Claude second brain by hand when these 10 repos already built the whole system They turn your Claude sessions into a wiki, let Claude read and write your vault from your phone, and one of them comes straight from Obsidian’s own CEO 01 llm-wiki → your Claude Code and Codex sessions become a searchable wiki, with an MCP server to query it 02 llm-wiki-claude-skill → one skill file teaches Claude to ingest sources, answer from them, lint the wiki and compile it into clean pages 03 obsidian-skills → Obsidian’s own CEO teaches Claude how Obsidian really works 04 llm-wiki → a Claude Code plugin with init, ingest, compile, query and lint, where every change is committed to git 05 obsidian-dev-second-brain → your tickets, sprints and project docs live in the vault as notes, and Claude keeps them in sync with the code 06 obsidian-mcp-server → 14 tools to read, write, search and surgically edit notes, tags and frontmatter 07 mcpvault → safe vault access with a read-only mode, and Obsidian doesn’t even need to be running 08 obsidian-claude-code-mcp → connect Claude Code to your open vault with one /ide command 09 obsidian-web-mcp → reach your vault from your phone or any MCP client, with OAuth and a Cloudflare Tunnel 10 obsidian-mcp → a git-backed vault with 18 tools, running locally or on AWS Lambda Nobody is going to build your second brain for you, and every chat you close without one is knowledge thrown away. Bookmark this, pick one repo from 01 to 05 and ingest your first source tonight. A month from now you have a wiki, and everyone who skipped it is still opening a blank chat.

Ryven

10,722 次观看 • 11 天前

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

Sleep is now part of the dev loop. The setup in the animation is simple. The coding agent works through the night, and its definition of done is that TestSprite's Integration Tests pass against the running app. Each failure comes back as the step that broke plus a fix prompt the agent can act on, so it fixes and retests on its own instead of stopping to wait for you. The CLI is open source under Apache-2.0 and works with Claude Code, Codex, Cursor, Antigravity, Kimi and Trae.
0:55

Sleep is now part of the dev loop. The setup in the animation is simple. The coding agent works through the night, and its definition of done is that TestSprite's Integration Tests pass against the running app. Each failure comes back as the step that broke plus a fix prompt the agent can act on, so it fixes and retests on its own instead of stopping to wait for you. The CLI is open source under Apache-2.0 and works with Claude Code, Codex, Cursor, Antigravity, Kimi and Trae.

Future Coded

17,277 次观看 • 1 个月前

Sleep is now part of the dev loop. The setup in the animation is simple. The coding agent works through the night, and its definition of done is that TestSprite's Integration Tests pass against the running app. Each failure comes back as the step that broke plus a fix prompt the agent can act on, so it fixes and retests on its own instead of stopping to wait for you. The CLI is open source under Apache-2.0 and works with Claude Code, Codex, Cursor, Antigravity, Kimi and Trae.
1:02

Sleep is now part of the dev loop. The setup in the animation is simple. The coding agent works through the night, and its definition of done is that TestSprite's Integration Tests pass against the running app. Each failure comes back as the step that broke plus a fix prompt the agent can act on, so it fixes and retests on its own instead of stopping to wait for you. The CLI is open source under Apache-2.0 and works with Claude Code, Codex, Cursor, Antigravity, Kimi and Trae.

JAYDEN™

23,263 次观看 • 1 个月前