Menu

Post image 1
Post image 2
1 / 2
0

I wrote the same AI instructions 6 times. Then I built a sync engine to stop.

DEV Community·Wu Kun·23 days ago
#zWYYCnEN
Reading 0:00
15s threshold

Every AI coding tool has its own skills format. I got tired of maintaining copies, so I built a tool that writes once and syncs everywhere. I use Claude Code for deep refactoring, Cursor for quick edits, and occasionally hop into Windsurf or Cline when trying something new. The problem? Every one of these tools has its own "skills" or "rules" system, and none of them talk to each other. Claude Code wants files in ~/.claude/skills/ . Cursor uses .cursorrules . Windsurf has workflows. Cline merges everything into .clinerules . Copilot has its own format too. So every time I refined a workflow — say, my iterative dev process — I had to manually reformat and copy it to 5 different places. Skip one, and that tool is out of sync. It's the kind of toil that compounds silently until you realize your Windsurf setup is 3 months behind. The fix: a sync engine I built a small tool that scans your machine for whatever AI coding tools are installed and pushes your skills to each one in the correct format. No config files.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More