VibeXP
← FeaturesPromptsYour reusable library

Stop rewriting the same prompts.

Save your best prompts once as templates. Fill in {{variables}}, reference other prompts with @, and reach the result from every AI tool you use, over one MCP connection.

Run VibeXP →Read the docs

The problem.

Without it
01

You rewrite from memory

The prompt that worked last week is being retyped now: slightly worse, a few minutes slower, every single time.

02

Results are inconsistent

Different wording every time means different quality every time. With no standard to reach for, the output drifts.

03

They are lost in chat history

Buried in a ChatGPT thread, a notes app or a teammate's head. A prompt you cannot find is a prompt you do not have.

How it works.

Prompts
Composable building blocksAdvanced features ↗

Build prompts from prompts

Type @ inside a prompt to embed another one by reference, and wrap anything that changes in {{double braces}}. Update a building block once and every prompt that uses it stays in step.

  • Dependency graph. A live uses and used-by map, and a prompt others reference is protected from accidental deletion.
  • Render before you send. Fill the variables, including inherited ones, and see the exact text your AI will receive.
# code-review
Review this {{language}} diff.
Apply @coding-standards and report using @output-format.
Every tool, one libraryPrompts over MCP ↗

Write it once, use it everywhere

Expose a prompt over MCP and it shows up inside Claude Code, Cursor, VS Code and Gemini CLI as a native prompt, or your agent renders it by slug. The CLI and REST API reach the same library.

  • Version history. Every change is snapshotted with its author; diff any two versions and restore without losing newer work.
  • Labels, projects and search. Group, tag and find prompts by meaning rather than by exact words.
vibexp_io_render_prompt(
  slug: "code-review",
  values: { language: "Go" }
)
Frequently askedAll documentation ↗
How do variables work?

Wrap any changeable part of a prompt in {{double braces}} to turn it into a fill-in-the-blanks template. When you use the prompt, you fill in the values and VibeXP renders the final text.

In the docs ↗
What are @-references?

Type @ inside a prompt to embed another prompt by reference. The referenced text is inlined when the prompt is rendered, so you maintain one building block and every prompt that uses it stays in sync.

In the docs ↗
Which tools can use my prompts?

Any MCP client that supports MCP OAuth, over a single connection: Claude Code, Cursor, VS Code, Gemini CLI and more. The CLI and the REST API reach the same prompts.

In the docs ↗
Can I track and roll back changes?

Yes. Every change is snapshotted with its author and time. Diff any two versions and restore an earlier one without losing newer work.

In the docs ↗
One click, and it helps more than you would think

Star the repo

Stars are how the next person tired of re-explaining their project to an AI finds this. It is the whole of the distribution: no ad budget, no sales team, no hosted plan to upsell.

Star on GitHub

Build a prompt library you will actually reuse.

Free, open source and self-hosted. One command to run it, one to connect your AI tools, and everything else in the docs.

Run VibeXP →Every feature