TLDR: I’m a software developer, but I don’t want to spend my personal time writing boilerplate for throwaway scripts. Claude Code lets me describe what I need, get a working tool in minutes, and move on. Here’s how I actually use it and a real example from my own workflow.
The Problem With Small Scripts
I write software for a living. You’d think that means I’m constantly automating things in my personal life. In reality, I’m not. Because the bar to writing a small personal tool is weirdly high.
It’s not that the code is hard. It’s that every small script still requires me to set up the project, figure out the right libraries, write the boilerplate, test it, fix the edge cases I didn’t think of. By the time I’ve done all of that for something that saves me ten minutes a week, I’ve spent three hours building it. The math never works out.
So I just didn’t. I’d do the repetitive thing manually, tell myself I’d automate it eventually, and then never do.
Claude Code changed that math.
The Tools
Claude Code: An agentic coding tool from Anthropic that runs in your terminal. You describe what you want to build, and it writes the code, runs it, fixes errors, and iterates until it works. It’s not a code autocomplete. It’s closer to a junior dev that does exactly what you tell it without complaining about scope creep.
Your terminal: That’s it. Claude Code runs locally. No new IDE, no cloud setup, no dashboard to learn. If you’re already comfortable in a terminal, you’re already set up.
The Workflow
The whole approach is built around one rule: describe the output you want, not the implementation. Claude Code handles the how. Your job is to be specific about the what.
Step 1: Identify the friction. What’s the thing you keep doing manually that takes longer than it should? It doesn’t have to be complicated. The best candidates are repetitive tasks with a predictable input and output. File renaming, data formatting, report generation, anything where you do the same steps in the same order every time.
Step 2: Write a plain English description. Open Claude Code and describe the tool you want like you’re explaining it to someone who knows how to code but doesn’t know your situation. Include the input, the expected output, any edge cases you already know about, and the language or format you want the result in. More detail up front means fewer back-and-forth rounds.
Step 3: Let it build and run. Claude Code will write the code, attempt to run it, catch errors, and fix them on its own. You don’t have to babysit it through every compile error. Watch what it’s doing, but let it work.
Step 4: Test it against a real case. Once it says it’s done, run it against actual data. Not a toy example. Real input from your real workflow. This is where edge cases you didn’t think to mention will surface, and that’s fine. Tell Claude Code what broke and it’ll fix it.
Step 5: Save it somewhere you’ll actually find it. This sounds obvious, but a tool you can’t find in three weeks is a tool you’ll rebuild from scratch. I keep a folder called /tools in my home directory. Every script Claude Code writes for me goes in there with a one-line comment at the top explaining what it does.
A Real Example: My Race Log Formatter
I keep a running log of every race I’ve done. Distance, finish time, location, notes. For years I tracked it in a messy spreadsheet with inconsistent formatting. Some rows had times in HH:MM:SS, some had them in MM:SS, some had the distance in miles, some in kilometers. It was a disaster to look at and a bigger disaster to query.
I described the problem to Claude Code: I have a CSV of race results with inconsistent time and distance formats, and I want a script that normalizes everything to miles and HH:MM:SS, calculates my pace per mile for each race, sorts by date, and outputs a clean CSV I can drop into Notion.
It wrote a Python script, ran it against a sample I provided, caught a parsing issue with one of the time formats, fixed it, and had a working script in about four minutes. I tested it against my full race log, two more edge cases came up (a DNF entry and a race where I’d logged a distance in kilometers with a “km” suffix), told Claude Code about both, and it handled them. Total time from describing the problem to having a working tool: maybe fifteen minutes.
I’ve now run that script every time I add a new race. It saves me five minutes of manual reformatting every single time, and my race log is actually clean enough to look at now.
Why This Works
The bottleneck for small personal tools was never knowing how to write the code. It was the activation energy required to start. Claude Code removes that. The cost of going from “I should automate this” to “I have a working script” dropped far enough that it’s now worth doing for problems that only save me a few minutes a week.
It also removes the ego problem. Writing a quick-and-dirty personal script when you’re a professional developer feels embarrassing. You start thinking about proper error handling and unit tests and whether you should make it configurable. Claude Code doesn’t care. It writes the ugly script that solves the problem. You can clean it up later if it actually becomes important enough to warrant it. Spoiler: it usually doesn’t.
Where It Falls Short
Claude Code is not great at requirements that live in your head. If you know what you want but can’t articulate it clearly, you’ll spend more time correcting it than you would have spent writing the script yourself. The quality of the output is directly proportional to the quality of the description you give it.
It’s also not the right tool for anything that touches production systems or sensitive data without you knowing exactly what the code is doing. I always read through what it writes before running it against anything that matters. It’s not that it writes bad code. It’s just good practice.
How to Start
Install Claude Code, then think of one thing you’ve been doing manually that has a clear input and a predictable output. Something small. A file you rename the same way every time, a report you reformat every week, a calculation you run in your head and then type out. Describe it to Claude Code in plain English and see what it builds. Don’t start with something important. Start with something annoying.
Try This First
Open Claude Code and type: “Write me a script that [the repetitive thing you keep doing manually].” Be specific about the input format and what you want the output to look like. Run it. If it breaks, tell it what broke. That’s the whole loop. Most small tools are three or four iterations from working.
Take what’s useful. Leave the rest.