OPEN SOURCE / PRACTICAL ENGINEERING

Your agent wrote 10,000 lines.
You still have to review them.

Or maybe you're setting up yet another Mac, losing your shortcuts, or copying agent instructions between projects. Find a workflow that fixes the problem — then get the tools to make it stick.

Less manual setup. Less repeated work. More time for the actual problem.
THE PROBLEM01 / CODE REVIEW
+10,428 LOC
One agent-generated change.
One human responsible for the result.
review / working-tree⌘K
14@@ verify changed behavior
15+ review by behavior, not file count
16+ navigate changes in your IDE
17 run tests at system boundaries
18- hope the diff looks fine
WORKFLOW BEFORE TOOLING→ /guides

01 / START WITH THE PROBLEM

Where are you losing time?

The useful part isn't the repository. It's understanding the workflow that makes the repository worth having.

01

Your agent changed thousands of lines. How do you review them?

Navigate changes, inspect diffs, and verify behavior without reading every line as an isolated text block.

CODE REVIEWExplore
02

Setting up another Mac? Stop doing the same work again.

Keep shortcuts, tools, and configuration in one reproducible setup instead of rebuilding them by hand.

DEVELOPER SETUPExplore
03

Your agent skills work on one machine. What about the others?

Manage reusable skills at their source and install them where they are actually needed.

AGENT WORKFLOWSExplore

Long-form guides are published externally when ready. No draft articles are presented as published work.

02 / OPEN-SOURCE IMPLEMENTATIONS

Don't build the setup twice.

Learn what a workflow needs. Then take a working starting point instead of rebuilding every piece.

Explore all open-source projects

03 / ENGINEERING

Need to evaluate my engineering work?

See the projects, technical decisions, and professional background behind the tooling.

Review my work

04 / PERSONAL SYSTEMS

Where is your day costing you?

Explore the recurring problems across work, sleep, training, and everyday life — and the systems built to address them.

Explore the 24-hour map

STAY IN TOUCH

Have a specific problem worth solving?

Follow the public work on GitHub, or get in touch if you want to discuss an engineering workflow.