All Talks

agnostic-ai

One spec, every AI CLI

Your team uses Claude Code, a colleague prefers Codex, and someone still has Copilot open. Each tool wants its own files, so the same conventions, skills and hooks end up copied in several places, and the copies drift apart without a single error. The tools are not the interesting part here. The workflow is.

We start with what we want from an agent and which part of its setup delivers each outcome: instructions and rules as hints, hooks and permissions as guarantees, skills, agents and MCP servers to get work done. Then we follow that setup through a few tool switches, see where it drifts, and compare two fixes: symlinks, and agnostic-ai, which keeps one spec and writes the native files 25 AI coding tools read. We close with the trade-offs and with questions for the room about what belongs in a shared agent setup.

Appearances


Keyboard Shortcuts

Movement vim hjkl

hPrevious post← left
jScroll down↓ down
kScroll up↑ up
lNext post→ right
ggScroll to top
GScroll to bottom
nNext sectionnext heading
NPrevious sectionprevious heading

Go to g = go

ghHomego home
gbBloggo blog
grReadingsgo readings
gcCVgo cv

Actions

/⌘KSearchvim search
dToggle themedark mode
tToggle TOCtable of contents
iSwitch languagei18n
mToggle highlightmark text

General

?Show this help
EscClose
:Terminalvim command mode
↑↑↓↓←→←→BA???