Yes, and this is exactly what Vilix is designed for. Define your rules once in Vilix and have every connected tool read them automatically before responding. There's no copy-pasting involved, no custom instruction panels to update in every single tool, and no risk of getting out of sync
The problem: every AI assistant is an island
Every serious AI tool comes with its own custom instructions or system prompt field. ChatGPT has “Custom Instructions.” Claude has Projects with custom instructions. Cursor has a .cursorrules file. Codex has a system prompt. So, if you want every one of these tools to know that your project uses TypeScript strict mode, prefers short answers, and has an API backend at a specific base URL, you have to copy the same block of text into every tool and keep them all in sync.
This is not ideal - especially when you're constantly starting new projects or adding new tools to your stack.
How Vilix solves it with user_rules and project_rules
Vilix has two types of rules, which live server-side in your account and get injected into every tool you connect:
user_rules: personal style directives
user_rules are short personal directives that apply everywhere in every project. For example: ‘keep answers under three paragraphs’, ‘never suggest installing a new dependency without asking first’, or “use British English spelling.”
You define them once, and every AI that connects to Vilix receives them on every turn.
project_rules: per-project stack and conventions
project_rules are attached to a specific Vilix project and contain technical context about it: the stack, the conventions, things the AI should or should not do in this project's codebase. Here's an example of what a project_rules might contain:
This project is a Next.js 14 app with TypeScript strict mode. Always use the App Router. Never use default exports for components. Tailwind only, no inline styles.
When you open this project in Vilix and then switch to ChatGPT, Claude, Cursor, or Codex - the AI auto-reads those rules before replying. You don't have to mention them in your query; they are already there.
How the auto-injection works
Vilix is an MCP-native memory layer. You connect it once as a custom MCP server at api.vilix.ai/mcp. Then, on every turn, the AI automatically calls two Vilix tools:
get_context : runs before the AI replies. It provides the AI with your recent conversation history, saved memories, semantically related past exchanges, user_rules, and the project_rules for whichever project is currently open.
save_turn : runs after the AI replies, to persist the exchange so future turns and other tools can see it.
You don't have to orchestrate this; the AI does it automatically. As a result, every reply from every tool starts with the same rules already loaded.
A concrete example: sharing rules between ChatGPT and Claude
Let's say I'm working on a SaaS product. In Vilix, I create a project called "Billing service" and add this project_rules:
Stack: Node.js, Stripe, PostgreSQL
Always wrap Stripe calls in try/catch and log the error to Sentry
API routes follow REST conventions, no GraphQL
Short answers preferred; include code snippets when the question is technical
I also have a user_rule: 'Never start a reply with the word "Certainly."'
Now I ask ChatGPT to write a new webhook handler - it reads the project and user rules via Vilix before replying. Then I switch to Claude to review the same webhook handler - and Claude reads the same rules from the same Vilix account. I get consistent, convention-aware output from both tools without having to repeat myself.
What tools are supported
Any tool that supports a custom MCP connector will work with Vilix rules. This includes ChatGPT, Claude, Claude Code, Cursor, Codex, Grok, Manus, GitHub Copilot, Windsurf, Lovable, OpenClaw, and Hermes. If a tool can point to an MCP endpoint, it connects to Vilix and automatically inherits your rules.
For a more detailed look at what cross-tool memory enables beyond just rules, see the cross-AI memory overview.
Setting up your first rules
After connecting Vilix to your first tool, there are a few ways to add rules. You can tell the AI to add a rule, and it will be added to your Vilix account right away. For example, you could say, "Add a user rule: always prefer async/await over promise chains." Or you can manage rules through the Vilix features panel.
Rules are versioned in your account, not in your tools. This means that whenever you improve a rule, all of your tools will see the new version on the next turn - no syncing needed.
If you want to have the same conventions in every tool without copy-pasting, the easiest way to start is by trying Vilix free and adding your first project_rules in the first session. From then on, every AI you connect to Vilix will have those rules.
Frequently asked questions
Can I share project rules between ChatGPT and Claude?
Yes! Connect both tools to Vilix as a custom MCP server at api.vilix.ai/mcp. Then, both will read your project rules automatically on every turn, giving them shared context without any copy-pasting.
What is the difference between user_rules and project_rules in Vilix?
user_rules are personal style directives that apply across every project and every tool. For example: your preferred answer length, tone, or habits you want the AI to avoid. project_rules are attached to a specific Vilix project and contain technical context about it: the stack, the conventions, the dos and don'ts for that particular codebase.
Do I need to mention my rules in every chat message?
No - Vilix automatically injects them via the get_context tool call that happens before every AI reply. You define the rules once, and the AI receives them silently on every turn, without you having to mention or reference them.
What happens if I update a rule? Do all tools pick it up?
Yes! Rules live server-side in your Vilix account, so the next time any of your tools call get_context, they will receive the new version of the rules. There is no per-tool update needed.
Which AI tools support Vilix rules?
Any tool that accepts a custom MCP connector: ChatGPT, Claude, Claude Code, Cursor, Codex, Grok, Manus, GitHub Copilot, Windsurf, Lovable, OpenClaw, and Hermes. If the tool can point to an MCP endpoint, it will connect to Vilix and automatically inherit your rules.
Top comments (0)