You're still typing every turn The guy who built... the tool wrote the loop that types them for him "I don't prompt Claude anymore I write loops that prompt Claude" A loop takes four shapes turn-based, you close it each round goal-based - all tests pass, stop after 5 tries time-based - every 10 min, fix what's red, overnight proactive - CI breaks, agents fix it and open a PR, no human at all A judge closes the loop, not you The prompt was never the unit of work the loop is Full breakdown belowshow more

there are four types of agent loops. most people... only know one. loop engineering is a choice between four structures, each handing off one more job than the last. every one answers two questions: what starts a run, and what ends it. hand-run, you answer both yourself, every time. 1) turn-based → you prompt, it acts, you review, you prompt again. both jobs stay with you. use when requirements are still forming. 2) goal-based → "/goal hit Lighthouse 90, stop after 5 tries." an evaluator checks, a no sends it back. use when the outcome is measurable but the path isn't. 3) time-based → a clock fires, it runs "check the PR, fix CI," then waits. /loop local, /schedule survives a closed laptop. use for recurring work. 4) proactive → no human present. it watches a channel, spawns triage, fix, and a reviewer, closes the task itself. use for standing duties you can't predict. not which one is most advanced. whether your task is exploratory, measurable, recurring, or standing. the more you hand off, the less you babysit. full breakdown in the article below.show more

THE LOOP ENGINEERING SETUP THAT LETS CLAUDE RUN YOUR... WORK FOR HOURS WITHOUT YOU you sit there babysitting it prompt by prompt other people set the loop up once and let Claude plan, act, verify and fix its own work with nobody at the keyboard that gap is the whole skill of loop engineering the 3 resources that actually teach it, in the order i'd read them: > Claude's "Getting started with loops" - the cleanest entry point, straight from the Claude team ↳ > Claude loop engineering: how to build an agent that works while you sleep - the full roadmap from a single prompt to a loop that runs overnight ↳ > the Loop Engineering orange book - the deep conceptual breakdown, for when you want the whole mental model ↳ entry point, then practice, then the concept. that order saves you a week learn this and the work that eats your whole day starts running without youshow more

seedance 2.5 off a script (NO PROMPT) and every... single thing came back right - the hands - the eyes - the phone angle - the timing on the last line 15 seconds, one generation, about $3 i wrote what she says and that was the entire input still seeing people write a page of prompt for this model you don't have to anymoreshow more

In our Anthropic Claude Design study, 5 designers approved... a design system before they typed their first prompt. >Brand palette >type system >components the whole thing all set up. Only 1 of them named any of it in their opening prompt. That designer was the only one to finish production-ready. The other 4 assumed Claude would carry the system over. It didn't. TLDR: Claude doesn't reliably carry the design system you just approved. If you don't name it in the prompt, it doesn’t exist. It's never been a better time to be a designer, but you must learn the art of the prompt.show more

FIVE LAYERS OF AGENT ENGINEERING, EACH ONE WRAPS THE... ONE BELOW IT. IF YOU SKIP LAYER 2, YOUR LAYER 5 WILL LOOK BROKEN WHEN IT IS ACTUALLY JUST STANDING ON NOTHING. for weeks i debated harness vs loop vs graph like they were competing choices. then a stack diagram made the shape obvious. they are not choices. they are floors. 01 | prompt engineering. the message. unit of work: one input. inputs are role, instructions, examples, format. output is a single raw response. 02 | context engineering. the memory. unit of work: what stays in the window. a curator selects, compresses, and drops from query, docs, memory, prior turns, and tool outputs before the prompt runs. 03 | harness engineering. the machine. unit of work: the machine itself. gather (context + prompt) → LLM → tools or sub-agents → verifier → final response. the article calls this the operating environment. 04 | loop engineering. the system. unit of work: the run. goal + success criteria + max iterations + budget + completion check wrap around one harness pass. failed pass appends results to context and retries. 05 | graph engineering. the topology. unit of work: the graph run. goal + nodes + edges + state schema. graph routes to agent nodes, tool nodes, or human approval. a reviewer node with a different model and fresh context checks the final answer. the wrapping is the whole point. layer 5 assumes layer 4 works. layer 4 assumes layer 3 works. skip layer 2 and layer 3's verifier keeps failing without a clear reason. this is why swapping the model is a one-day project and swapping the stack is a quarter. the model is the commodity. the five layers around it are the engineering. full three-layer breakdown of the top of the stack (harness, loop, graph) in the post below.show more

