Every hack
One practical AI hack a day. Steps, a prompt to copy, and what it is good for.
A 94 second launch film from one HTML file
No editor was opened. One HTML file of 436 lines, 14 script lines read by a local voice model, every cut snapped to a 112 BPM beat grid, 11 phone recordings inside a CSS phone, 2,838 frames rendered in 62 seconds.
3 min read →3 print CSS traps that broke my PDFs
Our PDF preview took 11 seconds and still did not match the screen. Printing the same HTML the editor renders, with headless Chromium, took it to 2.5 s cold and a 30 ms render. Three print-CSS traps cost a round each.
3 min read →The feature walkthrough that floated into empty space
An in-app guide fired on mount, tried to anchor to an element inside a conditional section, found nothing, and drifted. The fix is one check per step: is the target in the DOM right now? If not, skip it.
2 min read →Put a 0.25 second judge in front of your AI agents
Big models do the work. Around that work sit hundreds of small yes-or-no questions a day. A small judge model answered 116,097 of them in 20 days, in a median of 245 ms, and only acts alone above a confidence gate.
4 min read →My AI tester took 9 minutes and proved nothing. A week later: 1 minute, one real bug.
When an agent disappoints, most people swap the model. The fix was what it knows before it starts: a steps file instead of a script, a playbook, and a lessons file it writes itself.
3 min read →Lead a team of AI agents, not one chatbot
One lead you talk to, narrow agents that each do one job, and a gate in front of anything you cannot undo. This week the team got its own lanes, a QA runner, a rule book and a voice.
5 min read →Your team’s questions already have answers. Give them a command.
Every week the same four questions hit the team channel. The answers were already in Jenkins, GitLab, the gateway and Jira. Four read-only commands now answer them in seconds.
3 min read →