Meta-prompting, context engineering, and centralized instructions management for AI coding agents

Guides AI systems to operate with a deep understanding of system architecture, domain constraints, and engineering standards.
Gives every agent the same context, standards, and guardrails — across any IDE, any team.

Get Started See it in action GitHub

Why AI Agents Need Rosetta

AI coding agents are everywhere. Consistency and context are not.

System Status: Unmanaged AI Agents
MISSED CONVENTIONS
Agents lack your architecture, business rules, and compliance requirements. They produce code that violates conventions, causing expensive rework and high rejection rates.
INSTRUCTIONS DON'T SCALE
Every engineer writes their own prompts — or none at all. Crafting effective instructions takes hours of work per task, they go stale fast, and there's no way to version, review, or govern them.
NO CROSS-IDE REUSE
Prompt libraries are IDE-specific and fragile. Switch from Cursor to Claude Code? Rewrite everything. New model drops? Start over. The same problem gets solved differently on every team.
SILOED KNOWLEDGE
Patterns proven in one project never reach others. Senior expertise stays in people's heads. Breaking changes cascade undetected across services because agents see one repo, not the system.
Rosetta solves this. See how ↓

Try Rosetta

Pick a scenario and see how Rosetta handles it step by step.

Rosetta analyzing your request…
Rosetta

Pick a scenario on the left to start

Get Started

Four steps to connect Rosetta to your IDE and start coding smarter.

1

Add Rosetta MCP to your IDE

Pick your editor. No local install needed — Rosetta connects over HTTP.

Rosetta is designed to never use or see your data or IP.
 ‼️ You must receive a prior approval from your manager and company to use it. ‼️ 

Cursor: Settings → Cursor Settings → MCP → Add new global MCP server or paste into ~/.cursor/mcp.json
Windsurf: add via MCP settings in IDE

{
  "mcpServers": {
    "Rosetta": {
      "url": "[rosetta MCP production server URL]"
    }
  }
}

Run this command in your terminal:

$ claude mcp add --transport http Rosetta \
    [rosetta MCP production server URL]

Run these commands in your terminal:

$ codex mcp add Rosetta \
    --url [rosetta MCP production server URL]
$ codex mcp login Rosetta

Add to .vscode/mcp.json or ~/.mcp.json:

{
  "servers": {
    "Rosetta": {
      "type": "http",
      "url": "[rosetta MCP production server URL]"
    }
  }
}

Go to Settings → Tools → GitHub Copilot → MCP Settings, add to ~/.config/github-copilot/intellij/mcp.json:

{
  "servers": {
    "Rosetta": {
      "type": "http",
      "url": "[rosetta MCP production server URL]"
    }
  }
}

Go to Settings → Tools → Junie → MCP Settings → + Add → As JSON:

{
  "mcpServers": {
    "Rosetta": {
      "url": "[rosetta MCP production server URL]"
    }
  }
}

Add to your Antigravity MCP config file:

{
  "mcpServers": {
    "Rosetta": {
      "url": "[rosetta MCP production server URL]"
    }
  }
}

Add to your opencode.json file:

{
  "mcp": {
    "Rosetta": {
      "type": "http",
      "url": "[rosetta MCP production server URL]",
      "enabled": true
    }
  }
}
2

Complete OAuth

Your IDE will open a browser window to authenticate. Complete the OAuth flow when prompted.

3

Verify & Initialize

Restart your IDE, then verify Rosetta is connected:

# "What can you do, Rosetta?"

Then initialize your repository:

# "Initialize this repository using Rosetta"
4

Add Bootstrap Rule (optional)

If something does not work — download bootstrap.md and add it to your IDE's instruction file. See Quick Start for file paths per IDE.

✓
You're set. Rosetta is active. Talk naturally — Rosetta will pick the right workflow automatically.
See all workflows →
Agent-agnostic by design. Use frontier-class models (Claude Sonnet 4.6, GPT-5.3-codex-medium, Gemini 3.1 Pro) or better for best results.

Without Rosetta vs With Rosetta

Real enterprise cases. Same task — different results.

Without Rosetta
"Implement data changes from an Excel spec across two interconnected databases."
  • Started writing queries without understanding the full picture
  • Missed cross-schema relationships and dependent services
  • Ignored stored procedures, triggers, and legacy integrations
  • Produced partial SQL that would break downstream on deploy
Broken deploy. Hours of manual debugging.
With Rosetta
"Implement data changes from an Excel spec across two interconnected databases."
  • Loaded both database schemas and mapped every relationship
  • Identified all services and APIs depending on affected tables
  • Found missing fields and web services that needed updates
  • Discovered additional connections hidden in legacy COBOL code
  • Assembled full end-to-end implementation with all dependencies resolved
Complete implementation. Nothing missed — even legacy connections.
Without Rosetta
"Modernize this C++ service with Windows components into a new architecture."
  • Scanned a few files and suggested a generic rewrite
  • Missed Windows-specific dependencies and COM components
  • Couldn't determine what to reuse vs replace
  • Produced a vague spec — team still had to reverse-engineer the original
Spec full of gaps. Team starts over manually.
With Rosetta
"Modernize this C++ service with Windows components into a new architecture."
  • Systematically analyzed every class, method, and dependency
  • Mapped Windows components, libraries, and service boundaries
  • Determined what to reuse, what to replace, and what to drop
  • Created a target spec with interfaces, edge cases, and architecture decisions
  • Spec so precise that developers could ask AI follow-ups and get exact answers
Production-ready spec. Team moved straight to implementation.
Without Rosetta
"Add discount code support to checkout — requires changes across API gateway, pricing service, and order service."
  • Agent modified the pricing service without seeing the API gateway contract
  • Broke the order service integration — different payload format expected
  • No awareness of shared validation rules or error handling conventions
  • Each service fixed separately, introducing new inconsistencies
Three services out of sync. Integration tests failing for days.
With Rosetta
"Add discount code support to checkout — requires changes across API gateway, pricing service, and order service."
  • Rosetta loaded architecture, API contracts, and shared schemas across all three services
  • Agent produced a coordinated spec covering gateway routing, pricing logic, and order updates
  • Validation rules and error handling followed existing patterns automatically
  • Changes reviewed as a single coherent plan before any code was written
All three services updated in sync. Integration tests green on first run.