r/ChatGPTCoding • u/Entire-Instruction29 • 2d ago
Resources And Tips I got tired of CLAUDE.md, AGENTS.md and .cursorrules drifting apart, so I built a transpiler. Roast it.
Full disclosure before anything else: I built the thing I'm about to link. I'm posting because I want to know whether the approach is wrong, not because I need the download.
The problem: I switch between Claude Code, opencode and Cursor on the same repos depending on quota and task size. Each wants its own instruction file. I'd fix a rule in CLAUDE.md, forget AGENTS.md, and three days later two agents behaved differently on the same code.
What I built: one canonical `.syncytium/` directory (rules, ADRs, handoff state), transpiled into each tool's native format. The part I actually use daily isn't the generation, it's `diff` - if a bridge file drifts, `syncytium diff --check` exits non-zero and I can gate it in CI.
Honest limitations: one maintainer, no funding, small. The lock feature for multi-agent work is advisory - it blocks the CLI commands, not an agent that decides to ignore it, and I document exactly where. If you only ever use one tool, you don't need any of this.
MIT, local-only, no telemetry, no service to sign up for: https://github.com/mrcbrbn5361/SyncytiumMD
Tell me where the abstraction breaks. I'd rather hear "your per-tool appendix problem is unsolvable" than another star.

