Real engineering practice, packaged as skills your AI coding agent can install. Add one to Claude Code, Cursor, Codex, GitHub Copilot, or Gemini CLI, and it builds the way we do: the techniques we rely on, and the anti-patterns we avoid.
Create and maintain a consistent design system through component contracts, inventories, and verification, with separate workflows for evolving the system and building interfaces with it.
Read the blog post: AI makes design system guardrails mandatory; this framework delivers them
Keep a shared record of what a person actually wanted, one short list per day tagged with the PRs it produced, so a teammate can catch up on a burst of agent-assisted work without reading every pull request. Written by the agent at the end of a session, not by hand.
Read the blog post: Give up a little speed, get your team back
Profile Rails boot time with require-profiler: find the slowest requires and initializers, catch boot-time YAML parsing and HTTP calls, deep-dive into stubborn files with Stackprof, and turn the findings into fixes that speed up your Rails app startup.
Read the blog post: Get in, human: cut Rails boot time with require-profiler and this guide
Writes and audits Tailwind CSS with the five practices that keep a fast-to-write codebase maintainable: design tokens over magic values, short and consistently ordered class lists, semantically grouped tokens, and fixed variants for design-system components instead of arbitrary className props.
Read the blog post: 5 best practices for preventing chaos in Tailwind CSS
Release an npm package with no token left to steal: Trusted Publishing, provenance, and staged publishes from a single GitHub Actions workflow, plus click-by-click npmjs.com and GitHub settings with every URL resolved from your own package.json.
Read the blog post: The secure way to release an npm package in 2026
Make a site readable to ChatGPT, Claude, Perplexity, and the coding agents that fetch URLs: Markdown routes, Accept content negotiation, llms.txt, and crawler signals in robots.txt. Pushes back on the AI-SEO advice we tested and found useless.
Related blog posts: Making your site visible to LLMs: 6 techniques that work, 8 that don't, Which AI actually reads your site? Two months of LLM traffic, measured
Eleven skills that turn Storybook into an audit layer for vibe-coded React and Vite apps: tell real components from dead ones, map routes and flows, check design-system health, bridge Figma both ways, and write CSF3 stories for the states that matter.
Read the blog post: Storybook Workbench: audit vibe-coded UIs and find hidden bugs in hours
Publish a catalog of agent skills and make it discoverable to AI coding agents: the .well-known/agent-skills/index.json index, integrity digests, single-file vs multi-file vs bundle packaging, and every install method. Pushes back on pointing the index at raw GitHub URLs instead of a domain you control.
Read the blog post: Ship agent skills like packages: discovery index, digests, and install sources
Fixes what LLMs get wrong about Inertia.js on Rails, across React, Vue 3, and Svelte: controllers and prop types, forms without react-hook-form, pages and navigation, shared-prop typing, shadcn/ui, and Alba serializers with auto-generated types.
Related blog posts: Inertia.js in Rails: a new era of effortless integration, The joy of Inertia Rails: painting your own with 50 happy little lines and
Encode a video for the web with one ffmpeg script: AV1, HEVC, and H.264 MP4s plus a poster and the video tag with its sources in the right order, or VP9 and HEVC with alpha for a transparent video that plays in both Safari and Chrome.
Read the blog post: How to make web videos way smaller in 2025 using the AV1 codec
Write or rewrite an open source README the way PostCSS, Nano ID, imgproxy, and AnyCable did it: lead with what the project does and how it differs, drop the badges, and never invent a benchmark the repo can't back up.
Read the blog post: PostCSS creator shares how to make your open source popular
Write, refactor, and review Rails code by the principles from the Layered Design for Ruby on Rails Applications book: service, form, policy, and query objects, plus a codebase analysis that scores callbacks, finds god objects by churn and complexity, and flags layer violations in a diff.
Related blog posts: It deserved its own tome: Layered Design and the Extended Rails Way, Rails Hyperdrive: supercharged agentic development for Rails and