ANTHROPIC JUST DROPPED THE OFFICIAL GUIDE TO PROMPTING FABLE... 5. This is the most important prompting framework I've seen. Bookmark this before you forget. Most people treat Fable 5 like a chatbot. That's the mistake. > don't over-engineer prompts — it degrades output. > use /loop for autonomous multi-step work. > give it the goal, not step-by-step commands. > add a memory file. it learns from past runs. > spin up 50+ subagents for complex tasks. Fable 5 isn't an assistant. it's a consultant that leads the work. Read it before you write another prompt. Claude → Fable 5 → Autonomous Work → Real Output → Moneyshow more

an agent is four parts in a loop. you... own one. the other three break it. that's why the demo works and prod doesn't. you can't debug what you can't see. 1) the prompt → what you tell the model each turn. you own this one. good. 2) the context window → what it sees right now. the framework fills it with junk, and you never notice until it rots. 3) the tools → what it can do. you own the list, not when or why it fires them. 4) the control flow → what happens next, when to stop. the framework owns this. it's what breaks at 80%. own all four and your agent stops being a magic trick that works on stage and dies on call. this isn't my idea. it's the 12-factor agents guide (24k stars) github: the whole thing every serious builder ends up rewriting their stack around. full breakdown in the article below.show more

🚨Anthropic just gave Claude Code eyes and hands. read... that again. it can now open apps on mac, click around macOS, find bugs visually, screenshot them, fix the code, rebuild, and verify the fix. one prompt. absolute zero human input. full autonomy. seems like Claude Code is becoming a super app. i’m so here for it.show more

Just made this with Seedance. Full workflow, start to... finish: - Grab a reference image — TikTok, Instagram, or Pinterest - Upload it to Claude, write a JSON prompt, adjust as you like - Generate the image - Upload it to Seedance 2.5 with your full video prompt Done All inside MakeUGC, for $1. I made a full guide breaking down the exact JSON prompt structure that makes this work. Comment "JSON" and I'll send it overshow more

