One Library, many agent folders: sync to Claude, Cursor, Copilot, and beyond
Half the team lives in Cursor. Someone else swears by Claude Code. A contractor dropped GitHub Copilot instructions into .github/ and nobody wants to touch them. Your Library lives in Veritos, but “sync to repo” used to mean picking one layout and hoping the rest of the stack could live with it.
That is a bad fit for how people actually work.
We shipped multi-format sync so you decide where files land—not just what goes in them. Choose the agent presets you need, point at a fully custom folder if your setup is non-standard, or enable multiple targets at once so the same Library items can flow to more than one layout in the same repo.
What you can target
Veritos includes presets for the layouts teams already use—pick one, several, or add your own:
- Claude Code →
.claude— Claude Code, Cursor (Claude compatibility mode), Augment - Cursor →
.cursor— rules, skills, agents - Codex / OpenAI →
.agents— Agent Skills standard (agentskills.io), Codex CLI - GitHub Copilot →
.github— instructions, prompts, skills, agents - OpenCode →
.opencode— skills, agents, commands, plugins - Windsurf →
.windsurf— rules, skills - Augment →
.augment— rules, agents - Cline →
.clinerules— rule files (VS Code extension) - Amazon Q →
.amazonq— Amazon Q Developer rules - Gemini →
.gemini— Gemini Code Assist
That list will grow as new agents settle on a folder. If yours is not on it yet, you are not stuck: specify a custom path and we still sync the same Library content into the structure your team expects.
Why “multiple at once” matters
Some repos genuinely run more than one assistant. You might keep Cursor rules in .cursor and still want Copilot instructions in .github for contributors on a different stack. You might be migrating from one tool to another and need both trees updated until the switch is done.
Selecting several presets (or presets plus a custom path) means one update in the Library can propagate everywhere it needs to go—still through the same review story you already use in GitHub.
What stays the same
Your skills and rules still live in Veritos first: versioned, permissioned, reviewable. Sync is still “open a PR, merge when ready.” The change is only which directories on disk get the export—not whether you trust the process.
Next step
Open a repository’s sync settings, pick the agent formats (or custom paths) you want, and wire Library items the way you already do. If your team’s tool mix changes, adjust the targets; the Library does not need a rewrite.
Built by Julian Pomper and Max Gierlachowski in Vienna.