Happy Wednesday!
So I’m working on Sputnik (newsletter and podcast data for your agents, it’s really useful), and I have a ux.md file in there alongside the code.
It describes who our customers are and the things that are important to them. I’ve shared it before, you can see the ux.md file here.
I’ve been trying to figure out: how can I tell if this is working? How do I eval this? So I remembered that Claude Code stores its conversations locally, so I asked it this prompt:
we have a ux.md file. In the past week, I want to know if your claude sessions have read that and used that information? I am trying to find out in what situations has it been useful or helpful. I’m not sure how much of that you can find out with some certainty.
And it went to work. After reading the past week’s transcripts, here was its answer:
Here’s what I found, with reasonable certainty. I searched the last week’s session transcripts (73 sessions) for ux.md. 28 mention it — but that’s mostly noise, because CLAUDE.md (loaded into every session) contains the pointer “read ux.md before customer-facing work.” So I filtered for hard evidence of an actual read: a cat/sed/Read call on the file, or it distinctive content appearing in the transcript. Four sessions genuinely read it:
[…]
And it found a bunch of instances where it looks like it was used, mostly when we were building features or content directly for end users.
So there you have it. There are some ways to check if your ux.md file actually has an impact.
Health and happiness,
Peter
PS: I am working on some new AI learning series for mce (hands-on AI courses for UX professionals), for a relaunch around October. This ux.md stuff will be in there (with much more detail).
No posts
Comments
Nothing yet. Say the first thing.
Sign in to join the conversation.