20 days ago, I connected Claude Code to my... newly created instagram handle.. I gained 4.3M views and 6500+ followers in less than a month [ i post Ai generated animated stories ] Full workflow: i let claude study my account before i write another reel.. This is the cleanest content workflow i've built on claude. give it your IG first. 4 prompts handle the rest.. niche research, the reel script, the hook, and the daily automation.. the whole loop is basically, give claude your IG → find what's working → write retention-optimized scripts → engineer the hook → automate the daily output.. ▫️ Setup: give claude your instagram open claude code. claude code has a built-in web tool that browses any public URL. or install any agentic browser like Browser Harness or Firecrawl or Comet browser paste this with your handle filled in: "Browse and pull the last 30 reels and posts. Analyze my recurring topics, top-performing hooks, formats, and engagement patterns. Then map out my actual audience and what they consistently respond to." claude reads your profile, pulls every reel down, and now has the context to personalize every prompt below to YOUR account, not a generic niche. if you're on claude desktop, the same works with firecrawl MCP connected. ▫️ Prompt 1 find what actually goes viral in your niche: "Analyze the highest-performing Instagram Reels, TikToks, and Reddit posts in the [niche] niche from the last 30 days. Identify repeating hooks, visual styles, emotional triggers, and content formats that consistently generate high engagement. Then summarize the 5 strongest content angles optimized for AI-generated content and short-form videos." run this after the setup. you get 5 angles backed by what's already working in your niche, cross-checked against what's already working on YOUR account. ▫️ Prompt 2 write a high-retention reel script "Write a short-form Instagram Reel script about [topic] with an aggressive hook in the first 2 seconds. Create immediate curiosity, tension, or controversy to stop scrolling, then deliver a fast and satisfying payoff. Keep it under 30 seconds and optimize the structure for watch time, replays, comments, and shares. Finish with a subtle CTA." the line that matters: "optimize the structure for watch time, replays, comments, and shares." claude writes for the metrics, not just the word count. ▫️ Prompt 3 engineer better hooks "Study the top-performing Reels in [niche] and break down the hook structure, pacing, and emotional triggers used in the first 3 seconds. Then generate 5 new hook variations that are even more curiosity-driven, emotionally charged, and optimized to stop scrolling instantly. Focus on triggers like surprise, fear, ego, urgency, or desire." most reels die in the first 2 seconds. this prompt has claude reverse-engineer what already works, then give you 5 sharper versions to swap in. ▫️ Prompt 4 automate the whole workflow "Build a complete AI-powered content workflow for Instagram in the [niche] niche. The system should identify trending topics daily, generate high-retention scripts, create matching AI visuals, turn them into short-form videos, and generate optimized captions and hashtags. Structure everything as a repeatable workflow designed for consistent daily posting and growth." once the niche and script structure are validated, this turns it into a daily loop. one prompt that handles topic → script → visual → video → caption. these 4 prompts are the building blocks. the setup is what makes them yours. your real value is in the [niche] you plug in. content workflow built in one weekend, daily posting on autopilot from monday.show more

anthropic will sell you opus 5 at $200/mo. openai... will sell you gpt-5.6 at $200/mo. neither will tell you the fix that drops your bill to $20 was posted free on langchain's blog on july 18 peter steinberger posted one line asking if we'd moved from loops to graphs yet. 24 hours later there was a manifesto. a week later every ai account had a $497 graph engineering course. all of them wrong about the same thing the sentence that ends the argument, buried in a langchain post nobody quoted: loop engineering isn't an alternative to graphs, so much as a simple version of them the machine, five layers, each wraps the one below: L1 the ask · 23% of errors (anthropic red team, q4 2024) -> "just add more instructions" burns tokens with zero accuracy gain -> real fix: examples, output schema, constraints as positives L2 the context · where 90% of you actually die -> 140,500 tokens where 18,000 would work, 8x the price for the worse answer -> real fix: retrieve, rank, compact, clear dead tool outputs L3 the harness · 31% of "model bugs" are harness bugs (openai safety eval, 2024) -> unbounded file perms = avg $23,400 incident. sandboxed = $0 (stripe internal) -> no timeout = $847 median in api fees before you notice -> real fix: explicit scopes, timeouts, human-required gates L4 the loop · "it stopped" is a loop exit problem -> the verifier said "looks good" to garbage. again -> real fix: machine-checkable exit test, turn cap, rubric L5 the graph · only 12% of teams use graphs in prod (stanford hai, n=2,841) -> 58% of graph failures are wrong-agent selection, not model -> teams abandon graphs saying "harder to debug than a loop." that's a harness problem -> real fix: name every node's specialty, delete decoration fix down, not up. a symptom at layer 4 usually originates at layer 2. a bigger model on a broken harness is a smarter employee locked in the same empty room drop your $200/mo ai sub to $20, check the article belowshow more

i just open sourced the workflow behind $2M AI... video productions... i built 7 skills that run the pipeline end to end, built for Seedance 2.5 and they work in Claude Code, Codex, Hermes or any harness (works best with 1080p using Higgsfield CLI) here's how to use them, in order: /setup writes which image and video models you run into your project, once, so every skill reads the same stack /studio-init scaffolds the whole studio as a file tree from one question, the project name /film-breakdown walks your script scene by scene and writes a 22-field card for every shot /reference-board locks your references into a visual bible, a caption on every image and a ban list for the rest /asset-passport writes the exhaustive descriptor every later prompt will quote word for word /stress-test combat-tests each asset and flips it to locked only at 10 out of 10 repeatability /shot-prompt refuses to run until everything in frame is locked, then writes the 15-block prompt and logs every attempt get access to the skills and full breakdown of the pipeline in the article below:show more

