Cross-tool AI rules & memory vault

10/29/2026 02:00DevToolsAIProductivityLocal-first

One set of rules, skills and memory reused across Claude Code, Codex, OpenCode and 20+ AI coding tools

Problem: Heavy AI-coding users rotate between Claude Code, Codex, OpenCode and Kimi Code, and each tool has its own rule files, skill folders and memory. A preference stated in one tool has to be repeated in the next, and project context keeps getting lost, slowing people down.
Solution: A local-first vault where users maintain a single Markdown rules file and skill directory. The tool adapts and distributes them into each AI editor's config format, and exposes vault_search and vault_remember as MCP tools so any MCP-capable agent can look up past preferences and project knowledge.
Users: Professional and indie developers who use two or more AI coding tools, and AI-native small teams
MVP: Auto-sync configs for 5-8 mainstream AI coding tools; single source-of-truth folder for rules and skills; two MCP tools for search and remember; one-command CLI setup and status; fully local, no cloud pass-through
Revenue: One-time purchase at $19-39 for individuals; per-seat annual subscription for teams; usage-based billing for a hosted MCP service
Why now: The number of AI coding tools is exploding and they overlap heavily, so users rarely stay loyal to one. Cross-tool consistency is a fresh gap that big vendors have little incentive to solve.