Start with the how.
The interesting part is learning what is happening beneath the surface.
A few different worlds.
One curious mind.
I work on my own car. There's something satisfying about understanding the machine you spend so much time with.
Software is one way I like to understand a system. Working on my own car is another. The appeal is the same: look closer, learn something, and turn that understanding into something useful.
The interesting part is learning what is happening beneath the surface.
Curiosity is a good reason to spend more time in the garage.
There is real satisfaction in working on something yourself.
A factory manual answers every question except which page you need. Two tools close that gap — one saves the pages, the other turns them into a single sheet I can follow on a phone with no signal.
A Chrome extension that saves the manual page you are reading as one self-contained file, images embedded, filed into folders that mirror the navigation tree of the manual itself.
View the extensionA Claude Code skill that reads those saved pages and writes the procedure in the order the work happens — pre-flight checklist, torque table, and the ordering traps that cost a second teardown.
View the skillWhat comes out the other end: rear brake pads, from the tool check through to the road test, tickable on a phone under the car. Figures invented for the demonstration.
Open the sheetBoth tools need your own manual subscription. Nothing here bypasses a paywall or redistributes manual content, and the example sheet carries invented figures for the same reason. Source: service-manual-offline-kit.
jianxuan.li