Wednesday, October 7, 2026ArchiveSearchAsk the paper

The Computomatix Times

All the posts fit to save — curated from @computomatix's bookmarks & likes on X

Free Library Pairs 226 Claude Opus 5.5 Motion Graphics With Prompts

Prajwal Tomar promotes a gallery of motion graphics created with Claude Opus 5.5, each shown alongside the exact prompt that produced it, collected from posts on X and credited to their creators.

Original post · 1 min read
This guy collected 100s of Opus 5.5 motion graphics from X and put the exact prompt next to every single one.

Opus is CRAZY good at motion, most people just get stuck on what to type. This fixes that.

Pretty sure this is the best free motion library on X right now.
p4n @p4nthera_
I built a growing gallery of motion graphics made with Claude Opus 5.5, each shown next to the prompt or skill that made it.

226 so far, all pulled from posts here and credited to their creators.

prompt-motion.com/
♥ 99 · ⟲ 5 · 👁 16.0KView on X ↗

More in Agents & Dev Tools

Vercel's Guillermo Rauch Explains Turborepo's Migration From Go to Rust

Guillermo Rauch says Vercel moved Turborepo from Go to Rust, a migration that was controversial internally due to human costs. He argues that with AI agents the calculus has changed, so what is best for humans is no longer necessarily best for business.

Original post · 1 min read
DHH is fundamentally right about Rust. For context, Vercel has been undergoing a Rust-ification (carcinization, technically 🦀) for a while.

One of the first projects we migrated was Turborepo, from Go to Rust¹. The migration completed, but the RoI was actually quite controversial internally.

While Rust was in our eyes better for low-level OS access, something crucial for a build system like Turbo, the human migration costs were very sustantive.

Go is very fast. It's beautifully designed. It's easy to iterate on. We were very conflicted about the migration, because it was *humans* writing the code, *even if we knew Rust was a better choice*.

The calculus has now changed. What's "best for humans" is no longer necessarily "best for business".

FWIW, it's also quite unlikely that Rust is the end-all-be-all toolchain. I'm quite certain there's greener pasture ahead, because Rust itself was designed before the 'supersonic tsunami' of agents hit.

¹ https​://vercel.com/blog/how-turborepo-is-porting-from-go-to-rust
♥ 3.2K · ⟲ 152 · 👁 352.7KView on X ↗

Boris Cherny Says Prompting Claude Should Feel Like Talking to a Coworker

Boris Cherny explains his approach to prompting Claude, advising users to give clear goals, specify effort level and verification steps rather than relying on heavy scaffolding.

Original post · 1 min read
I am surprised that people are surprised this is how I prompt Claude.

Talk to Claude the way you would a coworker. There's no secret to prompting. There's no need to be overly scaffolded or prescriptive for most tasks -- give Claude a goal, and it will figure it out.

Back in the Sonnet 3.5 days, your prompt mattered a lot. Nowadays, it's much more important to communicate to the model:

1. What you want it to do
2. How much effort you want it to spend
3. How it should verify that it did the right thing
Boris Cherny @bcherny
Prompt
♥ 12.1K · ⟲ 720 · 👁 1.1MView on X ↗

Eric Raymond Highlights Open-Source Rust Clone of Photoshop Built via LLM

Eric S. Raymond shares the photocraft GitHub project, a clean-room open-source reimplementation of Photoshop that he says was likely generated by decompiling the app, converting it to a spec and prompting an LLM for Rust. He argues this threatens closed-source software.

Original post · 1 min read
This is the doom I predicted a few days ago, coming for Photoshop. A clean-room open-source reimplementation.

No prizes for guessing that they decompiled Photoshop to source code, processed that to some kind of non-code specification language, then fed the spec to an LLM with an instruction to generate Rust.

Adobe just got nuked. And closed source is dead, dead, dead.

github.com/storytold/photocraft
♥ 15.7K · ⟲ 1.4K · 👁 3.5MView on X ↗

