Загрузка видео...

Не удалось загрузить видео

На главную

Step 1: Open Claude Code. Step 2: Create 3 markdown files. Step 3: Type ONE command. You now have an AI team. A researcher that cites every source. A builder that can only use what the researcher found. A critic that never wrote the draft, so it never defends...

19,987 просмотров • 3 дней назад •via X (Twitter)

Комментарии: 18

Фото профиля Danylo Pravda
Danylo Pravda3 дней назад

Still waiting for the step where someone opens the app and looks at it

Фото профиля Isagii
Isagii3 дней назад

Massive stuff

Фото профиля 摸鱼中
摸鱼中3 дней назад

Great point!

Фото профиля Wukoayos
Wukoayos3 дней назад

Best part is the handoff file. If the builder can only cite what the researcher wrote down, checking the whole run means reading one Markdown file. I make Rho MD, a Markdown notes app.

Фото профиля Yaki
Yaki3 дней назад

the critic agent is the real unlock here honestly, stopped me from shipping so much garbage

Фото профиля 安叫兽|Bird🕊️ 🔶 BNB
安叫兽|Bird🕊️ 🔶 BNB3 дней назад

批评者没写过草稿这点挺关键,少了点护短。

Фото профиля Wes
Wes3 дней назад

The critic that never wrote the draft is the smart part. It has no reason to defend it.

Фото профиля 全哥AI创业记
全哥AI创业记3 дней назад

The critic that never wrote the draft is the key insight — I tried having one agent do everything and it just defended its own bad decisions. Separation of concerns applies to AI teams too. Stealing this setup.

Фото профиля talha
talha3 дней назад

does it actually catch bugs or just nitpick wording?

Фото профиля James Malsawm
James Malsawm3 дней назад

giving claude code a separate critic agent caught so many of my bugs

Фото профиля rama
rama3 дней назад

i ask gpt to be Claude's critic and vice versa

Фото профиля Vexo
Vexo3 дней назад

everyone here loves the critic, but a critic with zero context has its own failure mode: it flags deliberate choices as bugs and the builder "fixes" them. anthropic found ~59% of what their own reviewer kept flagging was old code. so does your critic see only the new diff, or the whole thing?

Фото профиля Raúl Nogales 🇪🇸🇺🇸
Raúl Nogales 🇪🇸🇺🇸3 дней назад

The weak joint is upstream. If the researcher cites a bad source well, the builder inherits it and the critic checks the draft against that same source. Garbage enters with a citation attached and comes out looking more reliable, not less.

Фото профиля DHRUV BANSAL
DHRUV BANSAL3 дней назад

When the critic doesn't trust a source... does it send the researcher back out or does the whole run just stop? A vendor comparison going to finance, say. Every number in it has to trace back to a link

Фото профиля E1ev3n.
E1ev3n.3 дней назад

The critic detail is the one I keep coming back to, because my own drafts always get defended by the same mind that wrote them. I tried splitting that job once and the review finally got honest, even if it stung a bit.

Фото профиля Camto
Camto3 дней назад

Amezing

Фото профиля k i c i l
k i c i l3 дней назад

What if the researcher finds bad sources

Фото профиля Ali Rewires
Ali Rewires3 дней назад

its kind of the same thing that happens to people, minus the ego. the writer agent got to its answer through its own steps, so reviewing its own draft just retraces them. a fresh critic starts from somewhere else

Похожие видео

I just reverse-engineered Apple AirDrop with Opus 5.5 to send files between my Mac & Windows PC this is insane... drag a file onto the other computer → hop. it's there. no cloud. no account. no cable. → here's the build step by step: • step 1 → open Claude Code on Opus 5.5 in an empty folder and paste the prompt below • step 2 → Opus picks the stack: one Electron codebase that runs on macOS and Windows • step 3 → discovery: every 1.5 s each computer says "i'm here" over UDP on your local network. the other one pops up on a radar • step 4 → transfer: files stream directly between the two machines. the other side gets Accept / Decline. "always accept" for your own computers • step 5 → before any UI, Opus wrote a test: two fake devices find each other and send a folder + a 3 MB file, byte for byte • step 6 → design: Opus split the work across parallel agents. one rebuilt the iOS 17 NameDrop glow as a WebGL shader, one drew 3 icon concepts and picked the best, one built the download site • step 7 → separate reviewer agents checked every piece. one caught a shader bug that would've rendered black on the Mac. i'm on Windows, i'd never have seen it • step 8 → GitHub Actions builds the .dmg and the .exe on every release. the Mac build runs on Apple hardware in the cloud, not on my PC • step 9 → first launch on the Mac: the icon just bounced in the dock. Opus added a startup log and a fallback that forces the window open. next build opened fine one afternoon. zero lines written by me. drop it on the Mac. it lands on the PC. that's it... find full prompt below ↓ Then read the article on how to reverse-engineer anything with Opus 5.5.

