Cursor & AI coding tools

Drop a PromptVCS rule into your AI coding assistant and it will manage prompts the right way from day one — fetching them at runtime by name instead of hardcoding strings, and wiring up versioning, environments, and CI eval gates as it writes your app.

The rule is tool-agnostic. Cursor, Windsurf, Claude Code, and GitHub Copilot all read a project rules file and use it to steer every suggestion.

One-line install

From your project root, drop the rule where your tool expects it:

# Cursor
mkdir -p .cursor/rules && curl -o .cursor/rules/promptvcs.mdc https://prompt-vcs-delta.vercel.app/promptvcs.mdc

# Windsurf
curl -o .windsurfrules https://prompt-vcs-delta.vercel.app/promptvcs.mdc

# GitHub Copilot
mkdir -p .github && curl -o .github/copilot-instructions.md https://prompt-vcs-delta.vercel.app/promptvcs.mdc

# Claude Code — append to your project's CLAUDE.md
curl https://prompt-vcs-delta.vercel.app/promptvcs.mdc >> CLAUDE.md

Where each tool reads rules

• Cursor — .cursor/rules/promptvcs.mdc
• Windsurf — .windsurfrules
• Claude Code — append to CLAUDE.md at the project root
• GitHub Copilot — .github/copilot-instructions.md

What the rule does

It tells the assistant to never hardcode prompts, and to fetch the deployed version at runtime with a small zero-dependency helper (no SDK to install):

// lib/promptvcs.ts
const PVCS_ENV =
  process.env.VERCEL_ENV === "production" ? "production" :
  process.env.VERCEL_ENV === "preview" ? "staging" : "development";

export async function getPrompt(name: string, env = PVCS_ENV) {
  const base = process.env.PROMPTVCS_API_URL ?? "https://prompt-vcs-delta.vercel.app";
  const res = await fetch(`${base}/api/v1/prompts/${name}/current?env=${env}`, {
    headers: { Authorization: `Bearer ${process.env.PROMPTVCS_API_KEY}` },
  });
  if (!res.ok) throw new Error(`PromptVCS ${res.status}`);
  return res.json();
}

The environment is derived from VERCEL_ENV(production → production, preview → staging, else development), so each deploy automatically reads the matching PromptVCS environment. It also documents the env vars (PROMPTVCS_API_KEY, optionalPROMPTVCS_API_URL), the pvcs CLI, and the promptvcs/eval-action@v1 CI gate. See the developer guide for the full API.

Read or copy the full rule here: https://prompt-vcs-delta.vercel.app/promptvcs.mdc.

Share it

Publishing the rule to cursor.directory makes it discoverable to every developer searching for AI-app rules — each adopter becomes a passive way for their teammates to find PromptVCS.