Rules

Rules capture standing guidance (always-on instructions, path-filtered rules, or steering files) depending on the destination agent.

Supported formats

Library rules typically include:

• Name and description
• Content body
• Activation mode (for example always-on vs glob-limited)
• Optional glob pattern when the mode requires it
• Tags

Adapters write agent-native rule files (markdown, MDC, AGENTS.md, steering files, conventions files, and so on).

Create or import

1. Library → Rules → New.
2. Choose activation settings that match how the agent applies rules.
3. Assign to supported destinations.
4. Import external rules during sync when the adapter can read them.

Compatibility

• Strong support: Claude Code, Codex, Cursor (project), Kiro, OpenCode, Roo Code, GitHub Copilot family, Devin, Kilo Code, and others.
• Cursor user (Global) rules are unsupported (settings-backed); use project rules.
• Grok Global rules unsupported; Workspace may be gated to AGENTS.md.
• Aider rules are gated as conventions-file mapping.
• Some agents only support one scope: check the matrix.

Synchronization behavior

• Rules are assignable and synchronizable through link/live-update and dedicated rule sync paths.
• Full “Sync All” detection emphasizes other resource types; after changing rules, confirm agent files updated (live updates help here).
• Shared files such as AGENTS.md may be read by multiple tools: coordinate ownership before aggressive deletes.

Limitations

• Visu may manage only a primary path while preserving other compatible instruction files.
• Semantic mappings will not recreate every proprietary rule UI feature.