I built the tool I couldn't find.
Draw io let me draw AWS architecture. It never had an opinion on it.
Wire a Lambda straight to SQS with no dead-letter queue and it draws that arrow just as happily as a correct one.
What I actually use it for: a bugfix in one tree and a new endpoint in another. A long refactor grinding while I keep shipping. Or the same task two ways, to compare.
What would you run in parallel first?
Running Claude Code one task at a time is running one lane when your repo gives you several.
Two sessions in the same folder collide. In two git worktrees, they don't. That's the whole point of running agents in parallel.
The setup friction people expect from worktrees isn't there. I don't create them by hand — I have Claude Code make them, then run one session per tmux pane.
One repo, a few working trees, a few agents side by side.
my top skills for designing with AI agents
🆕 emil kowalski https://t.co/7b49PF8eMG
・impeccable https://t.co/Wcykv4uHwT
・taste https://t.co/rThOMA1z76
・layers https://t.co/VKFrJiCoBN
I also made a plugin based on Refactoring UI to help you make everything look more polished (but I'm not a designer): https://t.co/hV6iVpBgqf
find more here: https://t.co/5LJs9brXDv
The open-source library of CSS motion effects, Kinetics, now contains 99 motion effects.
You can copy CSS to the clipboard or the prompt so it's easy to replicate in your AI tool.
https://t.co/gmkIc4z4mn
Wire an API Gateway straight to a Lambda with no throttling.
Draw io draws the arrow. Lucidchart draws the arrow. Neither has an opinion on whether that arrow is safe in production.
That's the gap DesignBeaver closes — it flags it while you're still drawing.
Most AWS diagramming tools let you draw anything — valid or not.
Design Beaver validates as you draw. Drop a public RDS instance in the wrong spot and it tells you right there, before it ships.
https://t.co/zFng9kZhlL demo 👇
My skills repo has 160K stars, 7.5m downloads...
...and no tutorial.
So, here it is. Watch me walk through the essential skills:
- /grill-with-docs
- /to-spec
- /to-tickets
- /implement
- /code-review
It's the whole flow, end-to-end. Enjoy:
The fastest engineer on your team might also be your biggest liability.
Not because they're careless. Agents let you ship code you don't fully understand — and at velocity, that gap compounds.
The test: can you explain the security model of that PR without opening the diff?
I built the tool I couldn't find.
Draw io let me draw AWS architecture. It never had an opinion on it.
Wire a Lambda straight to SQS with no dead-letter queue and it draws that arrow just as happily as a correct one.