in a similar vein to Kieran Klaassen & Every... 📧 's "compound engineering", I've used a prompt every day for the past few months called "self-improving Cline" (linked below). at the end of the task, it evaluates any rule I had turned on and proposes updates based on any friction points during the task. now, all my clinerules are extremely refined and improving every time I use them.show more

FABLE 5 + HIGGSFIELD TURN A $35,000 ANIMATED SITE... INTO A ONE-SESSION, $12 BUILD. HERE'S EXACTLY HOW. a studio runs this across four people and three weeks. you run it across one chat window and one afternoon. THE BUILD, STAGE BY STAGE: STAGE 1 - THE CONCEPT Claude reads your brief and scripts the scroll before a line of code exists - what the visitor feels at second 3, 15, 40. prompt: "read this brief. script the scroll beat by beat, then scaffold the project with GSAP ScrollTrigger + Lenis." STAGE 2 - THE VISUALS (Higgsfield) every hero shot, transition, and ambient loop comes out of 30+ generative models - matched to the story, not pulled from a stock library. prompt: "generate the hero sting and one b-roll clip per section. 3-5s, high-res, cinematic." STAGE 3 - THE MOTION (Claude Code) Claude writes the ScrollTrigger timelines and Lenis smooth-scroll, extracts frames, optimizes every asset. zero hand-coded keyframes. prompt: "wire the scroll: pin the hero, scrub the video, reveal each section on scroll. keep it 60fps on mobile." STAGE 4 - THE POLISH six cinematic effects baked in, no config: film grain, particles, vignette, glass cards, color tints, scroll pacing. prompt: "bake in the cinematic layer, then QA load speed, mobile breakpoints, and whether the scroll actually lands - rewrite what doesn't." CONNECT HIGGSFIELD (MCP): add it as a custom connector in Claude Code: mcp_servers: higgsfield: url: " one OAuth flow. Claude generates and pulls clips directly - no exporting by hand. THE MATH: → what a studio charges: $6,000-$35,000+ → what it costs you: a Claude sub + a few dollars of Higgsfield credits → what it takes: 4 people + 3 weeks → 1 operator + 1 session the pipeline was the moat. it just became four prompts. Follow me, comment "MATH" and I'll send you the full step-by-step Playbook. full breakdown in the article 👇show more

Seedance 2.0 + Claude Code is f*cking insane 🤯... I built a Claude skill that creates UGC ads on demand. One product + one prompt = the AI creator, the script, the scene-by-scene shot list, and the finished video. All inside Claude Code. Perfect for DTC brands and agencies who can't afford to keep paying $500-$1,500 per UGC video and waiting 2 weeks for revisions. This skill eliminates the entire loop: → Tell Claude the product, ad angle, and length → Skill writes the GPT Image 2.0 prompt to generate the AI creator from scratch → Skill writes every scene prompt, dialogue line, and delivery direction → Pipes it into Seedance 2.0 with character + product + voice locked → Speed up + caption in CapCut → Ship the ad in 20 minutes No more paying $11 per video on Arcads. No more 2-week revision cycles. No more PR boxes to creators who ghost you. What you get: → Perfect character consistency across every scene → Voice consistency that holds clip-to-clip → Real product fidelity using your actual product photo as a reference → Multi-scene day-in-life, testimonial, and action-shot formats out of the box Built 100% with a Claude skill + Seedance 2.0. I recorded a full step-by-step tutorial showing the exact workflow so you can build these AI UGC ads yourself. Want the full breakdown? > Like this post > Comment "UGC" And I'll send it over (must be following so I can DM)show more

