Tools we built for our own work, and publish.
They exist because the work needed them. They are used on every build before they are offered to anyone else.
Building is quick now. Turning a reviewer’s reaction into a precise change is still the slow part. spikes closes that loop.
A reviewer clicks the thing they mean on the real page and says what is wrong with it. The note arrives with the element, the page and the viewport attached, in a form a building agent can act on directly.
Open source: a command-line tool, a small widget for any page, and a server that hands notes straight to coding agents. A hosted version keeps reviews in sync across people.
werk holds what you want against what is true. The gap between them is not a problem to solve; held honestly, it is what drives resolution.
A terminal instrument for structural dynamics practice, after Robert Fritz. It computes how each tension is moving from the record of what you did, and an agent works within the structure you declared. It is how the work behind these builds is held.
Describe what you need. The reply comes from the person who would build it.
[email protected]