Movez

59,306 просмотров • 11 дней назад

I just reverse-engineered CCleaner / CleanMyMac with Opus 5.5 for Mac & Windows PC this is insane... one tap → 14.6 GB of junk gone. fully open-source and free. → here’s the build step by step: • step 1 → open Claude Code on Opus 5.5 in an empty folder, paste the prompt below + a few CleanMyMac screenshots • step 2 → Opus didn’t start coding. it drew 9 UI concepts on a canvas first. i picked one, it rebuilt the fonts, icons and glass buttons until it looked like Apple made it • step 3 → i sent it a random video of smoky gradients. Opus turned it into a live WebGL shader: “cosmic wind” rising behind the scan result • step 4 → stack: one Electron + React codebase that runs on macOS and Windows • step 5 → Opus split the build across 8 parallel agents. one wrote the junk scanner, one the disk map, one the AI assistant, one the tips & feedback screens, one the installers • step 6 → a separate safety agent attacked every line that deletes something. it caught a Windows short-name trick (DOCUME~1) that could’ve sent my whole Documents folder to the Recycle Bin. and an icon loader that could leak my Windows password hash to a remote machine • step 7 → the disk map is a physics toy: drag a folder bubble, throw it, watch it bump the others • step 8 → built-in AI: plug in Claude or ChatGPT and ask “what can i safely delete?” it only sees file names and sizes, never contents • step 9 → GitHub Actions builds the .dmg and the .exe on every release. the Mac build runs on Apple hardware in the cloud, not on my PC • step 10 → first real test: the startup-apps toggle said “Windows did not allow the change” Opus found PowerShell was losing the exit code after the admin prompt, made the app check the registry instead. next build: works one afternoon. zero lines written by me. 14.6 GB freed on the first click. that’s it... Find full prompt below ↓ Then, read how to rebuild any app from scratch with Opus 5.5 in the article below.

Movez

170,048 просмотров • 9 дней назад

this is crazy... the guy reverse-engineered his Meta Ray-Bans 3 with Opus 5.5 into a 3,000+ Elo chess engine he built AI chess cheat glasses on Opus 5.5 + Jev and open-sourced the whole workflow here's how it works step by step: step 1 → install it on your Mac with one command: npx chesshacker setup. It downloads Stockfish from GitHub and verifies the checksum step 2 → put on Meta Ray-Bans and video-call your own Mac on WhatsApp. The glasses see the board, the Mac sees what the glasses see step 3 → the Mac grabs frames straight from the call window. About 1 per second while it waits for the opponent, 1 every 3 seconds on your turn step 4 → Jev runs a cheap pre-check on every frame: is the board readable, is a hand over it, did a piece move? No change means no expensive AI call step 5 → only then Opus 5.5 reads the board. The app compares it with the position it already knows and accepts a move only if it's legal step 6 → Stockfish thinks for half a second and picks the best reply, with an eval like +1.5 or "mate in 3" step 7 → macOS speaks it through a virtual mic into the WhatsApp call: "Rook a to d1". You hear it in your ear step 8 → on the Mac a command center shows everything live: whose turn it is, the suggested move with a confidence bar, the move list and a log under the hood: → if Opus loses track of the board, the glasses say "Lost track of the board" and you fix it with undo or by typing the move → if Stockfish crashes, it restarts once and says "Something went wrong. Still trying" → every game is saved as a PGN file, API keys live in the macOS Keychain → an overlay draws the suggested move as an arrow on the live video, ready for OBS Clone his workflow below Then read the guide on how to reverse-engineer anything with Opus 5.5.

Movez

401,346 просмотров • 12 дней назад