SOMEONE BUILT A CLAUDE CODE PLUGIN THAT REFUSES TO... WORK UNTIL YOU DO PUSH-UPS OR SQUATS its called workout gate and it is exactly as cursed as it sounds when the hook fires, it blocks your prompt, opens your webcam, and makes you exercise to keep coding > it counts your reps live through the webcam with mediapipe, no honor system rounding down > only releases your prompt once you actually finish the reps > quit halfway and the leftover reps get saved as debt for your next session > chill, demo and hardcore presets, plus prompt based, time based or random triggers > tracks stats, streaks and personal records right in the claude code statusline we automated the coding, now we're automating the part where we actually take care of ourselvesshow more

> open ChatGPT > ask it to research 50... AI tools > it starts. one by one. slowly. > 45 minutes later you're still waiting > it forgets what it found on tool #12 by the time it hits tool #30 meanwhile: > open Kimi Agent Swarm > type one prompt > it spawns 50 sub-agents. one per tool. all running at the same time. > walk away. grab coffee. > come back to a finished spreadsheet. 50 rows. fully cited. exported to Excel. one prompt. 300 parallel agents. 4,000 coordinated steps. finished files, not chat replies. this article is the full guide. every prompt pattern. every honest limit. every use case.show more

AGENT ARCHITECTURE ROUTES WORK. IT DOES NOT REMEMBER WORK.... THAT GAP IS WHY YOUR LOOP KEEPS FIXING THE SAME BUG TWICE. these are two different engineering problems. every agent that silently drifts is missing one of them. architecture answers what runs. harness → loop → graph. it defines the tools, the retries, the branching routes, the approval gates. context ops answer what the run knows. write → read → compress → isolate. it defines what gets saved between attempts, pulled in on read, summarized on overflow, and split across sub-agents. for two months i believed a solid harness plus a verifier loop was enough. my coding agent kept re-discovering the same test failure across retries. the loop was working. it just had nowhere to write what it had already learned. here is the decision rule: if your agent forgets across restarts, add write and read. if it stalls on long tasks, add compress. if two sub-agents step on each other, add isolate. architecture without context ops is a well-routed system with amnesia.show more

Claude Fable 5 is insane for voice-of-customer research 🤯... I just built a Claude Code skill that catches your customers quoting your own ads back to you. It reads your reviews, cross-references every recurring phrase against your website + ad copy, and sorts your "voice of customer" into three piles: Planted, category-standard, organic gold. All inside Claude Code. Perfect for DTC brands and creative strategists who brief ads off review mining. If you're pulling ad copy from your reviews, some of that language is real customer voice, some of it is your own tagline, and every time you re-use it, you're marketing to yourself a little harder. This skill breaks the loop: → Drop in any review export (Judge .me, Okendo, Amazon, Shopify) → It scrapes your site + ad copy automatically → Every recurring phrase gets 3 forensic tests (overlap, independence, category) → Verdicts come with receipts: counts, sources, confidence levels → Dark-mode dashboard + 5 ready-to-test hooks from the gold pile No API keys. No pip installs. No copy-paste prompt rituals. What you get: → The "planted" list — phrases you taught your customers (stop briefing off these) → The organic gold list — language customers use that your ads never have → 5 hooks built from real customer phrasing → A dashboard your whole team can read Runs 100% in Claude Code Want full playbook for free? > Like this post > Comment "Claude" And I'll send it over (must be following so I can DM)show more

This is genuinely insane 🤯 I sent the same... prompt to 2 Claude Opus 5 agents 1 agent used no MCPs 1 agent used 2 MCPS the goal was to clone a very famous game, that has over 4 billion downloads and the results are scary.. The 1st agents game looks pretty basic. but has all the mechanics in place and even has power ups. The 2nd agents game looks polished especially for 1 single prompt. the 2nd agent used higgsfield mcp to create images for all of the assets then sent those images to Meshy AI with a prompt to create them it also generated all the UI elements. the results speak for themselves. you need to start MCP maxxingshow more