Boris Cherny: "Overnight sub-agents do deeper work" 10-step Fable 5 setup you can copy this week: 1. Write CLAUDE.md - stack - commands - code style - forbidden files - review rules 2. Add PROJECT_MEMORY.md - verified facts - failed attempts - last session - next run 3. Create 1 Skill per repeated workflow - CI triage - PR review - design QA - deploy check 4. Add eval cases Put them in: eval/.jsonl 5. Split maker and verifier Maker writes the chang Verifier runs the app, tests, screenshots, logs 6. Use worktrees for parallel runs No shared checkout No file collisions No mystery edits 7. Send work by price Fable 5 plans across days Sonnet 4.6 does bulk edits Haiku 4.5 grades Opus 4.8 handles fallback cases 8. Put UI work behind screenshots If the task is visual, text logs aren't enough 9. Move long jobs to Routines CI failed? Run triage PR opened? Run review 7am? Send digest 10. End every run by writing the lesson back A fix that stays in chat dies there The rule: > Builder makes the change > Verifier checks the real artifact > Memory keeps the receipt > You read the diff Skip the verifier and you don't have an agent system You have a very confident intern with shell access

AI strategist Nate B Jones: "REA isn't the death of software" He shows how an agent explains a real app feature with evidence, starting with how an authenticator app makes its codes Watch it, then copy the 8-step APK setup from the article below

Karpathy's agentic engineering was f*cking STEP ONE Your agent waits 3 hours for approval, the process dies, and the retry publishes twice Send this prompt to Opus, then read the guide below

Anthropic's first growth marketer, Austin Lau: ёё"Instead of me, a marketer, managing a bunch of campaigns, it's me, a marketer, managing a bunch of agents" He shows how he replaced his weekly budget spreadsheet with a live Claude dashboard Most agencies still copy ad spend into Google Sheets by hand every week Watch it, then copy the one-person agency setup from the article below

Grok Bot's lead designer Peng Zheng: "I will do the first 5%" The people who built Grok Bot show how they hand their bots real work and still stay in charge Your 5% on a memecoin desk is the filter Watch it, then copy the 14 rug checks from the article below

SaaStr founder Jason Lemkin: "Agents work all night and they work weekends and they work on Christmas" He shows how SaaStr swapped a team of 10 SDRs and AEs for 20 AI agents run by 1.2 humans, and which AI sales tools worked and which flopped Watch it, then copy the AI sales team setup from the article below

Anthropic's philosopher Amanda Askell: "I try and explain... to the model as clearly as possible" She shows how she actually talks to Claude to get real work out of it Most people still use it like a search bar Watch it, then copy the 21 rules from the article below

Jason Lemkin: "We're done with hiring humans in sales" 10-step AI GTM agency stack you can copy this week: 1. Source by pain, not by one filter - Clay for the build - Apollo for the first count - Ocean.io for lookalikes - Firecrawl for the prospect's own words 2. Find 2-3 people per company - the person who owns the problem - 1-2 people around them - check the first titles by hand 3. Run the email waterfall - Prospeo first - LeadMagic second - MillionVerifier before every send - catch-all held out 4. Route by account value - Tier 1 to lemlist, email + LinkedIn - Tier 2 to Instantly, email only - tier comes from a live trigger 5. Protect the main domain - cold email from spare domains only - 3 inboxes per domain - 20-25 emails per inbox a day - pause at 2% bounces 6. Keep the signal bridge dumb - RB2B, PredictLeads, UserGems watch - n8n passes the event to Clay - scoring lives in Clay 7. Point ads and outbound at one list - Tier 1 + 2 as a LinkedIn company list - founder posts from sales call questions - engagers go back into Clay 8. Split automation from agents - n8n for fixed steps - Claude for judgment calls - 1 API key per person - spend alerts before the invoice 9. Gate every send - HubSpot: read all, write drafts only - Instantly: launch needs approval - Slack: agent channel, never DM a client 10. One folder per client - CLAUDE.md under 200 lines - do-not-contact.csv - angles-that-worked - what-went-nowhere The rule: Clay finds the accounts The waterfall checks every email The agent drafts the reply A human decides what reaches a buyer Skip the approval gate and you don't have an AI agency You have $8,000 in burned credits and a burned domain

