The work I value most sits between product and engineering, closing the gap where design, code, and systems meet. Same instinct drives the tabletop games I design on the side.
I design and ship my own front-end PRs, in one loop.
I treat design systems as products, judged by whether a non-designer can build with them.
I make them machine-readable for AI agents, and stay honest about where the tools fall short.
What I'm known for
Context engineering
Systems built for machines to read
The decision I'm proudest of: stop treating AI's inconsistent output as the problem and treat it as missing context. Every component spec'd with what an agent must never generate.
Opinion
AI is enablement, not deskilling
AI lets skilled people do things that were too hard before. The risk is real, but it sits with the person, not the tool.
How I work with it
A multi-agent stack, weighted to my gaps
I deliberately weight my stack toward technical agents because my engineering background is lighter, and I separate the thinking tool from the building tool.
Honest about it
I challenge what the AI hands me
These tools favour their own output and will happily agree with you. The moment you stop challenging that is the moment it quietly steers you.
Designer to designer
Ask the real questions.
Craft, AI, design systems, the seam with engineering. Ask the brain anything, it answers in Tyren’s own words.
Ask anything, or paste a job description for an honest fit read. Pasted JDs aren't stored.
