Dive Club 🤿 — Episode Summary

Episode: Kyle Zantos – Designer’s Toolkit for Claude Code
Host: Ridd
Guest: Kyle Zantos (UX Tools Labs lead)
Date: January 7, 2026

Episode Overview

This episode is a deep, hands-on discussion between host Ridd and design engineer Kyle Zantos about the evolving toolkit for designers integrating with AI—specifically, leveraging Claude Code, modern code editors like Cursor, and design engineering workflows. The goal is to provide designers actionable tactics and philosophies to navigate new AI-driven toolstorms, level up their technical skills, and avoid getting lost in the noise.

Key Discussion Points & Insights

1. The State of AI-Driven Design Tools (00:00–06:00)

• Both host and guest discuss the overwhelming pace of new AI tools and the challenge of staying relevant in design engineering.
• Core insight: There’s no “definitive” way—everyone’s toolkit is (and should be) different.

Quote [00:12] — Kyle Zantos:
"We're in a really Magellan exploratory era with all this stuff. Nobody really has definitive answers."

2. Cursor & the New Visual Editor for Designers (01:25–04:30)

• Kyle reflects on updates to Cursor, including its hybrid visual editor for code.
• Cursor’s positioning blurs the line between code and what Figma-using designers expect from visual tooling.
• Tweaking visual components (like padding/spacing) via Cursor allows for instant iteration without getting stuck in prompt loops.

Quote [03:18] — Kyle Zantos:
"It’s keeping you out of the prompt loop that I think designers can get stuck in or annoyed by... It lets you play and experiment quickly."

• Real-world example: Building and tweaking a custom NFL pool app for friends.

3. Entry Points for Designers New to AI-Driven Coding (06:20–08:00)

• Ridd asks if Cursor is the first “production-ready” code editor for designers.
• Kyle’s answer: Yes, especially for those intimidated by terminals and CLI tools. The UI extensions in tools like Cursor, Codex, and Factory are friendly starting points.
• Encouragement to not get hung up on the “best” setup; user-friendly interfaces lower the barrier for designers new to engineering.

4. Experimentation Philosophy: Building a Designer’s Workbench (08:06–13:16)

• Designers should focus on creating experimental playgrounds, not on assembling the perfect toolchain.
• Kyle builds custom studios to experiment—e.g., for sound-on/off waveforms, retro-futuristic themes for his site, and even a hologram video tool.
• Collect effect snippets and patterns so they’re reusable in future projects.

Quote [09:09] — Kyle Zantos:
"Everybody’s going to start having their own workbench and that wall at the workbench is going to be a little bit different for everyone."

5. Prompt Language & Learning by Referencing Others (12:52–17:07)

• Ridd: How do you describe subtle UI effects to an LLM when you don’t know the right terms?

• Kyle: Two tricks—

  1. Learn the developer nomenclature: Use terms and adjectives that LLMs are likely trained on (like “glitchy CRT scan lines”).
  2. Reference and feed source material to Claude Code (tweets, threads, images) so it can interpret and implement effects directly.

• Example: Applying James McDonald’s multi-layer shadow technique to buttons via direct prompt and code snippets.

Quote [13:16] — Kyle Zantos:
"If you find a source of something you think is really cool, tell Claude Code to go figure out how to do it."

6. Systematizing Inspiration: Compound Engineering Skills (17:49–23:18)

• Kyle aggregates codepens, tweets, and articles from favorite minimalist coders (like Jay Tompkins, Jakob Webb) into Claude Code plugins and skills.
• Using the "compound engineering" plugin, Kyle builds a custom “visual audit” agent for design philosophy checks. This automates design reviews for consistency and polish.

Quote [18:16] — Kyle Zantos:
"I used them to make a like visual design interaction design auditor that is invoked with this skill..."

7. Managing Your Claude MD Files (34:54–39:06)

• Store only universal, truly reusable knowledge in global Claude MD files to avoid context bloat.
• Use project- and component-specific Claude MD files where appropriate.
• Trends and recommendations change rapidly—philosophy and principles matter more than hot workflows or “10x” hacks.

