I’ve been using Claude Code now inside Cursor in order to save money since Cursor chats are getting kinda pricey and my job pays for Claude Code. It’s nice to run /init in a repo and see Claude spin up a nifty summary of a project:
Project Overview
This is an automated Quartz v4 blog with sophisticated media optimization, AI-powered auto-tagging, and cloud sync capabilities. The project focuses on Unity, VFX, gamedev, and programming content with a highly automated publishing workflow.
Seems legit. Now, time to get to work.
Started off by fixing the issue in my deployment workflow causing images with no caption to be given “$1” as a caption. Now, I can confidently say that image captioning works properly. Does video captioning work? I’ll test that another time. One thing I did notice, however, were some unused scripts and outdated README files that got created a while ago and never got updated. Hopefully, with my CLAUDE.md now in place, outdated READMEs become a thing of the past.
Next was tackling the media-optimization-related bug of finding all .webp and .webm files that weren’t actually .webp and .webm files and properly converting them. I used ChatGPT to design a Python script that identified and renamed those phony files. To my surprise (and relief), there weren’t many. So few, actually (11), that I went ahead and did the markdown reference updating and cloud file deletion manually.
Now, that the known Quartz bugs are taken care of, I should probably go ahead and finally work on making that Instagram post to demo the metaballs, a task which has resided in the “Do ASAP” section of Tasks forever. I find it funny, but not surprising, how sidetracked I get by little optimizations and bug fixes—I genuinely enjoy code cleanup and organization. Maybe I should have been a janitor.
Tags: debugging deployment file-management optimization claude