Latest articles
See all articles →
How We Killed Vibe Coding Chaos: What We Learned Building a 400-PR/Day Multi-Harness System
What we learned building a 400-PR/day multi-harness system: filesystem as state, syntax graph DAGs, isolated runner sandboxes, and zero-LLM deterministic verification.
Your agent builds the 3 thumbnails for YouTube's A/B test
@di-atomic/thumbnail is live. Your agent plans two or three YouTube thumbnails that test real ideas, checks each one reads at the 200-pixel sidebar, makes covers for Shorts and Reels, and picks the frame your video opens on.

Stop guessing video structure. Your agent measures it from a proven hit
@di-atomic/video-analyst is live. Give your agent a YouTube link or a video file and it hands back a reusable template: timed sections, voice-over pace, opening rules and checked shot rhythm that the video-director fills.

Stop guessing your next video. Your agent researches it every week
@di-atomic/video-researcher is live. Every Monday your agent scores competitor videos against their own channel, tests each theme, and drops ranked ideas with the evidence on a board you pick from.

Exit 0 is not a finished video. Your agent now checks it.
A ducking check that reads the mix passes a video with no ducking. @di-atomic/video-editor renders your shot list into one video and proves the voice, captions and timing with four gates that read the file.

Your script fits 60 seconds. Two lines don't. Your agent checks.
A script can fit its total and still overflow a beat. @di-atomic/video-director times every voiceover line against the shot it plays over, in seven measured languages. New in 0.3.0: hand it a template measured from a video you liked, and it plans yours to that pace and hands back what the AI engines cannot shoot.