From UI patterns to product judgment
Patternry is now Pathmode.
We started by helping teams build the surface of software consistently. We ended up rebuilding the layer that decides what to build at all.
Patternry began as a design-systems and UI-pattern library — a way to keep the surface of software coherent as teams scaled. It was useful work. It also wasn't the work that decided whether the product was worth building in the first place.
The gap we kept watching show up wasn't how teams built. It was what they built — the layer of judgment between user evidence and the next line of code, where the wrong answer wastes a quarter and the right one is hard to articulate. AI removed the cost of building. The cost of building the wrong thing got louder, not quieter.
Pathmode is what we built once we stopped trying to fix the chrome.
What Pathmode is
The product judgment layer for builders making products with AI.
Pathmode turns user evidence — tickets, quotes, observations, requests — into intent specs that say what to build, for whom, and why. The discipline is called Intent Engineering.
Intent isn't a contract you compile. It's judgment under evidence — the part of product work that agents can't do for you, and that everything downstream depends on.
Where to go from here
Read the thesis
The Artifact of Judgment
Why product judgment can't stay tacit anymore — and what changes when you externalize it.
The discipline
What Is Intent Engineering?
The discipline that replaced prompt engineering — what it is, why it matters, how to practice it.
Try it
Explore Pathmode
Turn your user evidence into an intent spec your team and AI agents can execute from.
Looking for the old Patternry content? Many of the design-systems ideas live on in how Pathmode structures specs. The rest is in the blog archive.