braid vs Shared Git Repo
Sharing rules via a git repository works but requires manual syncing, folder format conversion, and has no auto-invocation. Every developer has to pull, copy, and maintain tool-specific formats.
Feature comparison
| Feature | braid | Shared Git Repo |
|---|---|---|
| Automatic format conversion | ✓ | — |
| Multi-tool format conversion | ✓ | — |
| One-command install | ✓ | — |
| Prompt injection scanning | ✓ | — |
| Role-based permissions | ✓ | — |
| Version control | ✓ | ✓ |
| Free to use | ✓ | ✓ |
| Offline access | ✓ | ✓ |
| Works without external service | — | ✓ |
Why teams choose braid
Multi-tool support
Write once, install to 15+ tool formats. Cursor, Claude Code, OpenCode, Windsurf, Cline, Zed, and more — all from one library.
Automatic format conversion
braid writes rules in each tool's native format automatically. No manual commands, no folder juggling — one install covers every agent.
Team collaboration
Shared library with role-based permissions. One engineer writes a rule, everyone's agent uses it automatically.