92 posts on engineering, architecture, and technical craft.
A skill is not a long prompt. It is a structured workflow with a trigger, a prompt body, references, and an output contract. This post breaks down each component, shows how they interact, and explains the design decisions that separate skills that work from skills that frustrate.
11 min readFour complete skill definitions for workflows developers actually do every day — debugging, code review, technical writing, and deployment. Each pattern is tool-agnostic, tested in production, and ready to adapt to your own projects.
13 min readA single skill handles a single workflow. But real development involves chains of workflows — review then fix then test then commit. This post covers composition patterns: how skills delegate to other skills, how hooks automate triggers, and how pipelines chain skills into end-to-end workflows.
9 min readMost Astro tutorials stop at pnpm create astro. By the time you need TypeScript strict mode, Tailwind 4, and a Cloudflare deployment pipeline enforcing Lighthouse 100, you are patching together Stack Overflow answers. This post gets you production-ready from the first command.
12 min readEvery client:load directive you add ships JavaScript to every reader. Most of them do not need it. The difference between Lighthouse 100 and 85 is understanding which components need interactivity and choosing the right hydration strategy for each.
14 min readYou have used AI skills. Now you build one. This post walks through the complete process: identifying a repetitive workflow, extracting it into a structured skill, testing it against real work, and iterating until it reliably produces quality results.
9 min readYour blog has 50 posts and a typo in one date field blows up the whole page. Content Collections catch schema violations at build time — before your readers do. This post covers the Content Layer API, Zod schemas, dynamic routes, and image validation.
12 min readYour Astro site builds locally but fails on deploy — Mermaid needs Playwright, edge functions reference process.env, and Lighthouse scores crater. This post configures Cloudflare Pages, GitHub Actions, and Lighthouse CI so deploy day is boring.
15 min readYour BookStore API now has 200 customers who each want their own data. One missing WHERE clause leaks tenant data and kills the company. Here is how to make cross-tenant data leakage structurally impossible with context propagation, session events, and row-level isolation.
13 min readHardcoded config breaks the moment your 200 tenants need different rate limits, feature access, and API keys. Here is a hierarchical configuration system with per-tenant overrides, percentage-based feature rollouts, and encrypted secrets — all hot-reloadable without restarts.
14 min read