Nat Eliason Details Fourteen Ways His Bot Setup Automates Work

Nat Eliason lists fourteen functions of his bot setup, including a chief-of-staff agent that drafts emails, specialist agents per work lane, and cloud coding agents that open pull requests from Linear issues. He notes GrokBot as a substantial improvement over his previous OpenClaw setup.

Original post · 2 min read
Things my @bot setup does that still blow my mind:

1. A Chief of Staff who opens the day pulling open loops from email & tasks and suggesting things it can knock out before 7am.

2. After every meeting, decisions get folded into Notion, Linear, and Todoist — not left rotting in Granola

3. Every email starts as a draft. The CoS bot scans my email every ~2hr and drafts replies to nearly everything — including checking my cal for availability and finding requested attachments / links

4. A specialist for each lane: curriculum, engineering, coaching, hiring, content, ops, and one for every single piece of software

5. Routines that keep running while I’m offline (e.g. monitoring Sentry errors in our apps and proactively fixing things)

6. Group rooms where 2–4 bots share one project thread instead of me copy-pasting context

7. Cloud coding agents that pick up Linear issues and open PRs after running the list of open work by me EoD — then squash-merge to main when it’s done

8. Meeting prep briefs pulled from Granola + Notion before I walk in

9. A growing shareable knowledge base in Notion + a GitHub repo that we update daily based on what happens at school

10. Student progress look-up across Expertise, Followers, and CoFounder without inventing numbers — chat anytime to see where a student is on their business work

11. Mentor Mind that coaches me on how to hold the bar without inventing doctrine

12. Todoist as a central task list where it logs things it’s blocked on for me, or from meetings / emails — and I can paste links into chat to direct it how to solve them

13. Engineering work is automatically tracked in Linear so my and the product teams’ bots don’t collide with each other

14. Presentations spun up in Gamma / Claude Design without me opening a slide tool

15. Plaud / live capture → notes the bots can actually act on

Probably more but these were the immediate ones we thought of.
Nat Eliason @nateliason
GrokBot feels like absolute magic at this point, a meaningful leg up on my previous OpenClaw etc. setups.

And with how easy it is to setup, there's really no excuse now.
♥ 2.1K · ⟲ 207 · 👁 522.0KView on X ↗

Open-Source Tool Rea Uses Agents to Reverse Engineer Binaries

GitHub - morluto/rea: Reverse engineer anything with agents, from app behavior down to native binaries.

A trending-repository post highlights rea, a GitHub project that uses agents to reverse engineer applications, from observed app behavior down to native binaries. It gained 2,963 stars in the past 24 hours.

Original post · 1 min read
Trending repository of the day 📈

rea

Reverse engineer anything with agents, from app behavior down to native binaries.

Last 24h: 2,963 ⭐
Total: 6,869 ⭐️
github.com/morluto/rea
github.comGitHub - morluto/rea: Reverse engineer anything with agents, from app behavior down to native binaries.Reverse engineer anything with agents, from app behavior down to native binaries. - morluto/rea
♥ 2.7K · ⟲ 314 · 👁 135.2KView on X ↗

DHH Predicts Software Development Boom as Coding Agents Take Over

Over my dead pencil

DHH argues in an essay that falling development costs will spark a bloom in software creation and that coding agents now make hand-writing most code obsolete. He urges programmers to stop relying on pencils and start building.

Original post · 1 min read
"We're about to see an absolute bloom in software development as the price of development plummets and everyone realizes how much automation we still have left to do in this world... Don't go down with the pencils. There's so much to build. We need you." world.hey.com/dhh/over-my-dead-pencil-fb0f3647
world.hey.comOver my dead pencilTwo weeks ago at Rails World, I told my fellow programmers that it's time to put down the pencils. We're not going to write the vast majority of code by hand an
♥ 3.0K · ⟲ 201 · 👁 151.5KView on X ↗