cursorrules

VibeTrace — Automatic Conversation Recording xxxxxx、

You are an agent in a VibeTrace-enabled project. At the end of every response where you made code changes or provided a substantive answer, you MUST generate a metadata record of this conversation turn.

This metadata powers the VibeTrace VS Code extension, which gives the user a visual timeline of their entire project's vibe-coding journey.

---

1. Determine Session ID

The session_id identifies which agent window this conversation belongs to. It should be human-readable so the user can recognize it in the VibeTrace sidebar.

• First turn in this window: Create a session_id from the user's first request — a short CamelCase topic + 3 random lowercase letters. Example: user asks "add login page" → LoginPage-k7m.
• Subsequent turns: Reuse the session_id from earlier in this conversation. Do not change it.

---

2. Determine Module

The module field classifies which business feature this turn belongs to.

• BEFORE assigning a module, you MUST read the file .vibe/MODULE_DICT.md using the Read File tool.
• If the current work matches an existing module in the dictionary, use that EXACT name (case-sensitive).
• If NO existing module matches, you may create a new one.
  • New module names should be short CamelCase (e.g., UserProfile, PaymentGateway, DashboardUI).
  • Do NOT create variants of existing modules (e.g., if Auth exists, do NOT create Authentication or auth).

---

3. Generate the Metadata JSON

After completing the user's request, create a JSON file with the following structure:

{
  "id": "<YYYYMMDD>-<session_id>-<3randomchars>",
  "session_id": "<ShortTopic>-<3chars>, e.g. WechatQrLogin-a3f",
  "module": "<your determined module name>",

  "original_prompt": "<the user's raw prompt, copied verbatim>",
  "intent": "<1-sentence condensation of what the USER asked for>",
  "summary": "<1-sentence summary of what YOU did to fulfill it>",

  "impactFiles": [
    {
      "path": "relative/path/to/file.ts",
      "action": "create | modify | delete | read",
      "description": "<one-line description of what changed and why>"
    }
  ],

  "unresolved_issues": "<optional — things left undone, config needed, follow-up required>"
}