Part 1 of a 2-part series. This post covers the whole tool and the "one source of truth" problem. Part 2 goes deep on the most novel piece — letting your npm packages ship agent skills. (dev.to shows the series navigation once Part 2 is published.) TL;DR Write project instructions once in AGENTS.md → agent-kit derives CLAUDE.md , .gemini/GEMINI.md , .github/copilot-instructions.md , and CONVENTIONS.md . No more drift. It mirrors skills from your installed packages and your project into every agent's directory ( .claude/skills/ , .cursor/skills/ , …). Keep nested skills/ folders Claude Code can't read natively — agent-kit flattens them into the layout it requires on sync. Start: npm i -D @mongez/agent-kit && npx agent-kit init The problem: every agent wants its own file AI coding tools are converging on how they work — but not on where they read project instructions. The result is fragmentation. One agent reads AGENTS.md . Another expects CLAUDE.md .…