Everything here runs our studio every day. None of it was built to be a product, which is exactly why it is worth reading. Free, MIT licensed, no sign-up.
Running a small studio for several clients at once creates a specific set of problems. Your machine ends up holding seven clients' logins. Your notes and settings drift apart across three computers. A client's website breaks quietly and you find out when they do.
We solved each of these with something small and boring, then kept using it for months. These are those tools, with the client names taken out and the rough edges documented rather than hidden.
One isolated Windows account per client, created in a single command. Separate desktop, separate browser profile, separate app logins, and an explicit deny so a client workspace can never read another client's credentials. Heavy folders land on your biggest drive instead of filling up C:.
View on GitHub ↗Check a client's website every morning with Playwright, then send them a branded HTML health report. Measurement and judgement are kept deliberately separate, so the report engine can never invent a number it did not measure.
View on GitHub ↗Keep one Claude Code configuration in sync across every machine you work on. A shared folder, robocopy, and newer-file-wins. Deliberately does not sync credentials or session history, and explains why.
View on GitHub ↗Pull remote job listings from six sources in one command, dedupe against everything already seen, rank against lanes you define, and write one spreadsheet. Five of the six sources need no API key. It reads listings and never applies to anything.
View on GitHub ↗Why give these away? Because the useful part of a small tool is rarely the code. It is the two hours somebody already lost finding out that removing inheritance from a Windows folder strips every permission on it, or that a cloud drive picks a different letter in every user account.
Those lessons are written into the READMEs rather than left as scar tissue in a private repo. If one of them saves you an afternoon, that is the whole point.
A fair warning: these are studio tools, not products. They do one job on one setup and they will need editing to fit yours. The READMEs are honest about what each one does not do.
This is the kind of thing we build in the background while running the day to day. Let us look at what your business keeps doing by hand.
Book a Strategy Call ↗