Log in or create a free Rosenverse account to watch this video.
Log in Create free account100s of community videos are available to free members. Conference talks are generally available to Gold members.
Hands on AI #3: Claude Code for UX people
This video is featured in the Evals + Claude playlist.
Summary
In this final talk in the series, we are not going to write code, but we will dig into Claude Code, and do a deep analysis of why it has taken off the way it has as an agent.
What are the properties and the UX decisions that went into building it that make it such a success? What are some of the things we as UX people can learn from it.
You will go away with a much better intuition around AI agents, how you can set them up yourself or build them for your customers in a more successful way, how to think about adoption and agent UX properties. It’s still very early in this agent journey - get ahead of the pack right now.
Key Insights
-
•
Claude Code is a minimalist AI agent that uses tools in a loop, enabled by post-training models for reasoning and tool use.
-
•
Despite a terminal UI being poor UX by traditional standards, Claude Code creates user feelings of respect, control, and trust through transparency and interaction design.
-
•
Agents like Claude Code operate by the model writing output tokens to its own prompt window, effectively chatting with itself while calling tools to perform actions.
-
•
Context and memory for agents are managed by simple markdown files that describe projects, workflows, or skills, allowing models to have relevant information without built-in memory.
-
•
Claude Code supports multimodal inputs, enabling tasks like analyzing images as well as text or code.
-
•
The 'decade of agents' implies ongoing rapid evolution with agents becoming central to product workflows over years rather than an instantaneous shift.
-
•
Users, rather than designers or developers, should be empowered to define workflows and prompts, shifting traditional roles and responsibilities.
-
•
Model memory is externalized via saved context text files or 'skills' that function like onboarding materials loaded on each session start.
-
•
There is no fixed best practice yet for agent workflows; experimentation and simplicity outperform over-engineering.
-
•
The evolving AI landscape challenges rigid job titles like 'designer' and 'developer,' encouraging more collaborative, role-fluid approaches.
Notable Quotes
"Cloud code wasn’t programmed to do this; it’s a very lightweight system where the model does most of the work."
"Agents are literally models using tools in a loop—they respond to themselves and the tools in chat-like conversations."
"Despite the worst user interface ever, cloud code is the most popular and successful agent that exists today."
"Trust the user and trust the model are the two lessons I’m getting over time."
"Your short term memory is the context window; too big, and the model has trouble accessing everything."
"Skills are like onboarding material for the model; you write them as simple markdown files that describe workflows or tools."
"If you build for the next model, even if it can hardly do something now, it will probably do it well in the future."
"Don’t overcomplicate workflows; the simplest thing that could possibly work is often best."
"We need to dramatically change the hats, the walls, and the workflow of how we work together in design and development."
"You can’t just be a designer adapting UX workflows assuming everybody else’s workflow stays the same; everything is changing with AI."
Or choose a question:
More Videos
"The closer we worked with product ops, the better we enabled our own design and business goals."
Jon Fukuda Jake Burghardt Jose Coronado Natalie Dunbar Denise TillesAll the Ops: Successful cross-functional collaboration
September 10, 2025
"Natalie Dunbar will talk about the convergence of content strategy and design operations and charting a course together."
Alana WashingtonTheme 3 Intro
October 1, 2021
"Embedded squads build domain expertise but risk losing knowledge if someone leaves, while centralized teams help reduce duplicated effort."
Andrew MichaelBuilding a Product Insights Team
March 10, 2022
"I don’t exactly even know who I am if not a researcher."
Nalini P. KotamrajuTwo Jobs in One: Being a “Leader who is a Researcher” and a “Researcher who is a Leader"
March 10, 2021
"Building more ethical, responsible, and humanistic forms of technologies requires diverse and interdisciplinary conversations."
Prayag Narula Rida QadriHCI 2.0: Humanity Deserves the Attention that UX Research has to Offer
March 28, 2023
"Post-implementation reviews help catch bugs or style issues before customers see them, maintaining high quality."
Yunyan Li Anna Le Jen KimUX Best Practices
June 11, 2021
"I tried to do everything all by myself at first and it didn’t catch on because no one else knew I was doing it."
Shipra KayanHow we Built a VoC (Voice of the Customer) Practice at Upwork from the Ground Up
September 30, 2021
"People outside of your design organization are making design decisions; they are also designers."
Dorelle RabinowitzThe Magic Word is Trust
June 15, 2018
"I am in the land of the traditional territory of many diverse indigenous nations."
Sarah BrooksTheme 3 Intro
December 10, 2021
Latest Books All books
Dig deeper with the Rosenbot
How can Rosenbot help me improve the way I phrase UX-related questions?
In what clinical workflow areas is AI currently being integrated and what are the main UX challenges associated?
What are the core UX research tools essential for managing participant recruitment and study logistics in large companies?