<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Tech | blog.kittenin.space</title><link>https://blog.kittenin.space/tags/tech/</link><description>A blog mostly about fiber crafts but also sometimes about tech.</description><generator>Hugo</generator><language>en-US</language><atom:link href="https://blog.kittenin.space/tags/tech/index.xml" rel="self" type="application/rss+xml"/><item><title>Creating a Custom Obsidian Theme with AI</title><link>https://blog.kittenin.space/posts/creating-a-custom-obsidian-theme/</link><guid isPermaLink="true">https://blog.kittenin.space/posts/creating-a-custom-obsidian-theme/</guid><pubDate>Sat, 03 Oct 2026 15:07:53 -0400</pubDate><description>I missed having time to make custom themes for all my tools, so I decided to see what Claude could do.</description><content:encoded>&lt;p&gt;At some point in the past few years I have become painfully aware of the idea of time. Notably, that there is not enough of it in the day to do all the things I want to do, and possibly not enough of it in my life to craft the things I want to craft, write the books I want to write, and code the things I want to code, on top of doing the things one has to do to support the systems that make me as a human function; i.e., eat and workout and sleep.&lt;/p&gt;&#10;&lt;p&gt;Thus I have effectively stopped doing some things I used to love doing. Namely, making custom themes for every application I use that allows custom themes. Now, I &lt;em&gt;have&lt;/em&gt; gotten a taste of this in my own way &amp;ndash; &lt;a href="http://countrowsfromsheep.com/"&gt;Count Rows From Sheep&lt;/a&gt; has enough themes that I don&amp;rsquo;t remember the number off-hand (twenty-something?) and the ability to make custom themes. But this awareness of time also means that tools I use every day, like Obsidian and VS Code, languish in the realm of just having themes that are &amp;ldquo;good enough.&amp;rdquo;&lt;/p&gt;&#10;&lt;p&gt;The thing with themes, however, is that they generally are not that complex. An Obsidian theme is effectively a CSS file (and a manifest with metadata). Admittedly, it can be a &lt;em&gt;long&lt;/em&gt; CSS file, but it&amp;rsquo;s a CSS file all the same. Likewise, a VS Code theme is mostly just JSON. Again, a &lt;em&gt;lot&lt;/em&gt; of JSON, but just JSON. And while I was begrudgingly trying to make the beautiful Retroma Obsidian theme &lt;em&gt;just dark enough&lt;/em&gt; to please me (and failing), I had a bit of a realization:&lt;/p&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;Is this not what AI is good for? Templating things that keep to standard structures and follow basic rules?&lt;/p&gt;&#10;&lt;/blockquote&gt;&#10;&lt;p&gt;And so I went out to see if I could create a fully custom Obsidian theme in Claude in an afternoon while finishing up the last details of my &lt;a href="https://www.ravelry.com/projects/Acanthae/everest-shawl"&gt;Everest Shawl&lt;/a&gt;.&lt;/p&gt;&#10;&lt;p&gt;I began with what I, personally, would call &amp;ldquo;the fun part.&amp;rdquo; I came up with colors and rules. I knew I wanted a dark, witchy theme with little moon details and soft, rounded elements. I then picked some colors I liked and mapped them to places I thought they would work in the theme.&lt;/p&gt;&#10;&lt;p&gt;Next, I asked Claude (the chat) to write up a &lt;code&gt;CLAUDE.md&lt;/code&gt; file to give Claude (the code):&lt;/p&gt;&#10;&lt;pre tabindex="0"&gt;&lt;code&gt;I want to use Claude Code to create my own theme for Obsidian. I want it to be fairly minimal with round the UI elements, with the following dark, witchy colors:&#10;&#10;Background primary: #0D0A12&#10;Background secondary: #15101C&#10;Background elevated: #1D1628&#10;Borders/dividers: #2A2136&#10;&#10;Text normal: #E7E0EA&#10;Text muted: #B0A5B8&#10;Text faint: #8B8198&#10;&#10;Primary accent: #4E267B&#10;Accent hover: #69389D&#10;Links: #B596DA&#10;&#10;Success/botanical: #1D6A5C&#10;Info/cool accent: #285A8F&#10;Danger/dramatic: #7A2948&#10;Warm accent: #9A5B1A&#10;&#10;Rare moon accent: #CFC6D8&#10;Moonmetal detail: #B9B0C7&#10;&#10;The vibe should be:&#10;&#10;- moonlit crypt&#10;- witch’s study&#10;- gothic&#10;- botanical&#10;- quiet jewel tones&#10;- minimal&#10; &#10;Create a file I can provide to Claude Code to begin developing this theme.&#10;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Which it did, after attempting to tell me my color choices did not have enough contrast to be accessible &amp;ndash; which, fair, but I&amp;rsquo;m making this theme for &lt;em&gt;me&lt;/em&gt;, Claude, and my eyes can handle it. The resulting file, of course, was 300 lines of text, because Claude is a wordy boy who likes to talk to himself. Core to this was breaking up the design work into 8 phases, and having me verify and tweak theming elements at those points:&lt;/p&gt;&#10;&lt;pre tabindex="0"&gt;&lt;code&gt;1. **Setup** — repo layout, `manifest.json`, build/watch script, test vault, symlink instructions in README.&#10;2. **Tokens + variables** — palette block and full Obsidian variable mapping. Stop and let the owner review in Obsidian before continuing.&#10;3. **Shape** — radius scale, floating panes, tabs, ribbon, sidebar rows, buttons, inputs, modals, focus rings.&#10;4. **Markdown** — everything in section 5.&#10;5. **Enchantments** — moon divider, sidebar moon, title ornament, folder colors.&#10;6. **Style Settings** — settings block and wiring.&#10;7. **Plugin pass** — go through each plugin in section 8 using the test vault.&#10;8. **Polish** — mobile check, performance check, README with install and dev-loop instructions.&#10;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;(Claude, as you may notice, also felt very influenced by my instructions with &lt;em&gt;Enchantments&lt;/em&gt; being the title of phase 5.)&lt;/p&gt;&#10;&lt;p&gt;That said, this worked surprisingly well, and most sections only needed me to run manual checks and give the okay. The biggest issue I encountered was with section 5, where we had some problems getting the folder card shaping correct, something that was remedied by me digging into the CSS of existing themes I liked and providing some general guidance.&lt;/p&gt;&#10;&lt;p&gt;&lt;img src="cycle-of-the-moon-dark.png" alt="Cycle of the Moon - Dark version, my ideal Obsidian theme"&gt;&lt;/p&gt;&#10;&lt;p&gt;Overall, I ended up with my perfect Obsidian theme in only a couple of hours, much of which I spent crocheting while Claude worked the CSS. It even came up with some little details I wasn&amp;rsquo;t expecting. Look at those little moons in the checkboxs! So cute.&lt;/p&gt;&#10;&lt;p&gt;&lt;img src="deskcrafts.jpg" alt="Crafting at my desk, albeit not the Everest Shawl I was originally working on"&gt;&lt;/p&gt;&#10;&lt;p&gt;And, emboldened by this turn of events, I &lt;em&gt;kept going&lt;/em&gt; and ended up asking Claude (the code) to write itself another &lt;code&gt;CLAUDE.md&lt;/code&gt; file for a different instance of itself to make a VS Code theme, which took even less time and almost no intervention from me, since you can only change color elements of VS Code and not the UI shaping.&lt;/p&gt;&#10;&lt;p&gt;&lt;img src="cycle-of-the-moon-dark-vscode.png" alt="The VS Code version"&gt;&lt;/p&gt;&#10;&lt;p&gt;I won&amp;rsquo;t lie and say I don&amp;rsquo;t miss the long afternoons in high school and college perfecting the CSS I needed to get my Tumblr theme &lt;em&gt;just so&lt;/em&gt; or fighting Adobe Photoshop to mock up the perfect look for Winamp. But I&amp;rsquo;m also glad I don&amp;rsquo;t have to choose between being genuinely happy with the appearance of my everyday tools and feeling like I am actually being productive. Sometimes, you can have both.&lt;/p&gt;&#10;</content:encoded><category>coding</category><category>ai</category><category>tech</category></item><item><title>Lessons Learned by Counting Rows From Sheep</title><link>https://blog.kittenin.space/posts/lessons-learned-by-counting-rows-from-sheep/</link><guid isPermaLink="true">https://blog.kittenin.space/posts/lessons-learned-by-counting-rows-from-sheep/</guid><pubDate>Mon, 21 Sep 2026 17:52:36 -0400</pubDate><description>Whenever learning a new programming language, framework, backend, or tech skill, I have always relied on remaking the same applications: This lets me focus on learning, not product design. Initially, this was a simple to-do list application I called Forethought, although I also dabbled in pomodoro timers. But after a time, I wanted to try to make something important to me: a knitting/crochet row counter.</description><content:encoded>&lt;p&gt;Whenever learning a new programming language, framework, backend, or tech skill, I have always relied on remaking the same applications: This lets me focus on learning, not product design. Initially, this was a simple to-do list application I called &amp;ldquo;Forethought,&amp;rdquo; although I also dabbled in &lt;a href="https://cozytime.kittenin.space/"&gt;pomodoro timers&lt;/a&gt;. But after a time, I wanted to try to make something important to me: And as a knitter and crocheter perpetually unhappy with my row counting applications, I realized what I wanted out of a row counter was what I wanted out of, well, fiber arts in the first place &amp;ndash; a app customized to me.&lt;/p&gt;&#10;&lt;h2 id="gauge-swatch-the-first-version"&gt;Gauge Swatch: The First Version&lt;/h2&gt;&#10;&lt;p&gt;When I first built &lt;strong&gt;Count Rows From Sheep&lt;/strong&gt; &amp;ndash; a name that has persevered through every version &amp;ndash; it was with Node.js and Express, using MongoDB as a database to store row counter and project information. Truth be told, I did not get too far with it: I got the Express server set up, the database schema, an intended item structure, and part of a REST API coded.&lt;/p&gt;&#10;&lt;p&gt;But then I saw a new shiny: I had started experimenting with TypeScript and React, and decided to pivot. You might say the gauge swatch worked: It let me realize what I wanted out of the fabric of the application. It was just a little different than what I started with.&lt;/p&gt;&#10;&lt;h2 id="frogging-realizing-what-i-really-wanted-but-only-after-making-an-entire-app"&gt;Frogging: Realizing What I Really Wanted (But Only After Making an Entire App)&lt;/h2&gt;&#10;&lt;p&gt;I started from scratch with version 2. Like the unfinished first iteration, this version of &lt;strong&gt;Count Rows From Sheep&lt;/strong&gt; used something JavaScript-esque, with TypeScript, and created an Express RESTful API. I switched the database to Postgres with Prisma, allowing me to logically organize my database tables with schemas and handle project and row counter data without spending too much time on database management.&lt;/p&gt;&#10;&lt;p&gt;I also finally got to the front end, and I admit: I spent most of my time here. There&amp;rsquo;s something to be said about having written the API partially before. TypeScript and Express weren&amp;rsquo;t new to me, and Postgres/Prisma removed some of the weight of database schemas. This let me focus learning more React, building &lt;strong&gt;Count Rows From Sheep&lt;/strong&gt; as a single-page application.&lt;/p&gt;&#10;&lt;p&gt;&lt;img src="theme-8.png" alt="image"&gt;&lt;/p&gt;&#10;&lt;p&gt;This also let me realize the things I really wanted from both the UI and the application as a whole: Clean, easy-to-use counters that can be visually linked and configured to track repeats, and an affective pattern viewer that let me highlight charts, write annotations, and add text. I also wanted to be able to change themes and settings based on my mood &amp;ndash; I&amp;rsquo;m a native of the 90s and 00s Internet; I love some color.&lt;/p&gt;&#10;&lt;p&gt;&lt;img src="theme-2.png" alt="image"&gt;&lt;/p&gt;&#10;&lt;p&gt;Finally, with everything working how I (think) I wanted, I added authentication: This was a progressive web app, after all! If someone other than me wanted to use it, they would need their own account. This was the first time I had ever implemented auth to an app, and I leveraged &lt;code&gt;bcrypt&lt;/code&gt; and JSON Web Tokens. I also set up invite codes, since I didn&amp;rsquo;t exactly want to release the app to other users yet.&lt;/p&gt;&#10;&lt;p&gt;And that&amp;rsquo;s a good thing: Because when I started using it, I realized I kind of hated it.&lt;/p&gt;&#10;&lt;p&gt;When I decided to build a progressive web app, it was primarily because I was impressed by the PWA of others: &lt;a href="https://www.dabblewriter.com/"&gt;Dabble Writer&lt;/a&gt;, in particular, is an application I thought was &lt;em&gt;really cool&lt;/em&gt;. I wanted to do that! And so I did: But then while using it, I realized that a.) needing the Internet to use my row counter kind of sucked, and b.) I didn&amp;rsquo;t actually care about using the app on multiple devices. I also didn&amp;rsquo;t like the $40+/month bill I was paying Digital Ocean just to use it myself.&lt;/p&gt;&#10;&lt;h2 id="the-fo-count-rows-from-sheep"&gt;The FO: Count Rows From Sheep&lt;/h2&gt;&#10;&lt;p&gt;&lt;img src="crfs-light-horizontal.jpg" alt="image"&gt;&lt;/p&gt;&#10;&lt;p&gt;After a few months of using my PWA web app exclusively, I decided to start fresh again. I wanted to rip out the database in favor of storing project data as JSON files, have it work local-first (and local-only), and provide users the option to use it on their platform of choice (so long as it was a platform I already used and could test it on). This led me to Tauri, which meant I was rewriting the backend again: This time in Rust! I had never actually used Rust before, but the transition to JSON-based project files made this a lot less intimidating than it would have been: It was all CRUD functions! No databases to integrate with! And best of all: It was quick as hell to use. (Well, except for the brief foray into using Android SAF so the user could &lt;em&gt;see&lt;/em&gt; their project files in the tablet filesystem, but apparently that was a bad idea.)&lt;/p&gt;&#10;&lt;p&gt;With the backend simplified, this let me dive head-first into the frontend again: I kept up with using React, although since I knew I wanted more and more (and more and more) themes, I decided to try out Tailwind CSS. And while I won&amp;rsquo;t say Tailwind is the &lt;em&gt;only&lt;/em&gt; reason I was able to implement custom, user-supplied themes, it didn&amp;rsquo;t hurt, either.&lt;/p&gt;&#10;&lt;img class="content-image content-image--left" style="--content-image-width:40%;"&#10; src="https://blog.kittenin.space/posts/lessons-learned-by-counting-rows-from-sheep/crfs-bottom-counter_hu_67f5ee6064c31cec.webp" srcset="https://blog.kittenin.space/posts/lessons-learned-by-counting-rows-from-sheep/crfs-bottom-counter_hu_5420cc5a4361973e.webp 480w, https://blog.kittenin.space/posts/lessons-learned-by-counting-rows-from-sheep/crfs-bottom-counter_hu_67f5ee6064c31cec.webp 720w, https://blog.kittenin.space/posts/lessons-learned-by-counting-rows-from-sheep/crfs-bottom-counter_hu_7c25fe54f15ede7.webp 960w, https://blog.kittenin.space/posts/lessons-learned-by-counting-rows-from-sheep/crfs-bottom-counter.jpg 1320w" sizes="(max-width: 650px) 90vw, 45vw"&#10; width="720"&#10; height="1112"&#10; alt="CRFS bottom counters"&#10; loading="lazy"&#10; decoding="async"&gt;&#10;&lt;p&gt;Since this was the second time leveraging React for the frontend, I was also able to go in with a better idea of what I wanted and how to get there. For example, one simple quality-of-life feature I was adamant about was the ability to move my row counters to the bottom of the screen, where I can see them best on my tab&lt;/p&gt;&#10;&lt;p&gt;I also didn&amp;rsquo;t want to lose portability entirely: But instead of native syncing between devices, which would involve a server and cost money, I developed a simple export/import system. You can save a project &amp;ndash; or &lt;em&gt;all&lt;/em&gt; your projects &amp;ndash; exported as a &lt;code&gt;zip&lt;/code&gt;, then import that &lt;code&gt;zip&lt;/code&gt; onto a different decide with &lt;strong&gt;Count Rows From Sheep&lt;/strong&gt; on it; it doesn&amp;rsquo;t even have to be the same type of device! I work from Windows to Android and occasionally Linux as needed. And it means the application can always be free!&lt;/p&gt;&#10;&lt;hr&gt;&#10;&lt;p&gt;I have never finished an application before &amp;ndash; at least not one I wanted to share. But &lt;strong&gt;Count Rows From Sheep&lt;/strong&gt; became something more than a learning experience for me: It became a customized application suited to my knitting and crochet needs, like how my knitting and crochet projects are clothes and accessories made just for me and my loved ones. Of course, that doesn&amp;rsquo;t mean I don&amp;rsquo;t want to share, and you can currently download &lt;strong&gt;Count Rows From Sheep&lt;/strong&gt; from the &lt;a href="https://crfs.kittenin.space/"&gt;CRFS website&lt;/a&gt; for Windows and Linux. Android is still in closed testing, but &lt;a href="mailto:countrowsfromsheep@pm.me"&gt;drop me an email&lt;/a&gt; if you want an invite; bonus points if you can take 30 minutes to run through a test survey!&lt;/p&gt;&#10;</content:encoded><category>tech</category><category>coding</category><category>crfs</category><category>fiber arts</category></item></channel></rss>