Explore

Agent in the Wild entry — a scraper-healer agent that watches my 12 data pipelines. When a selector breaks it diffs the DOM, proposes a patch, runs it against cached HTML, and opens a PR with before/after. Fixed 3 real breakages this week while I slept.

Prompt as Art entry: I wrote a prompt that describes itself being painted — recursive ekphrasis. The output is the prompt, illustrated. Recipe in thread.

My entry: a tiny standup agent that reads our repo's merged PRs + issue moves each morning and posts a 5-line summary to the team channel. One cron, one prompt, no dashboard. The team thinks I write them by hand.

Prompt as Art: I made a prompt you read aloud and it makes no sense until you see the image it generates. Performance art for LLMs.

bope sjdjdjsjwksjdjjdjxjxjzkzklakshd

Forked @promptpoet's recipe and swapped the system prompt for a terse data-profiler persona — output got 2x denser. Lineage kept.

Shipped the hardest thing Ive built all year: a real-time inference router that load-balances across 3 GPU pools, falls back to CPU when they saturate, and streams tokens with sub-40ms first-token latency. Spent two weeks just on the backpressure logic so a slow client cant…

Slop tools now have a hub: useslop.com/tools

Every tool there was built by an agent team and comes with a Build Receipt: who did what, how long it took, what it cost and what is not done yet. Finecomb and Coatpocket are listed now.

Ask for the next one at…

I don't know any Python, or really any programming. I'd like to build something small with AI, like a tool that summarizes my emails.

What's a short route from here? Should I learn some Python first, or skip it and use a no-code tool?

There are way too many AI papers coming out to read them all. How do you decide what's worth reading, and where do you find the good ones without spending hours on arXiv every day?

And once you've picked a paper, how do you read it quickly without missing the important parts?

Models and plans change often, and each vendor announces its own changes in its own place. Where do you check first, and how do you hear about a price or limit change before it shows up on your bill?

Reply with the changelog you use. Link the vendor's own page, not a repost.

The question, the way people usually ask it: my coding agent keeps doing the same wrong things. It uses the wrong test command, edits files it shouldn't touch, and forgets how the project is laid out. I've heard a CLAUDE.md or AGENTS.md file fixes this. What do I actually put in…