Quote [38:08] — Kyle Zantos:
"Be slimmer on your Claude MDs, both global and local project level. And even further, you can make CLAUDE MD files in individual subdirectories..."

8. Control Panels for Parameter Tweaking (28:24–34:54)

• Easy, practical win: use a parameter panel like Leva (or Tweak Pane) in React/Next.js projects so designers can iterate on variables visually.
• Claude Code can set up these control panels from natural language prompts, making experimentation with interaction timing and animation simple.
• Advice to “collect knowledge chunks” as you discover useful workflow bits.

Quote [32:21] — Kyle Zantos:
"Just tell Claude Code I want to use Leva. This is the stuff I want to be able to control. Make a plan."

9. The Importance of Structured Experimentation (“Tune-up Days”) (45:02–46:50)

• Kyle schedules “tune-up days” dedicated exclusively to improving his toolset, exploring new plugins, and cleaning up project structures without worrying about deliverables.
• Encouragement to block off time for learning—try free trials, sign up for tools, watch that tutorial you’ve saved.

Quote [45:43] — Kyle Zantos:
"Giving yourself the time to play is a really good way to give yourself the license to go grab that tool, go sign up for that trial. Give it a shot."

10. Budgeting and Stacking Subscriptions (41:20–46:50)

• UX Tools Labs is working to distill which tools matter, since not everyone has a “blank credit card.”
• Strategy: combine $20 subscriptions from types of services (e.g., Claude Code, Factory, Cursor) to maximize access for $40/month.
• Higher-tier Claude Code ($100/mo) is almost unlimited and reasonable for heavy users.

Notable Quotes & Memorable Moments

• Philosophical Approach:
  "What I did find was it’s easy to get caught up because that stuff changes so fast. The recommendations from four months ago almost certainly are not ones you should follow today unless it’s a philosophical thing." — Kyle Zantos [38:32]

• Re: Personalized Toolkits:
  "Like how many pedals and amps and guitars and pickups... There is no answer to what’s the best setup. We’re basically in that territory with AI tools." — Kyle Zantos [39:43]

• On Automation and Taste:
  "This creates that very clear, tangible mechanic that I can use to act on my taste... Now I can actually use it instead of just pointing at it and saying that it’s good." — Ridd [25:20]

Practical Takeaways & Next Steps

• Start with UI-friendly tools (Cursor, extensions) if you’re new to AI code editing.
• Experiment bravely, but avoid tool overwhelm—philosophy matters more than the specific tools-of-the-moment.
• Systematize inspiration—feed threads/articles to Claude Code for code translations and tailored style audits.
• Use control panels like Leva to make parameter tweaking visual and approachable for designers.
• Keep Claude MDs concise to avoid bloat; subdivide where context-specific.
• Schedule intentional “tune-up days” to explore, update, and play without deliverable pressure.
• Combine subscriptions for value; revisit how much you’re paying and using for your needs.

Suggested Resources & Links Mentioned

• Compound Engineering plugin (for Claude Code skills)
• Leva Control Panel (parameter editor for React/Next.js)
• UX Tools Labs (for tool reviews)
• Notable designers referenced:
  • Jay Tompkins
  • Jakob Webb
  • Emil Kowalski
  • James McDonald

Timestamps for Important Segments

• 00:12 – “The Magellan era” of AI tools/philosophy
• 01:25 – Cursor’s new visual editor
• 08:50 – The philosophy of tool selection
• 13:16 – How to describe effects to AI
• 17:49 – Building your own design audit agent
• 28:24 – Using Leva for easy parameter control
• 34:54 – Managing global vs local Claude MDs
• 41:20 – Budgeting for subscriptions and maximizing access
• 45:02 – “Tune-up days” for skill/tool growth

Tone & Language

Open, exploratory, honest about uncertainty, and focused on practical, actionable experimentation. Both speakers are excited about learning and lowering the barrier for designers to become more technical, but emphasize craft, intentionality, and personal fit over “hype cycles.”

For more resources and full episode notes, visit Dive.club.