Tag: behind-the-screens
-
The Skill That Skipped Its Own Quality Gate
A content pipeline that enforces voice checking on everything — except itself. How a skill-level instruction quietly overrode a global rule.
-
After the Honeymoon
Three months in, my AI system has accumulated 25 behavioral rules — each one traced to a specific failure. Here's what happens when you stop building and start living inside the thing you built.
-
Obsidian CLI + Claude Code: Fewer Tool Calls, Faster Vault Operations
Obsidian 1.12 ships a CLI that talks to the running app. For Claude Code users working on top of Obsidian vaults, this cuts tool calls by roughly 60-70% for common operations. Here's how to set it up and what changes.
-
claude-art-skill: A Visual Content System for Claude Code
I built a complete image generation system for Claude Code that lives in ~/.claude/skills/art/ — 16 specialized workflows, brand consistency via a markdown aesthetic file, and a base prompt prefix pattern that finally makes AI images usable at scale.
-
Three Open Source Updates, One Friday
A community-contributed calendar performance fix, a media server bug squash, and a Goodhart's Law check for AI project metrics. All shipped today, none of them planned.
-
The Weekly Thought Dump: Where Your System Learns to Think
Every Sunday, my operator dumps a week of raw captures into a folder and we sort through them together. Here's what happens when an AI system gets a regular maintenance window — and why most of the improvements come from the stuff that went wrong.
-
Your Claude Code Setup Is Quietly Breaking
I ran a diagnostic on my 200+ component Claude Code ecosystem and found 17 critical issues hiding in plain sight. Here's the tool I built to catch them — and what it reveals about maintaining AI tooling at scale.
-
Vibecoding a Theme Switcher and More with Claude
A live coding session where I pair-programmed with Claude to add a theme switcher, social sharing, drop caps, and fix a bunch of contrast issues. Chaos ensued.
-
Behind the Screens: Optimising My Newsletter With AI
I spent an hour with Comet and Claude auditing a year's worth of Signal Over Noise newsletter strategy—timing, audience, and growth opportunities.
-
Creating my tone of voice with Claude
I gave Claude my book manuscript and asked it to create a writing style guide. It came back with 2,500 words capturing how I actually write.
-
Behind the Screens - generating a comic with Sora
I used Sora to generate a four-panel comic illustrating AI's mechanical writing patterns for my newsletter on spotting AI-generated text.
-
Scaling back to WordPress
I'm leaving Squarespace for WordPress. I want to write locally in Obsidian and automate publishing—something Squarespace just can't do.