Boris Cherny: "The verification is probably the single most important thing" 10-step REA setup you can copy this week: 1. Install REA - npx rea-agents@latest setup - restart the agent - run doctor - Ghidra only for native binaries 2. Pick a safe first target - the official Notes example - Calculator's % button - an Electron app you own 3. Split into two rooms - Room A reads with REA - Room B builds from SPEC.md only - Room B never sees the analysis 4. Make SPEC.md the wall - behaviour - inputs and outputs - edge cases - open unknowns - no code, no addresses, no names 5. Tag every claim - observation - inference - unknown 6. Build the oracle first - byte: compare compiled code - behaviour: same inputs, same outputs - runtime: run it, use it, watch it 7. Plant 3 failures - one wrong constant - one swapped branch - one off-by-one boundary - if any passes, fix the oracle 8. Put the builder on /goal - every SPEC case passes - all 3 planted failures rejected - no file outside ./my-version - stop after 25 turns 9. Set effort per room - reading: medium - spec: high - verification: xhigh 10. End every run in git - confirmed facts - open unknowns - checks that exist - next experiment The rule: Reader explains the original Spec holds the wall Oracle decides what's true Planted bugs test the oracle TH08 passed every byte check with 0.0 instead of 128.0 Skip the planted failures and your oracle is just another confident guess

300 agents on one question is f*cking unfair… REA takes an app apart and shows the evidence. Kimi K3 throws a whole swarm at reading it. You rebuild one behavior in your own code and prove it matches. Steal the prompt in the pic, bro. Full 8-lesson course in the guide below.

This repo is f*cking everywhere right now, and most people are using it wrong… REA gives your agent a real disassembler. The point isn't cracking stuff. It's reading software you own, then rebuilding the feature in your own clean code. Try it on one app you already use, bro. Then grab the full 8-step clean-room setup in the guide below.

Everyone's saying "graphs" and half of them mean different sh*t… Andrew Ng's course builds knowledge graphs. Your agent needs the other kind: boxes, arrows, one shared notebook. Paste this prompt into Opus 5.5, bro. It tells you loop or graph, then builds it. Full guide below.

This sh*t is actually insane… Anthropic's co-founder reverse engineers AI like a compiled binary. Now one free repo lets Claude do that to any app you own. Paste this prompt into Opus 5.5, bro. Then steal the full REA setup in the guide below.

Claude Code's creator ditched codebase indexing. Claude just greps your code like a senior engineer. Point that at code nobody documented and it's f*cking scary good… Paste this prompt into Opus 5.5, bro. You'll thank me later. Then steal the full reverse engineering setup below.

Anthropic's head of product for Claude Code lets an AI coworker read her Gmail. It flags who matters and pings her in Slack. That's f*cking next level… Paste this prompt into Opus 5.5, bro. You'll thank me later. Then grab the full run-your-business-from-Slack setup in the guide below.

Anthropic's growth marketer built his own ad machine in Claude Code. Without writing a single line of code. It's f*cking genius… Paste this prompt into Opus 5.5, bro. You'll thank me later. Then grab the full distribution system in the guide below.

This dude just cut his Opus 5.5 coding agent from $6.42 to $2.00 per feature. Opus still does all the thinking. Holy sh*t, it's so stupidly simple… Paste this prompt into Opus 5.5 with a week of your agent logs, bro. Then read the breakdown below and stop paying frontier prices for multiple choice questions.

Continuous Discovery Habits author Teresa Torres: "Am I ever going to have to explain this context to Claude again?" She opens her Obsidian folder of tiny context files Claude pulls from, incl. a profile she never wrote a single word of. Claude did Sick of re-explaining your whole f*cking life to every new chat, fam? Watch it, then steal the 3 prompts that build your portable MY-AI folder from the article below

Greg Isenberg, breaking down the marketing engineer role: "That repo is the difference between 'hey, AI helped me make a thing' and 'AI is helping the whole company get smarter'" He shows the growth OS folder he'd set up before any agent: customer truth, founder voice, outbound, creative tests, agent jobs Watch it, then steal the 6-file brain, the agent contracts and the weekly loop from the article below

OpenAI's Deep Research lead Isa Fulford: "The citations actually also cite the specific lines from the sources" She shows how Deep Research asks clarifying questions first, then backs each claim with the exact source line Watch it, then steal the research contract, the evidence ledger and the ready prompt from the article below

OpenAI co-founder Andrej Karpathy: "Think of the tokens in the context window as a precious resource" He explains why every leftover token in your chat makes the model slower, pricier and easier to distract Hitting your Claude limit by Wednesday? Watch it, then steal the 22 token-saving rules from the article below