Claude Code for product managers: research, writing, context libraries, custom to-do system, and more | Teresa Torres

Why has Cloud Code become your buddy? I was writing my notes in my task management tool, and that was Trello. As time went on, I just started to get really worried about how am I ever going to get my data out of Trello. And so I was like, I wonder if Claude can help, and that was like one thing. Maybe I could just do this better with Claude. And by moving my task management to Claude, now Claude sees my tasks, and I can literally start my day and be like, Claude, what's on my to-do list that you can just do for me? I can say, hey, Claude, what's my sales pipeline right now? And because Claude is tagging my tasks, it literally can generate a list of all my sales tasks and where they're at. This has given me a lot of inspiration because I forget a lot of things. It's got a lot going on. Welcome back to How I AI. I'm Claire Vell, product leader and AI obsessive here on a mission to help you build better with these new tools. Today, we have a very practical episode with Theresa Torres, author of Continuous Discovery Habits, which we all know and love, an internationally acclaimed author, speaker, and coach. Theresa's gonna show us how she uses Claude code for basically everything, but especially to manage her huge to-do list, all the information she needs to do a great job and builds a giant context library so she can be, as she says, lazy with her prompting. Let's get to it. This episode is brought to you by Brex. If you're listening to this show, you already know AI is changing how we work in real practical ways. Brex is bringing that same power to finance. Brex is the intelligent finance platform built for founders. With autonomous agents running in the background, your finance stack basically runs itself. Cards or issues, expenses are filed and fraud is stopped in real time, without you having to think about it. Add Brex's banking solution with a high yield treasury account and you've got a system that helps you spend smarter, move faster and scale with confidence. One in three startups in the US already runs on Brex. You can too at brex.com/howiai. Theresa, welcome to Howiai. I am so thrilled with today's episode because we get to see what I love, which is Goodall Claude code in a non-coding environment. And we were laughing before the show. You were just in every directory on your computer straight in the terminal, like this is how we're living right now. So I have to ask you before we get into any of it, why Claude code? Why has Claude code then become your buddy? Yeah, this has been a really gradual evolution. I started like everybody else, like literally in chat GPD in the web. And then I wanted to have an LLM help me with writing and I gradually moved to Claude 'cause Claude's a little bit better writer, although that might be changing. And then, you know, I do code and I mostly code in the AWS environment and this is gonna be really embarrassing. I do most of my coding in the AWS management console. And my husband for like four years has been like Theresa, you just need to use ID. And I was kind of afraid of ID. I literally had no version control. But I recently had a project where one of the things that I built is being integrated into a real production quality product. And I was like, oh, I gotta level up my engineering game. And that got me into VS code. And then because I needed to use like Git and be like a real engineer if I was gonna have something I built go in a real product. And so I had to level up my pretend engineering game. And my husband was like, and look, you can just have Claude in the terminal right here inside VS code. And then that was a game changer. And I think the reason why coding with Claude helped me with all the things we're gonna talk about today is I feel like engineers pair program with Claude when they use Claude code. And I think this idea of pair programming, I pair program now with everything I do, even if it's not programming. So like I pair task manage and I pair right. And I pair everything. - Great. And so let's get into it because you're gonna show us task management. And I mean, the running joke is like every, every third startup is going to be a to-do list. Like if you haven't tried to start a to-do list startup, are you really like an early stage founder? But you have coded yourself a task management platform that works for you. And I'd love for you to walk us through it. - Yeah, and I'll explain why I did this. I actually think the reason why there's so many task management apps is that how we manage our tasks is so idiosyncratic that this is exactly the type of thing that you should build for yourself. 'Cause it can work exactly the way he want it to work, which is part of the magic. But what God be here was I'm a huge note taker. Like instead of thinking out loud, I think by outlining and writing notes. And I was writing my notes in my task management tool. And that was Trello. And this is kind of nightmare-ish because now my notes are locked into a third party tool. They weren't very searchable. And like as time went on, I just started to get really worried about how am I ever gonna get my data out of Trello. And so like I wonder if Claude can help. And that was like one thing. Like maybe I could just do this better with Claude. And then the second thing that got me into this was as I started to get more involved in AI, I forced myself every time I did a task to ask, how can AI help with this? Can it automate it? Can it augment it? Do I like doing it? Do I want AI to do it for me? And by moving my task management to Claude, now Claude sees my tasks. And I can literally start my day and be like Claude, what's on my to-do list that you can just do for me? Or what's on my to-do list where I should be thinking about how you can help? And then it's not on me to figure out how to use AI. Claude's kind of my pair, AI buddy. So what I built is I have a slash command slash today. Are people familiar with slash commands so I describe that? You should definitely describe them. OK. So a slash command is just a Claude code shortcut that we get to define. So I decided it was called slash today. I wrote a really detailed prompt which we can look at. That tells Claude exactly what to do every time I type slash today. So every single morning of my life, even on Saturdays and Sundays with my cup of coffee, I sit down and I literally just type in slash today. And if I run this, it's going to overwrite what I'm going to show you, but we'll run it real live in a minute. But what it does, you can see the summary from this morning's output, it checks my Trello board, so I still use Trello to coordinate with my team. Says there were no new cards, nothing new to add to my list. It generates a today file, which is what we're looking at here in Obsidian. This is, it's gone through all of my tasks that are just markdown files and told me what's due today. We're late in the day, so I've done a lot of my to-do list. I am like every other human. I have a long list of overdue tasks that I have not done. And they always end up at the top of my to-do list. And tasks are things that have due dates, right? Like there are things I have to do by a certain time. I also have a whole folder full of ideas. It's just things that I want to get to someday. And you can see I have four ideas that are currently in progress. These get added to my to-do list every day. So though when I make it to the end of my list, I can be like, OK, what should I be working on that's more long term? And then we're going to talk about this, I think, next. But I do have this kind of plug-in that I created that does research queries for me every day. And then every day on my to-do list, I get my research digest to review and save papers that I want to summarize and learn from. And that's-- it's such a simple workflow. But what's behind the scenes, if I go over here on the left, I just have different folders. These are literally marked down files. We're an obsidian. When I have a bugs folder, I have an ideas folder, I have a task folder. And then if we look at a task, a task has some front matter. So front matter is an obsidian concept. It's just like field type and then value. It's YAML behind the scenes for people familiar with that. And so I have a task, a task has a due date, and then there's tags. And every single one of my tasks has this. And so what's happening when I run my today command is Claude is just searching my tasks folder for anything that has a due date of today. And I have to ask just behind the scenes is the Trello data being pulled via the Atlassian MCP? Or how is it actually accessing all this data as obsidian stored locally? Like, how does this all stitch together? Yeah, so I actually don't use Trello anymore at all. I'll tell you why I have a Trello MCP server. But I don't, like, when now when I want to create a task, I don't go create it on my Trello board. I literally-- we can demo this new task. Send-- thank you to a player. Very sweet. I was blessed. And then Claude has all the context for how my task management system works 'cause Claude is open in my task folder. And you can see here it's creating a file in my tasks. It's at the due date of today. It hasn't added tags, which is kind of a problem. We'll see if it figures it out. Oh, it's being very smart. So because it added something to my today list, it knows it needs to update my today this file that we're looking at. I actually don't want it to do it this way because it's going to remove all my checklists. And I like feeling like I did my stuff. I'm going to just tell it to just manually add it. So that's the strip that it just tried to run and it's kind of telling you the behind the scenes of how this today slash command works. There is a Python script behind this that does that search all the tasks for anything that is due today, search for anything that's past due. And you can see here that now it just shows up on my to-do list. And this sounds so silly, but I didn't have to open a web browser. I didn't have to click through 14 different buttons in a GUI that is constantly changing. I didn't have to click on a date picker and then click a label and then move it to the right list. I literally just typed off the cuffs notes to Claude. And because I work in Claude all day every day, this task window is always open. And then I usually have a second session open for whatever project I'm working on. And so I can always just bounce over and be like, hey, new task or hey, new idea. And it's just the speed of it is what I really love about it. So I don't have to think about anything. And then why put Obsidian in the loop? It's something you already had. It has a lot of context. It's structured the way you want it. You know, these could be just raw Markdown files and you could just x them off the way they're shown above. What do you think that extra layer is for you? I was not an Obsidian user before this. And I'll say I wasn't even comfortable with Markdown at the beginning, like let's go back six, eight months. Like I was not a comfortable Markdown user. There's a few things I like. I like the really tactile, like it's silly, but I like checking the box. I know I couldn't ask. I know I can put an x in a box and Markdown. It's not quite the same. Really what I like is the file browser on the left. And if you'll notice, my vault is not set at tasks. It's set higher than that. So I have, we'll talk about my LLM context, but I have like my LLM context. All my notes across everything. Some podcast files that I use to work with my podcast. This is the research stuff we're gonna get into. All my tasks, some skills that I've been trying to experiment with, my writing. And so I kind of think about Obsidian is my file browser. And because it's all in Markdown, it makes everything I do super accessible to Cloud. And then I can do things like I can say, Hey, Cloud, what's my sales pipeline right now? And because Cloud is tagging my tasks, it literally can generate a list of all my sales tasks and where they're at on the fly. So like for most task management, you're limited to what views they create. Or you can use tags, but who manually tags things? I'm optimistic I'll do that, but I never do it. Whereas in this system, Cloud does all the tagging. Anytime it generates a task, it'll think about what tags to add. And then in my Cloud MD for this project, not for my global one, for this project, we keep a taxonomy of what tags we're using and we kind of manage that. When I see things I don't like, I update that Cloud MD. So I'm co-creating it with Cloud, but Cloud's doing all the heavy lifting. So I want to recap this before we go to the next workflow, which is you've created a slash command in Cloud code to look at your tasks and assemble, basically assemble your tasks. From today, you have a structured task document format in Obsidian that every task goes into with like a title, a due date, some tags that automatically get populated. And some context, and then you have a couple like known commands you can use in Cloud that allow you to add, remove, update, whatever those tasks of a fly. And this just gives you the personalized experience you want for your to-do list connected across all your sources. And then in case it slipped by people, I do want to call out. You noted that Cloud can have sort of like project level instructions and global level instructions. And I think this is something that people don't take enough advantage of, is context scoping their Cloud MD files to the right area, so that you could have one for your task management list. That's really focused. You have a global one for all your properties, et cetera, et cetera. So I think I have your flow. This has given me a lot of inspiration because I just forget a lot of things. There's a lot going on. OK, I'm going to show you like here's the real value. Like let's say I'm doing this task. This is too simple of a task. Let's do-- I'm working on launching a course, right? And if-- as I get onto this, like let's say I'm like right before this, I was like, half done updating the sales page. And then let's say I find a bug in my course platform. And I need to document this bug. I take all my notes literally while I'm doing the task. And it's all embedded. And again, it's all text. So if later, like tomorrow, I come back and be like, where in the world did I log that bug? Because I did it lazily in my notes. And I didn't actually create a bug. I can be like, Claude, help me find this thing that I don't know where it's at. And like, I don't know about you. I don't know if you've used Trello. But I think any task management tool-- I could say this about the search is not that good. And it's not that good at searching all the context in the task. And that's what I really love from this. Is that like, I can't figure it out. But Claude will try every permutation of searches till it finds it. Even if I'm remembering the words wrong, I'll be like, hey, I have a thing called new blog post tomorrow. And it'll be like, I can't find anything called new blog post tomorrow. But I have this thing that says, article Wednesday. Is that what you're looking for? And I'll be like, whoa, Claude, that is what I'm looking for. Yeah, I don't think we say it enough that these are really great local search engines for. We use it so much in code all the time. I'm like, hey, can you remind me how XYZ worked? Or I think I shipped this feature. Can you remind me exactly how it was implemented or who did it? But you can apply that same framework, that same search framework to any text-based tool. These tools are really good at grabbing that context. Well, speaking of finding useful context, you have a second workflow around research. I would love for you to walk us through. So how do you assemble all this research that helps you do your job? OK, so I aspire to be a academic which is weird, but I do. And I really want to keep up on academic research on a lot of topics. In fact, we can go over here and look at my topics. So I do a lot about I'm really interested in this research around like synthetic users. And should we be letting AI do interview synthesis for us? I'm interested in team collaboration, creativity, discovery skills, whatever. A lot of education, because I teach, personas, because it's a super hot topic. And I really want to know, what are we learning from academic research? I happened to have access to a university library, which is great, but I never have the discipline to go search for things. There's never a moment in my day where I'm like, oh, I'm bored. I should go do this. But I wish that I did, right? And so what I did-- and this is also one of the nice things about using Claude as my test manager is I can integrate it right into my test manager. So I'm going to start by showing you the output of this, and then I'll talk about how I built it. So every day on my to-do list, I get a little research I just-- it's giving me the search results from a daily archive search. So archive is a preprint server. It's where most papers now, thanks to COVID and post-COVID, get published before they're published for real. What's nice is they're free, and they're fast. They're real-time. What's not nice is it's before they're edited, edited. So you have to be your own filter. It does a search, and then I get a markdown file with all the results. So this is like-- this is literally today's file. I have not gone through it yet. But then when I go through it, if I open a PDF, and I download it, I save it to these topic folders. And in each of these topic folders, there's a source directory and a notes directory. So my PDF goes in sources, and this is going to matter in a second. And then what happens the next day after I've saved a PDF is on this research today, Digest. I get summaries of every paper I save the day before. And I get really detailed summaries of not kind of the half-bagged, here's a paragraph of what the paper is about. But I wrote this skill to focus on the methods of the paper and the effect size. Things that are going to-- because I have to be the editor, there's no editor for these papers yet. Things that can help me decide, is this worth reading? Does it look like it had a big enough effect size? Did it look like it was a good study? And I have a funny story about this. The day I built this, I was reviewing my daily digest. And I saw this paper on purchase intent. And I read this, and I had it summarized, and I read this summary. And because it was like in this nice, contemporary format, I realized this flaw. I was like, oh, they use this purchase intent survey. That's not very reliable. Like, it's not an accurate measure of purchase intent. And the next day on LinkedIn, I saw Ethan Mullack shared the paper. And I was like, oh, this is kind of a crummy paper, Ethan. And I reshared it. And I basically said, here's why we don't have to care about this paper. And I outlined like a very critical review of the study. And the only reason why I could do that is because I had this system. And I'd already looked at the paper that had just come out. I had already analyzed it and critiqued it. And is there something we can learn from this? And then I wrote a really detailed LinkedIn post about it. And it's honestly one of my most best-performing posts on LinkedIn ever. Well, there you go. And what I have to ask is, how does this get triggered? Is this automatically-- is this triggered off that today command? How does that work? So I did integrate it into my today command. But the way it works, I built this as a plugin. It is available as a public repo. I will say it's still being tested. It has one user. My husband is going to be the second user. And if you want to be the third user, we can make it available. It is a public repo, but use it your own caution and still in development. What's funny about this is the only part of this that really requires AI is the paper summaries. But the part-- I would not have been able to build this without AI. So I basically just explained the clause. Here's what I want. I want to run a daily search. I want to digest on my to-do list. How are we going to make this happen? And what's happening under the hood is I have two Python scripts. One of them, every morning, searches archive. And then every Sunday, it searches Google Scholar. And it's keeping track of what papers we've already seen, what papers are new. And it's searching based on a config file of my personally defined keywords. And then every night, I have a second script. And these are crime jobs. I just run on my computer like on a schedule. And then at night, that second script is looking through my source directories in my research directory for any new PDFs. And it's creating a to-do list for my today command to take all the papers in that list, trigger Cloud Code Agents to generate the summaries. And then the summaries get added to this research today file. And do you still have to download those PDFs manually? I am downloading this PDFs manually. And I could. There is enough information in the search results that I probably could download them automatically. Even my hands selecting what papers I want to summarize, it's already a fire hose. So I want a filter. If we look at my digest, I don't need to read all of these papers. There's some of them that are going to pop out. That's really relevant to what I do. I'm going to grab that PDF. Just spend five to 10 minutes a day just looking at this and downloading papers. And then I forget about it. And then the very next day, I get those summaries. That's awesome. And are there any other-- you've spoken about archives and these academic sources. Have you thought about creating this for other sources of market information that are maybe useful? Yeah, so I wrote a blog post. I wrote a blog post called Cloud Code. What is it? How it's different and why non-technical people should use it. And in that blog post, I gave this scenario. I was trying to go from total beginner to magical moment. And so the magical moment I created was in that one blog post you learn about. The terminal you learn about Cloud Code. And by the end, Cloud Code has generated a very detailed competitive analysis for whatever competitors you tell it, with a detailed price comparison table, a detailed feature comparison table. Because I think this is the type of stuff Cloud is really good at. It can go query things. It can aggregate things. It can create reports. And so I've been starting to think about what I would love is this same research report for LinkedIn posts that are relevant to-- because I want to go be part of the conversation and comment on things. But when I log in, LinkedIn, I kind of want to stem my eyes out. So I need a filter, right? LinkedIn's API makes that really hard. I know I was going to say this is a call for a LinkedIn MCP here. So we can just access LinkedIn through the dark mode terminal. We'll have to figure out how to push their ads through MCP before they do that. But I do think there are a lot of applications for this that people that are interested in the academic research side. I mean, Cloud, I'm using Cloud to Google for me. I don't really go to Google anymore. This episode is brought to you by Graphite, the AI-powered code review platform, helping engineering teams ship higher quality software faster. As developers adopt AI tools, code generation is accelerating. But code review hasn't caught up. PRs are getting larger, noisier, and teams are spending more time blocked on review than building. Graphite fixes this. Graphite brings all your code review essentials into one streamlined workflow. Stackdiffs, a cleaner, more intuitive PR page, AI-powered reviews, and an automated merge queue. All designed to help you move through review cycles faster. Thousands of developers rely on Graphite to move through review faster. So you can focus on building, not waiting. Check it out at graphitedev.link/howiai to get started. That's graphitedev.link/howiai. You've shown two things, which is your to-do list is so overwhelming. You need a way to filter and aggregate and work through it. And then your sort of inbound knowledge sources are so overwhelming. You need to figure out a way to filter, summarize, and operationalize this. I really like this. But then I'm guessing at the end of the day, you have a bunch of tasks you've done, and you haven't done, and a bunch of research that you've read, or you haven't read. And you, I mean, like all obsidian users, or like all extreme note takers, which I expect you to be, just have a lot of information to go through. And so how have you thought about organizing, using that local context, that memory, to make something like Cloud Code do a good job on your behalf? Yeah, so I definitely have overdue tasks. That's why I went back to my to-do list here. And actually, this looks like a really nice clean view. If we went to my ideas folder, there's just too much to do, right? And so one of the things that I've been really playing with is I have this mantra in my head of automation or augmentation. So when I have a new task come up, can Cloud just do this for me, or should Cloud be helping me do this? And I love this because it's helped me be really reflective about like, what do I want to keep doing, what do I want the robot to do for me, right? I mean, not literally a robot, but you get the idea. And I realize the more context I provide to Cloud, the more Cloud can do for me. And so I have an obsidian vault that is literally GST for Cloud. And I call it LOM context, because sometimes I switch to Codex. It doesn't matter which model you're using. And I just have, like, a ton of information to find. This is going to look overwhelming. I did not create this all at once. I did it very iteratively over time. The way that I built it is as I was finding myself discouriding things to Cloud. I'd be like, OK, Cloud, what did we learn today that should go in a context file? And Cloud has written these context files for me. So the first one I did was a writing style guide. So I just sort of told Cloud. I said, hey, I actually didn't tell Cloud who I was. To start this, I just said, go to product talk and tell me what you think the author's writing style is. Who's the audience? What's the philosophy? Like, what's the tone? And Cloud actually went to my blog and read it and started writing stuff. And then I looked at it and I was like, yeah, this is kind of right. It's not really right. Let's fix this. And so we co-created a writing style guide. This is super long. I did not write this myself at all. Like, Cloud did all of the heavy lifting. But there's so much in here. There's a section on how my book writing is versus my blog writing. We have a section on headlines. We have a section on sub headers. We have a section on like key phrases I like to use. Never do this. Always do that. And what it means, I don't want-- I rarely let Cloud wait for me. But Cloud critiques all of my writing. And by having a really detailed writing style guide like this, Cloud's critiques are spot on, right? Because it knows my goals. It knows my audience. It knows who I'm trying to write for. It knows how I'm trying to write. And then I do the same thing for-- I have a business profile, a personal profile. I have a ton of business context. For marketing, I have like who my audience is. Brand guidelines, my marketing channels. I don't know what that content architecture one is. That's probably something Cloud created. Content, assets. Like just there's a ton here, right? The metrics I track, my publication schedule. I probably should not open partnerships. All of my products, right, like all my individual courses, my subscription products, whatever. And then each of these files just has content about that. And here's what I learned doing this. At first, I started putting everything in my Cloud MD. Like literally everything went in my Cloud MD. But then I realized, like, Cloud loads my Cloud MD every single time. I don't want all this context in there, right? And you'll notice, like, I have a business folder, but I also have a personal folder. I have a business profile and a personal profile. One of the most common things I use LLM's for are like, holy crap, my dog just ate this is she's safe. Cloud does not need to know what my marketing channels are or my blog post archive when it's telling me my dog's not going to die, right? And so it got me thinking about, like, to do context well, it's not just that we have to document everything. We have to document everything in teeny tiny files. So when we ask Cloud to do a task, we can give Cloud just the context it needs to do that task well. And then I don't ever tell Cloud when to use these files. Like if we look at my business profile, this is just a index. It's telling Cloud, this is what's available to you. You can find my company overview here. You can find details about these courses here. Here's some other products I have. So that whenever I ask Cloud to do something, it says in my global Cloud MD, if I ask you for help with something related to my business, use my business profile. If I ask you for help with something personal, use my personal profile. So then based on what I ask Cloud, it will load these profiles. And then based on the content of what I asked it, it'll pick which of these context files to add to the conversation. And then that makes sure I can be super lazy in my prompts. I can be like, Cloud, blog post, review. Give me feedback, right? And it'll just look at the topic of a blog post and like pull my audience file and look at who, what the product I'm referring to is. And it just helps. Yeah, I think this index file strategy is something that we hear a lot from how I guess, which is you want any individual context space or information to be relatively short and relatively focused, but you want to give the LLMS a map to those places. And so I almost think of this as like if you had a filing cabinet and you had to take a random person, an intern off the street and you said, here's my task. If you go in this filing cabinet, you'll be able to figure out how to do it. How do you structure, what do you take? What's the instructions you take on top of the filing cabinet that says this is how this filing cabinet works? But then how easy can you make it to discover exactly what context, what task in the step-by-step workflow you want somebody to follow is really the mental model you want to set up when working with something like a cloud code on a wide variety of tasks. And then you can be very lazy. You can be like, go write me a blog post on XYZ. And it can discover pretty naturally how to get there. - I think this is one piece I would add to that, which is, I think it's really easy to think about like, we got to give the LLMS a lot of context, but I think there's a corollary to that, which is if we give it too much irrelevant context, it's still going to not be very good at its job. And so like it was a big leap for me to realize this needs to be a lot of small files. Like I don't want one file with all my products because if we're working on one product, it doesn't need to know about the other products. - And I mean, I think that is the difference between like throwing a 2000 page user manual on someone's desk and saying somewhere in here is the answer versus an organized set of kind of like files and folders with little labels like how to write a blog post or what our products are. And so I do think just the form factor of how you store your context allows you to be, as you said, what we all want to be, a little lazy when-- - Totally. - And I'm lazy even in how I create these, like at the way that I create context files, is it any time I'm finishing a session with Cloud Code, I just go Cloud. Would you learn today that we should document? And I make Cloud do it. - Yep, I love it. - Well, I have to ask you one last thing because you are such an exceptional writer and put out excellent content. But I know you use a little Cloud to do a little of that. And I'm just curious how you get Cloud to be an effective writing buddy. Maybe it's exactly what you said, which is it's a reviewer. It enforces your style guide. But have you found, this is like the million dollar question for everybody. You found a way to make AI writing less terrible. - Yes and no. Okay, I love to write. So I really like, this is when I ask that question about augmenting versus automating, I don't want to automate writing. I will share, I have written two blog posts where an LLM did the bulk of the writing. I've been very transparent about this. The first one is I interviewed 11 people about how they're using loveable. And I had chat GPT turn those transcripts into individual stories that I shared. So like I didn't write those individual stories. I wrote the intro, I wrote the conclusion. I made sure they sounded normal. And then my blog post is coming out tomorrow, actually it is themes that are coming out from my podcast just now possible. And I had Claude do a lot of the writing on that. That was a little bit more heavy lifting. But for the most part, I still do all my writing and what I rely on Claude for is while I'm writing, usually in Obsidian with Claude, open a terminal right next to me. I'll be like, I'll realize I wrote something and wonder if it's true. And be like, Claude, I think this, is there any evidence that this is true? And Claude will go off in research and I'll go back to writing. Or I'll write my intro. And I'll be like, Claude, I wrote my intro. Can you tell me how to make the hook stronger? And it will like read my intro and tell me what it likes and doesn't like? Or I'll write a section and I'll be like, okay, Claude, review the section. What's good, what's not good? And then Claude's not just giving me generic feedback, right? Because I've written this style guide. It knows how I aspire to write. So then when it tells me what's good and what's not working, it's doing it based on my own goals that I've told it. Like here's how I want you to critique my writing. And then my favorite is it just fixes my typo as I go. So then I can type really lazily and not care that I'm spelling everything wrong. - Yes, I have indulged in fancy nails lately. Other people who have watched this podcast have seen me type terribly with my fancy nails. And it has allowed me to enjoy fancy nails without having to fix my typos, which are very abundant. These days, so I think that's great. Okay, so to recap all of your workflows, which I think is great, we went really deep on your to-do list. I kind of agree, everybody just has this particular way. They want to manage themselves and they want to manage their list is the perfect use case for building something yourself. So if anybody out there is looking for a personal project, highly recommend getting started with a customized to-do list, maybe here in Claude code, like you've done it. You showed us how you can do a daily automation and summarization of information that you find useful, which allows you to engage in broader market conversations that you wouldn't have the time or capacity to do in an in-depth way. And that's driving, I'm sure, great things for your business as well as just making you a more informed leader and voice in the market. We've gotten really organized around your local context and memory system. You clearly love a structured file and a structured folder, so I have to acknowledge that. That's amazing. And then while you rarely write LLM first, you found that Claude code in particular, Claude is a really good writing buddy to keep you sort of like on the rails, do you research for you, get you feedback, like make incremental fixes and fix typos in grammatical errors? So just that. Do you? No, I'm going to go to lightning round questions because I do have to ask you a few other things. Clearly, love Claude. But what else do you say anything else? What are some other daily drivers for you? Are you always in dark mode terminal? I am often in dark mode terminal. I do use VS code, so when I'm writing code, I do still prefer to be in IDE and have colorful diffs. As far as other AI products, it's funny. Everybody asks me, like, what about cursor? I actually have never used it. I know it's amazing. I try, like, the way that I deal with the overwhelm of just the firehose of information is I try to only seek out a new product when there's something wrong with what I'm using. So like, I uncover a gap. I'll be like, OK, now I gotta go find to fill this gap. And a lot of this setup of like Claude code with obsidian or Claude code in VS code just works really well for me that I haven't tried a lot of other stuff. I would say the only other big AI product I'm using on a regular basis, I still occasionally use chatGPT in the browser, usually, because I'll be doing something else in the browser. And it's just easy to pop over to chatGPT. Or I use Descript for video editing. And it is one of the-- I can't think of very many non-foundation lab AI products that I love, but I love Descript. Yeah, we use it to edit the podcast. And what a delightful change in user experience from what you used to have to do to what you can do today. Video by editing a text transcript is just the most magical thing that exists. Yes. And if you missed it, the founder of Descript did a early how-i-i podcast talking nothing about their AI product, but did talk about how he opened a, which I think is open now, a East Bay. I think it's an Oakland or Berkeley board game business using, basically, chatGPT as a co-founder. So don't listen to that one. I listened to that episode. I don't think I realized it was from the Descript guy. It was. And I got the funniest text from a friend who said, this is the most Bay area thing ever. Two guys that don't think that they can arrange a board game without putting AI in the middle. OK, so my second question for you. We've already asked for the LinkedIn API MCP. We're fine being advertised too. So any LinkedIn PMs out there, we are fine getting inline advertisements as long as we don't have to log in. So we can read our content in the terminal. What else do you wish was out there to power your tool? Maybe it's not an AI tool, but maybe it's a data source. You know, LinkedIn is pretty high on the list. Like I just-- I hate AI-generated content. I think this is why I still do my own writing, because reading other people's AI-generated contents comments kind of breaks my soul a little bit. So I think LinkedIn is probably the big one. Although there's probably 100 times a day where I'm like, why can't I just do this thing? But I don't know. I get pretty far with Cloud. Cloud can teach me how to do anything, which I really like. LinkedIn, these are two people who want to reach a business audience, because I've solidly told everybody, if you want to run a business like I run, I'm sure if you want to run a business like you run, you got to live on LinkedIn. It's just a reality. There's a second one. And I know this is getting better, but it's still not good. I really want text to image where it can close the quotation mark on the quote in the image. That's the only one I really want. OK. OK, we'll make this ask out there. Anybody working on those products, please. We will be beta testers for you. OK. And then last and final question. And we will get you out of here. When AI, when your buddy Claude is just not listening, not doing what you want. Writing terrible slop. What is your prompting technique? Are you all caps? Do you just quit? Complete kill Claude. What do you do? I kind of kill Claude. I use clear excessively. And I think that's what got me on this context file thing. Is that like, I don't really want to rely on the conversation history, because when Claude gets stuck, I want Claude to go away, and I want a clean slate, and I want to start over. But I don't want to have to re-explain all my context to Claude. So I've built a lot of tips and tricks to constantly be keeping documentation about what we're doing while we're doing it. So that when Claude doesn't listen, I can just be like, slash clear, we're starting over. I wish I could do that in my human conversation. We have all the information we need. It is not getting us to an agreement. Let's just slash clear, start. We've round and round, stop. Let's do it over. All right. Well, Theresa, this has been great. Where can we find you? And how can we be helpful to you? Yeah, so I blog at producttalk.org. Lately, I have been blogging a ton about Claude code. So if you found this stuff interesting, there's going to be much more coming. And then I recently started a podcast called JustNowPossible. And it's more about, I interview cross-functional product teams about how they're putting AI into production, which is super fun. And so you can check that out as well at JustNowPossible.com. Yeah, smash that subscribe button, check it out. Sounds awesome. Well, thank you so much for joining how I AI. Let's get you back to pair everything with Claude code. Yeah, it's the best. Thanks so much for watching. If you enjoyed this show, please like and subscribe here on YouTube, or even better, leave us a comment with your thoughts. You can also find this podcast on Apple Podcasts, Spotify, or your favorite podcast app. Please consider leaving us a rating and review, which will help others find the show. You can see all our episodes and learn more about the show at howiipod.com. See you next time.