Stop re-explaining your standards to every AI tool.
Your coding rules live in CLAUDE.md here, .cursorrules there, AGENTS.md somewhere else — scattered across repos and tools. Blueprints keeps every rule that shapes your AI in one versioned, team-shared library: import straight from GitHub, organize it per tool, and reach it from everywhere you work.
Free and open source · Self-host it · Works with the tools you already use
Configures the AI tools you already use
Every AI tool wants its own rules file.
The standards that should be one source of truth end up copied into five — and they never stay in sync.
Rules are scattered
CLAUDE.md in one repo, .cursorrules in another, AGENTS.md somewhere else. No single source of truth for how your AI should behave.
They drift out of sync
You fix a convention in one place and forget the other four. Each tool slowly behaves a little differently — and nobody notices until it bites.
You re-explain them every session
New chat, new tool, new teammate — you restate the same standards from scratch, again. Your stack, your conventions, every time.
One library for every rule your AI follows.
Blueprints is the versioned, team-shared home for your AI’s standards and config — organized per tool, searchable, and reachable everywhere your AI works. One place to keep your coding standards, instruction files, and tool config, instead of five.
Prompts are what you ask. Blueprints are the rules it always follows.
The task you hand the AI — reusable, composable instructions you invoke per job. Explore Prompts →
The standing standards and config the AI obeys on every task — your coding conventions, instruction files, and tool config, organized per tool.
Lead featureOne-click GitHub import
Already wrote the rules? Import them in one click.
Connect your GitHub repo and VibeXP pulls in your existing AI-config files — CLAUDE.md, AGENTS.md, .cursorrules, plus everything under .claude/, .cursor/, .codex/, and .agents/ — and automatically sorts each one by tool and kind. No copy-paste, no reformatting.
- Auto-classified. Each file is typed by tool and kind — rules, sub-agent, skill, slash-command — with front-matter parsed for titles and descriptions.
- Idempotent & reported. A clear import report — scanned, imported, skipped, failed — and re-imports skip what’s already there.
Organized per tool
Sorted by the tool it configures.
Every blueprint is typed for the tool it belongs to — Claude Code, Claude, Cursor, or Codex — so you (and your AI) always reach the right rules for the right tool. Filter, search, and group by project.
- Typed, not tangled. A tool badge on every blueprint — usable as a list filter across your whole library.
- Grouped by project. Every blueprint belongs to a project, with search, type filter, and sort to keep big libraries tidy.
Version history
Your rules change. Track every change, restore any version.
Standards evolve. VibeXP snapshots every edit with who changed it and when — diff any two versions side by side and roll back safely. No more “who loosened this rule, and when?”
- Treat rules like code. Author attribution and timestamps on every snapshot, with a searchable timeline.
- Diff & non-destructive restore. Compare split or unified; restoring is itself a new version, so nothing is lost.
One set of rules, every tool you use.
Your AI pulls the right rules from your library over one MCP connection — Claude Code, Cursor, Codex — and you can reach them from the CLI and API too. Update a rule once; everywhere that uses it stays current.
https://connect.vibexp.io/mcp/v1/commonFind the right rule. Know which ones matter.
Search your whole knowledge base by meaning — and see which standards your workflow actually leans on, broken down by channel.
Better on your own. Unstoppable with your team.
- Start solo. Import your rules today — every session starts from your standards, not a blank slate you re-explain.
- Expand to your team. Blueprints live in a shared workspace — everyone’s AI follows the same standards, every change is attributed, and new teammates inherit your conventions on day one instead of guessing.
Questions, answered
Everything you need to know before you put your AI’s rules in one place.
Give your AI one set of rules to follow.
Import your scattered rules files, organize them per tool, and reach them from everywhere you work. Free and open source — self-host it.
Free and open source · Self-host it · Works with the tools you already use