Skip to content
Jigwright

A jig guides the cut

Tools that check their own work.

A jig doesn't trust a steady hand. It registers the work against a reference edge so the cut lands in the same place every time. We build software the same way: our tools verify what they did, then tell you the truth about it.

Now shipping

HullForge

Drive a running Unreal Engine 5 editor from Claude. Inspect and edit assets, materials, landscapes, Blueprint graphs and PCG graphs. Around fifty typed tools, and every write is verified.

Verified write
setM_Rock.TwoSided = true
readM_Rock.TwoSided -> true
okverified. saved. 4.2 KB on disk.
Every mutation is applied, re-read from the object, then compared. A write that silently did nothing is reported as a failure.

How we build

Verify the work, don't assume it

A tool that reports success without checking is worse than one that fails loudly, because you find out later and further from the cause. Every write our tools make is read back and compared.

Refuse before you destroy

When an edit cannot be saved, or a delete would break something that depends on it, the right answer is to stop and say exactly what is in the way. Not to proceed and leave you to discover it.

Say what actually happened

Error messages name the thing that went wrong, where it is, and what would fix it. "Operation failed" is not a message, it is the absence of one.

What's next

Jigwright builds development tools, games, and integrations. HullForge is the first thing we've shipped, and more is in progress. If you want to know when, get in touch.