Dive Club
Posts
🤿 latent space

🤿 latent space

+ the ultimate Claude skill for design engineering

Ridd
January 14, 2026

It’s no secret designers are playing more in code as of late.

But up until this point it’s felt like I had to make a choice between:

Spinning up my environment and using an IDE
Recreating production in AI prototyping tools

That’s why I’m so interested in what Dessn is building 👀

It allows designers to prototype in the context of their production codebase (without any of the setup).

So I asked the co-founders Gab and Nim to hook it up to the Inflight repo and give me a little demo to see what’s possible.

I’m pretty sold 👀

Listen on Youtube, Spotify, Apple or wherever you get your podcasts 👇

🤝 WITH MOBBIN

There legitimately might not be a tool that the design industry agrees on more than Mobbin…

Over 1 million designers from companies like Airbnb, Uber, Headspace all use Mobbin for design inspiration.

And it makes sense…

It’s highest ROI investments you can possibly make as a designer.

I use Mobbin almost every day to see real world examples of how different products handle specific UI patterns and flows.

It’s invaluable to my practice and I can’t recommend the product enough 👇

🔗 FEATURED RESOURCE

Zantos’s design engineering skill for Claude Code

The Designer’s Toolkit for Claude Code really took off…

In it, Kyle Zantos talks about a “skill” he created to capture the philosophies and tactics of his favorite design engineers on Twitter.

Like you, this blew my mind and I immediately wanted it for myself 😅

So I asked him to share the skill with the community and he agreed! Here’s how Kyle describes it:

A Claude Code agent + skill for motion design audits, trained on Emil Kowalski, Jakub Krehel, and Jhey Tompkins. Get per-designer feedback on your animations—restraint vs polish vs experimentation—with actionable recommendations.

Kyle Zantos

You’re definitely going to want to bookmark this one 👇

🔗 FEATURED RESOURCE

How I do web design

Koos Looijesteijn wrote a list of 30 things that actually helped him as a designer and it’s legit.

It’s all over the place but there are a lot of pointed insights that are worth saving.

Here are a couple of my favorites:

#12: Prototypes should be single-purpose, so you can discard them after testing. You don’t want to maintain a complete shadow product only the design team can truly appreciate.

#22: Team compositions may not always match with a good design process. You may, for instance, find yourself on a team with backend engineers where ideally you’d spend a few months doing research before implementing anything. If that’s how your organization works, now is the time to correct that for the next team. For this one, make the best of it. The engineers may actually find it useful to do some R&D while you’re doing research. If the product manager insists on working agile, maybe you can put only part of your design capacity on iterative development, while the rest uses the outcomes in user research.

🔗 FEATURED RESOURCE

AI Design Field Guide

A new written interview series just launched that I will definitely be following along with.

It’s called the AI Design Field Guide and the first interview is with Barron Webster who is a model designer at Figma.

Check it out 👇

👥 DIVE TALENT NETWORK

Whenever companies I like start hiring, they usually ping me to see if I know anyone great…

So I put together a list of the most talented designers and builders to recommend to companies like Raycast, Lovable, ElevenLabs, and some of my favorite early stage startups.