Toolinko
I build what I need as I go. Toolinko is the toolkit that grows out of that work, and the tooligans are its little tool hooligans: scrappy, lightweight and capable of quite a lot.
Each has a particular job: looking at an image together, assembling a performance, checking an interface or preparing an application.
These workflows start with the materials already at hand. A marked image, unordered voice notes, a partly working page or a job listing can be enough to begin. The tool's job is to make those materials inspectable and carry a decision into a precise operation.
The tools
| Tool | Starting material | Work it supports |
|---|---|---|
| Sketchiebook | An image and something worth pointing at | Shared visual reference, selected regions and conversations |
| DevNotes | A live page and something worth pointing at | Visual feedback, with the note and page context kept together |
| Studio | Screen recordings, voice takes and editorial direction | Picture editing, performance mapping, sound repair and verified delivery |
| Liquid | Frontend source and the page people use | Code inspection, continuous layout checks, accessibility and functional checks |
| Applyekhine | A listing, a résumé and known answers | Relevance, application preparation, verified fields and human submission |
A practical working relationship
I decide what the work means, what matters and whether the result is right. The agent takes responsibility for inspecting the materials, carrying out the operation and checking what changed.
The useful review surface depends on the work. An image note can identify several related details. A crop preview can reveal a missing part of the frame. A spectrogram can isolate a sound. A form readback can show whether the intended value reached the intended field.
Sources & further reading
- The focused tooligan package modelProject documentation