pmpt-cli 1.14.15 → 1.14.18

package/dist/commands/clone.js

@@ -1,6 +1,6 @@
 import * as p from '@clack/prompts';
 import { join, dirname, resolve, sep } from 'path';
-import { existsSync, mkdirSync, writeFileSync, readFileSync, readdirSync } from 'fs';
+import { existsSync, mkdirSync, writeFileSync, readFileSync } from 'fs';
 import { isInitialized, getConfigDir, getHistoryDir, getDocsDir, initializeProject } from '../lib/config.js';
 import { validatePmptFile, isSafeFilename } from '../lib/pmptFile.js';
 import { fetchPmptFile, trackClone } from '../lib/api.js';
@@ -110,7 +110,8 @@ export async function cmdClone(slug) {
     const pmptDir = getConfigDir(projectPath);
     const historyDir = getHistoryDir(projectPath);
     const docsDir = getDocsDir(projectPath);
-    restoreHistory(historyDir, pmptData.history);
+    // History is not restored — user's journey starts fresh from v1.
+    // The version summary is embedded in pmpt.ai.md for AI reference.
     if (pmptData.docs) {
         restoreDocs(docsDir, pmptData.docs);
     }
@@ -160,7 +161,9 @@ export async function cmdClone(slug) {
         `- When requirements change or new decisions are made`,
         '',
         `Keep the Progress and Snapshot Log sections in pmpt.md up to date.`,
-        `After significant milestones, run \`pmpt save\` to create a snapshot.`,
+        `After significant milestones, save a snapshot:`,
+        `- **If pmpt MCP tool is available** (Claude Code, Cursor with MCP): call \`pmpt_save\` directly with a descriptive summary. Do this proactively — do not wait for the user to ask.`,
+        `- **Otherwise**: run \`pmpt save\` in terminal.`,
         '',
         '---',
         '',
@@ -175,16 +178,13 @@ export async function cmdClone(slug) {
             answers: pmptData.plan,
         }, null, 2), 'utf-8');
     }
-    let versionCount = 0;
-    if (existsSync(historyDir)) {
-        versionCount = readdirSync(historyDir).filter((d) => d.startsWith('v')).length;
-    }
     importSpinner.stop('Restore complete!');
     // Track clone event (fire-and-forget)
     trackClone(slug);
     p.note([
         `Project: ${pmptData.meta.projectName}`,
-        `Versions: ${versionCount}`,
+        `Cloned from: @${pmptData.meta.author || 'unknown'} (${pmptData.history.length} versions)`,
+        `Your history: starts fresh from v1`,
         `Location: ${pmptDir}`,
     ].join('\n'), 'Clone Summary');
     // Copy AI prompt to clipboard

package/dist/commands/remix.js

@@ -88,12 +88,24 @@ ${contextSection}${techSection}
 
 ## Instructions for AI
 
-This is a **remix** of an existing project. Build my version based on the differentiation above.
+This is a **remix** of an existing project. Before building anything, do the following:
 
-1. Read the original project below to understand the structure and approach.
-2. Build MY version — same core concept, but with my differentiation applied throughout.
-3. Do NOT copy content verbatim. Adapt everything to fit my context.
-4. Start with core features first, then iterate.
+**Step 1 — Understand & Clarify (do this first)**
+
+Read my "My Version" section above and the original project below carefully, then ask me clarifying questions. Specifically, identify:
+- Anything in my differentiation that is ambiguous or unclear
+- Information that would be needed to build my version but is not provided
+- Assumptions you would have to make — ask instead of assuming
+- Any conflict between my twist and the original that needs resolution
+
+Ask all your questions in a single message. Wait for my answers before proceeding.
+
+**Step 2 — Build**
+
+After I answer your questions, build MY version based on the differentiation and my answers.
+- Same core concept as the original, but with my differentiation applied throughout
+- Do NOT copy content verbatim. Adapt everything to fit my context
+- Start with core features first, then iterate
 
 ### Documentation Rule
 
@@ -102,7 +114,9 @@ When you make progress, update \`.pmpt/docs/pmpt.md\`:
 - When a feature is implemented (mark as done)
 - When a development phase is completed
 
-Keep the Snapshot Log up to date. Run \`pmpt save\` after milestones.
+Keep the Snapshot Log up to date. After milestones, save a snapshot:
+- **If pmpt MCP tool is available** (Claude Code, Cursor with MCP): call \`pmpt_save\` directly with a descriptive summary. Do this proactively — do not wait for the user to ask.
+- **Otherwise**: run \`pmpt save\` in terminal.
 
 ---
 

package/dist/lib/plan.js

@@ -98,13 +98,21 @@ ${workflowSteps}
 - When requirements change or new decisions are made
 
 Keep the Progress and Snapshot Log sections in pmpt.md up to date.
-After significant milestones, run \`pmpt save\` to create a snapshot.
+After significant milestones, save a snapshot using the method below.
+
+### Saving Snapshots
+
+**If the pmpt MCP tool is available** (Claude Code, Cursor with MCP configured):
+Call the \`pmpt_save\` MCP tool directly with a descriptive summary. Do this proactively after milestones — do not wait for the user to ask.
+
+**Otherwise:**
+Run \`pmpt save\` in the terminal.
 
 ### Per-Feature Checklist
 After completing each feature above:
 1. Mark the feature done in \`.pmpt/docs/pmpt.md\` (change \`- [ ]\` to \`- [x]\`)
 2. Add a brief note to the Snapshot Log section
-3. Run \`pmpt save\` in terminal
+3. Save a snapshot (MCP tool or \`pmpt save\`)
 
 ### What to Record in pmpt.md
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pmpt-cli",
-  "version": "1.14.15",
+  "version": "1.14.18",
   "description": "Record and share your AI-driven product development journey",
   "type": "module",
   "bin": {