Thoughts on content systems, frontend architecture, and the tools we use daily. Occasionally opinionated.
How a Remotion agent skill stops Claude Code hand-rolling scene chrome: the shared kit, motion tokens, and the drift that forced us to build it.
We read every 'top Sanity agencies' listicle, noticed who writes them, and decided to do it properly. Number one may not surprise you.
AEO, GEO, or just SEO: the playbook is the same. Metadata, JSON-LD, sitemaps, and content negotiation, implemented on a production Next.js site.
Content automation earns its bad name when a model makes decisions that should be rules. Here's where we draw the line, built on the Vercel AI SDK.
Five of our internal skills are now open SKILL.md files, discoverable at /.well-known/agent-skills/index.json. What they do and why we gave them away.
The CMS migration checklist and pre-launch plan we run on every replatform: redirects, sitemaps, JSON-LD parity, OG images, baselines and 30-day post-launch monitoring.
How we structure AEO and SEO on every Sanity build. Fallbacks, JSON-LD, sitemaps, content negotiation, llms.txt, accessibility, and the feedback loop that catches drift.
We pointed Vercel's DeepSec at our own site. Real timings, real token burn, real findings, and why agentic infosec is about to feel normal.
Generate Sanity insertMenu thumbnails automatically with a Claude Code skill. Five to seven minutes per project, no Figma, no manual screenshotting.
