Stop Using .md for AI Agent Instructions
Static site generators, formatters, and indexers treat .md files as content. Agent instruction files need dotfiles like .claude to avoid unwanted processing.
Static site generators, formatters, and indexers treat .md files as content. Agent instruction files need dotfiles like .claude to avoid unwanted processing.
Analysis of how AI models cite sources reveals a new discipline: mention engineering. This isn't SEO anymore—it's about crafting content that becomes ideal citation material for AI models.
My site serves identical content in HTML for humans and markdown for AI agents, with no hidden content, excellent crawlability, and smart content negotiation based on Accept headers.
AI agents lack foresight, overcomplicate simple problems, get stuck in loops, apply sledgehammer solutions, and misrepresent outcomes.
Developers hate marketing but crave trust. The path to enterprise adoption requires 10+ meaningful encounters through documentation, content, open source, and consistent signaling. Each touchpoint builds confidence; friction breaks it.
AI startups fail by optimizing for quarters instead of decades. Win by ignoring market noise, hiring missionaries during downturns, ruthlessly seeking truth, securing credibility early, selling FOMO, targeting unregulated markets, building for the pyramid, embracing acute pain, and becoming your own media.
We're transitioning from linear AI coding assistants to orchestrated agent systems. The future isn't about humans using AI tools--it's about humans orchestrating AI processes.
Used Claude Code to analyze Twitter's algorithm, build FollowSaver Chrome extension, and navigate Web Store submission. AI handled 95% of technical work—I provided direction and created assets. Approved in 24 hours. The barrier to shipping dropped from months to hours.
I've solved the idea-to-code friction by running autonomous AI agents in VMs. Every shower idea gets spec'd and implemented automatically using loop.sh orchestration, specialized subagents, and proper tooling.
Used AI to analyze its own git history, sparking thoughts on transparent AI-human collaboration. The future isn't hiding AI use—it's building verifiable trails of who did what, when, and how. Like Andy Weir's crowdsourced Martian, creative work has always been collaborative.
Request an AI summary of this blog