npm - rivet-design - Versions diffs - 0.9.1 → 0.9.3 - Mend

rivet-design 0.9.1 → 0.9.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (138) hide show

package/dist/mcp/agent-variants/SessionStore.d.ts +63 -2
package/dist/mcp/agent-variants/SessionStore.d.ts.map +1 -1
package/dist/mcp/agent-variants/SessionStore.js +331 -71
package/dist/mcp/agent-variants/SessionStore.js.map +1 -1
package/dist/mcp/agent-variants/WorktreeOrchestrator.d.ts +197 -8
package/dist/mcp/agent-variants/WorktreeOrchestrator.d.ts.map +1 -1
package/dist/mcp/agent-variants/WorktreeOrchestrator.js +805 -46
package/dist/mcp/agent-variants/WorktreeOrchestrator.js.map +1 -1
package/dist/mcp/agent-variants/contracts.d.ts +1101 -9
package/dist/mcp/agent-variants/contracts.d.ts.map +1 -1
package/dist/mcp/agent-variants/contracts.js +131 -5
package/dist/mcp/agent-variants/contracts.js.map +1 -1
package/dist/mcp/agent-variants/createZeroToOneTool.d.ts +205 -0
package/dist/mcp/agent-variants/createZeroToOneTool.d.ts.map +1 -0
package/dist/mcp/agent-variants/createZeroToOneTool.js +295 -0
package/dist/mcp/agent-variants/createZeroToOneTool.js.map +1 -0
package/dist/mcp/agent-variants/designContextStore.d.ts +160 -0
package/dist/mcp/agent-variants/designContextStore.d.ts.map +1 -0
package/dist/mcp/agent-variants/designContextStore.js +295 -0
package/dist/mcp/agent-variants/designContextStore.js.map +1 -0
package/dist/mcp/agent-variants/elementRefToTarget.d.ts +21 -0
package/dist/mcp/agent-variants/elementRefToTarget.d.ts.map +1 -0
package/dist/mcp/agent-variants/elementRefToTarget.js +47 -0
package/dist/mcp/agent-variants/elementRefToTarget.js.map +1 -0
package/dist/mcp/agent-variants/errors.d.ts +1 -1
package/dist/mcp/agent-variants/errors.d.ts.map +1 -1
package/dist/mcp/agent-variants/errors.js +6 -0
package/dist/mcp/agent-variants/errors.js.map +1 -1
package/dist/mcp/agent-variants/index.d.ts +4 -1
package/dist/mcp/agent-variants/index.d.ts.map +1 -1
package/dist/mcp/agent-variants/index.js +7 -1
package/dist/mcp/agent-variants/index.js.map +1 -1
package/dist/mcp/agent-variants/inspirationDesignContext.d.ts +430 -0
package/dist/mcp/agent-variants/inspirationDesignContext.d.ts.map +1 -0
package/dist/mcp/agent-variants/inspirationDesignContext.js +2379 -0
package/dist/mcp/agent-variants/inspirationDesignContext.js.map +1 -0
package/dist/mcp/agent-variants/pendingChangesAdapter.d.ts.map +1 -1
package/dist/mcp/agent-variants/pendingChangesAdapter.js +10 -7
package/dist/mcp/agent-variants/pendingChangesAdapter.js.map +1 -1
package/dist/mcp/agent-variants/sourceContext.d.ts +7 -0
package/dist/mcp/agent-variants/sourceContext.d.ts.map +1 -0
package/dist/mcp/agent-variants/sourceContext.js +158 -0
package/dist/mcp/agent-variants/sourceContext.js.map +1 -0
package/dist/mcp/agent-variants/tools.d.ts +14 -0
package/dist/mcp/agent-variants/tools.d.ts.map +1 -1
package/dist/mcp/agent-variants/tools.js +330 -15
package/dist/mcp/agent-variants/tools.js.map +1 -1
package/dist/mcp/changeBatchClassification.d.ts +30 -0
package/dist/mcp/changeBatchClassification.d.ts.map +1 -0
package/dist/mcp/changeBatchClassification.js +65 -0
package/dist/mcp/changeBatchClassification.js.map +1 -0
package/dist/mcp/server.d.ts.map +1 -1
package/dist/mcp/server.js +237 -39
package/dist/mcp/server.js.map +1 -1
package/dist/proxy-middleware/proxy-config.d.ts.map +1 -1
package/dist/proxy-middleware/proxy-config.js +1 -15
package/dist/proxy-middleware/proxy-config.js.map +1 -1
package/dist/routes/agentVariants.d.ts +3 -1
package/dist/routes/agentVariants.d.ts.map +1 -1
package/dist/routes/agentVariants.js +131 -13
package/dist/routes/agentVariants.js.map +1 -1
package/dist/routes/mcp.d.ts +7 -1
package/dist/routes/mcp.d.ts.map +1 -1
package/dist/routes/mcp.js +139 -16
package/dist/routes/mcp.js.map +1 -1
package/dist/server.d.ts.map +1 -1
package/dist/server.js +2 -2
package/dist/server.js.map +1 -1
package/dist/services/SessionBridgeService.d.ts +22 -0
package/dist/services/SessionBridgeService.d.ts.map +1 -1
package/dist/services/SessionBridgeService.js +61 -0
package/dist/services/SessionBridgeService.js.map +1 -1
package/dist/services/TelemetryService.d.ts +121 -0
package/dist/services/TelemetryService.d.ts.map +1 -1
package/dist/services/TelemetryService.js +155 -0
package/dist/services/TelemetryService.js.map +1 -1
package/dist/services/WorktreeManager.d.ts +57 -5
package/dist/services/WorktreeManager.d.ts.map +1 -1
package/dist/services/WorktreeManager.js +205 -13
package/dist/services/WorktreeManager.js.map +1 -1
package/dist/services/templates/designCatalog.d.ts +27 -0
package/dist/services/templates/designCatalog.d.ts.map +1 -0
package/dist/services/templates/designCatalog.js +141 -0
package/dist/services/templates/designCatalog.js.map +1 -0
package/dist/services/templates/designmd/airbnb.md +545 -0
package/dist/services/templates/designmd/airtable.md +554 -0
package/dist/services/templates/designmd/apple.md +562 -0
package/dist/services/templates/designmd/binance.md +634 -0
package/dist/services/templates/designmd/bmw-m.md +503 -0
package/dist/services/templates/designmd/bmw.md +544 -0
package/dist/services/templates/designmd/bugatti.md +454 -0
package/dist/services/templates/designmd/cal.md +542 -0
package/dist/services/templates/designmd/claude.md +589 -0
package/dist/services/templates/designmd/clay.md +541 -0
package/dist/services/templates/designmd/cohere.md +451 -0
package/dist/services/templates/designmd/cursor.md +537 -0
package/dist/services/templates/designmd/expo.md +526 -0
package/dist/services/templates/designmd/figma.md +578 -0
package/dist/services/templates/designmd/framer.md +544 -0
package/dist/services/templates/designmd/hp.md +670 -0
package/dist/services/templates/designmd/linear.app.md +548 -0
package/dist/services/templates/designmd/mintlify.md +852 -0
package/dist/services/templates/designmd/miro.md +825 -0
package/dist/services/templates/designmd/notion.md +821 -0
package/dist/services/templates/designmd/raycast.md +669 -0
package/dist/services/templates/designmd/resend.md +585 -0
package/dist/services/templates/designmd/sentry.md +262 -0
package/dist/services/templates/designmd/shopify.md +350 -0
package/dist/services/templates/designmd/spotify.md +246 -0
package/dist/services/templates/designmd/stripe.md +322 -0
package/dist/services/templates/designmd/supabase.md +255 -0
package/dist/services/templates/designmd/superhuman.md +252 -0
package/dist/services/templates/designmd/uber.md +295 -0
package/dist/services/templates/designmd/vercel.md +310 -0
package/dist/services/templates/viteReactTs.d.ts +42 -0
package/dist/services/templates/viteReactTs.d.ts.map +1 -0
package/dist/services/templates/viteReactTs.js +267 -0
package/dist/services/templates/viteReactTs.js.map +1 -0
package/dist/types/change-request-types.d.ts +15 -3
package/dist/types/change-request-types.d.ts.map +1 -1
package/dist/utils/skills/claude-skill.d.ts +2 -2
package/dist/utils/skills/claude-skill.d.ts.map +1 -1
package/dist/utils/skills/claude-skill.js +19 -98
package/dist/utils/skills/claude-skill.js.map +1 -1
package/dist/utils/skills/cursor-rules.d.ts +2 -2
package/dist/utils/skills/cursor-rules.d.ts.map +1 -1
package/dist/utils/skills/cursor-rules.js +15 -80
package/dist/utils/skills/cursor-rules.js.map +1 -1
package/dist/utils/skills/shared-variants-protocol.d.ts +23 -0
package/dist/utils/skills/shared-variants-protocol.d.ts.map +1 -0
package/dist/utils/skills/shared-variants-protocol.js +131 -0
package/dist/utils/skills/shared-variants-protocol.js.map +1 -0
package/package.json +4 -3
package/src/ui/dist/assets/main-C9jfEp80.css +1 -0
package/src/ui/dist/assets/main-DejhsBWR.js +382 -0
package/src/ui/dist/index.html +2 -2
package/src/ui/dist/assets/main-Bv0LuxKz.js +0 -382
package/src/ui/dist/assets/main-BzmseUDd.css +0 -1

package/dist/services/templates/viteReactTs.js ADDED Viewed

@@ -0,0 +1,267 @@
+"use strict";
+var __importDefault = (this && this.__importDefault) || function (mod) {
+    return (mod && mod.__esModule) ? mod : { "default": mod };
+};
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.writeTemplateBundle = exports.writeCreateAppTemplate = exports.isDestinationEmpty = exports.VITE_REACT_TS_TEMPLATE = exports.CREATE_APP_TEMPLATE_FILES = void 0;
+const fs_1 = __importDefault(require("fs"));
+const path_1 = __importDefault(require("path"));
+const TEMPLATE_FILES = [
+    {
+        relativePath: 'package.json',
+        contents: `{
+  "name": "rivet-created-app",
+  "private": true,
+  "version": "0.0.0",
+  "type": "module",
+  "scripts": {
+    "dev": "vite",
+    "build": "tsc -b && vite build",
+    "preview": "vite preview"
+  },
+  "dependencies": {
+    "@vitejs/plugin-react": "^5.1.1",
+    "typescript": "~5.9.3",
+    "vite": "^7.3.1",
+    "react": "^19.2.0",
+    "react-dom": "^19.2.0"
+  },
+  "devDependencies": {
+    "@types/react": "^19.2.7",
+    "@types/react-dom": "^19.2.3"
+  }
+}
+`,
+    },
+    {
+        relativePath: 'index.html',
+        contents: `<!doctype html>
+<html lang="en">
+  <head>
+    <meta charset="UTF-8" />
+    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
+    <title>Rivet Created App</title>
+  </head>
+  <body>
+    <div id="root"></div>
+    <script type="module" src="/src/main.tsx"></script>
+  </body>
+</html>
+`,
+    },
+    {
+        relativePath: 'tsconfig.json',
+        contents: `{
+  "files": [],
+  "references": [
+    { "path": "./tsconfig.app.json" },
+    { "path": "./tsconfig.node.json" }
+  ]
+}
+`,
+    },
+    {
+        relativePath: 'tsconfig.app.json',
+        contents: `{
+  "compilerOptions": {
+    "tsBuildInfoFile": "./node_modules/.tmp/tsconfig.app.tsbuildinfo",
+    "target": "ES2022",
+    "useDefineForClassFields": true,
+    "lib": ["ES2022", "DOM", "DOM.Iterable"],
+    "allowJs": false,
+    "skipLibCheck": true,
+    "esModuleInterop": true,
+    "allowSyntheticDefaultImports": true,
+    "strict": true,
+    "forceConsistentCasingInFileNames": true,
+    "module": "ESNext",
+    "moduleResolution": "Bundler",
+    "resolveJsonModule": true,
+    "isolatedModules": true,
+    "noEmit": true,
+    "jsx": "react-jsx"
+  },
+  "include": ["src"]
+}
+`,
+    },
+    {
+        relativePath: 'tsconfig.node.json',
+        contents: `{
+  "compilerOptions": {
+    "tsBuildInfoFile": "./node_modules/.tmp/tsconfig.node.tsbuildinfo",
+    "target": "ES2023",
+    "lib": ["ES2023"],
+    "module": "ESNext",
+    "skipLibCheck": true,
+    "moduleResolution": "Bundler",
+    "allowImportingTsExtensions": true,
+    "verbatimModuleSyntax": true,
+    "moduleDetection": "force",
+    "noEmit": true,
+    "strict": true
+  },
+  "include": ["vite.config.ts"]
+}
+`,
+    },
+    {
+        relativePath: 'vite.config.ts',
+        contents: `import { defineConfig } from 'vite';
+import react from '@vitejs/plugin-react';
+export default defineConfig({
+  plugins: [react()],
+});
+`,
+    },
+    {
+        relativePath: '.gitignore',
+        contents: `node_modules
+dist
+.DS_Store
+.env
+.env.local
+`,
+    },
+    {
+        relativePath: 'src/main.tsx',
+        contents: `import { StrictMode } from 'react';
+import { createRoot } from 'react-dom/client';
+import './index.css';
+import App from './App';
+createRoot(document.getElementById('root')!).render(
+  <StrictMode>
+    <App />
+  </StrictMode>,
+);
+`,
+    },
+    {
+        relativePath: 'src/App.tsx',
+        contents: `const App = () => {
+  return (
+    <main className="app-shell">
+      <section className="hero">
+        <p className="eyebrow">Created with Rivet</p>
+        <h1>Describe what should exist, then refine it visually.</h1>
+        <p className="lede">
+          This starter will be replaced by Rivet's creation agent.
+        </p>
+      </section>
+    </main>
+  );
+};
+export default App;
+`,
+    },
+    {
+        relativePath: 'src/index.css',
+        contents: `:root {
+  color: #111111;
+  background: #f7f4ef;
+  font-family:
+    Inter, ui-sans-serif, system-ui, -apple-system, BlinkMacSystemFont, "Segoe UI",
+    sans-serif;
+  font-synthesis: none;
+  text-rendering: optimizeLegibility;
+  -webkit-font-smoothing: antialiased;
+  -moz-osx-font-smoothing: grayscale;
+}
+* {
+  box-sizing: border-box;
+}
+body {
+  margin: 0;
+  min-width: 320px;
+  min-height: 100vh;
+}
+button,
+input,
+textarea {
+  font: inherit;
+}
+.app-shell {
+  min-height: 100vh;
+  display: grid;
+  place-items: center;
+  padding: 48px;
+}
+.hero {
+  max-width: 760px;
+}
+.eyebrow {
+  margin: 0 0 16px;
+  color: #ff3300;
+  font-size: 13px;
+  font-weight: 700;
+  letter-spacing: 0;
+  text-transform: uppercase;
+}
+h1 {
+  margin: 0;
+  font-size: clamp(42px, 7vw, 88px);
+  line-height: 0.95;
+  letter-spacing: 0;
+}
+.lede {
+  max-width: 560px;
+  margin: 24px 0 0;
+  color: #555555;
+  font-size: 20px;
+  line-height: 1.5;
+}
+`,
+    },
+];
+exports.CREATE_APP_TEMPLATE_FILES = TEMPLATE_FILES;
+exports.VITE_REACT_TS_TEMPLATE = {
+    files: TEMPLATE_FILES,
+    devCommand: { cmd: 'npm', args: ['run', 'dev'] },
+    buildCommand: { cmd: 'npm', args: ['run', 'build'] },
+    packageManager: 'npm',
+};
+/**
+ * Return true when the destination can receive a generated app.
+ */
+const isDestinationEmpty = (destinationPath) => {
+    if (!fs_1.default.existsSync(destinationPath)) {
+        return true;
+    }
+    return fs_1.default.readdirSync(destinationPath).length === 0;
+};
+exports.isDestinationEmpty = isDestinationEmpty;
+/**
+ * Write the embedded Vite template into the destination folder.
+ *
+ * @effect Creates directories and writes files at destinationPath
+ */
+const writeCreateAppTemplate = (destinationPath) => {
+    (0, exports.writeTemplateBundle)(exports.VITE_REACT_TS_TEMPLATE, destinationPath);
+};
+exports.writeCreateAppTemplate = writeCreateAppTemplate;
+/**
+ * Write an arbitrary template bundle to a destination directory. Used by the
+ * MCP fresh-scaffold flow so callers can pin a specific bundle per worktree.
+ *
+ * @effect Creates directories and writes files at destinationPath
+ */
+const writeTemplateBundle = (bundle, destinationPath) => {
+    for (const file of bundle.files) {
+        const absolutePath = path_1.default.join(destinationPath, file.relativePath);
+        fs_1.default.mkdirSync(path_1.default.dirname(absolutePath), { recursive: true });
+        fs_1.default.writeFileSync(absolutePath, file.contents, 'utf8');
+    }
+};
+exports.writeTemplateBundle = writeTemplateBundle;
+//# sourceMappingURL=viteReactTs.js.map

package/dist/services/templates/viteReactTs.js.map ADDED Viewed

@@ -0,0 +1 @@

+ {"version":3,"file":"viteReactTs.js","sourceRoot":"","sources":["../../../src/services/templates/viteReactTs.ts"],"names":[],"mappings":";;;;;;AAAA,4CAAoB;AACpB,gDAAwB;AAqBxB,MAAM,cAAc,GAAmB;IACrC;QACE,YAAY,EAAE,cAAc;QAC5B,QAAQ,EAAE;;;;;;;;;;;;;;;;;;;;;;CAsBb;KACE;IACD;QACE,YAAY,EAAE,YAAY;QAC1B,QAAQ,EAAE;;;;;;;;;;;;CAYb;KACE;IACD;QACE,YAAY,EAAE,eAAe;QAC7B,QAAQ,EAAE;;;;;;;CAOb;KACE;IACD;QACE,YAAY,EAAE,mBAAmB;QACjC,QAAQ,EAAE;;;;;;;;;;;;;;;;;;;;;CAqBb;KACE;IACD;QACE,YAAY,EAAE,oBAAoB;QAClC,QAAQ,EAAE;;;;;;;;;;;;;;;;CAgBb;KACE;IACD;QACE,YAAY,EAAE,gBAAgB;QAC9B,QAAQ,EAAE;;;;;;CAMb;KACE;IACD;QACE,YAAY,EAAE,YAAY;QAC1B,QAAQ,EAAE;;;;;CAKb;KACE;IACD;QACE,YAAY,EAAE,cAAc;QAC5B,QAAQ,EAAE;;;;;;;;;;CAUb;KACE;IACD;QACE,YAAY,EAAE,aAAa;QAC3B,QAAQ,EAAE;;;;;;;;;;;;;;;CAeb;KACE;IACD;QACE,YAAY,EAAE,eAAe;QAC7B,QAAQ,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA8Db;KACE;CACF,CAAC;AAEW,QAAA,yBAAyB,GAAmB,cAAc,CAAC;AAE3D,QAAA,sBAAsB,GAAmB;IACpD,KAAK,EAAE,cAAc;IACrB,UAAU,EAAE,EAAE,GAAG,EAAE,KAAK,EAAE,IAAI,EAAE,CAAC,KAAK,EAAE,KAAK,CAAC,EAAE;IAChD,YAAY,EAAE,EAAE,GAAG,EAAE,KAAK,EAAE,IAAI,EAAE,CAAC,KAAK,EAAE,OAAO,CAAC,EAAE;IACpD,cAAc,EAAE,KAAK;CACtB,CAAC;AAEF;;GAEG;AACI,MAAM,kBAAkB,GAAG,CAAC,eAAuB,EAAW,EAAE;IACrE,IAAI,CAAC,YAAE,CAAC,UAAU,CAAC,eAAe,CAAC,EAAE,CAAC;QACpC,OAAO,IAAI,CAAC;IACd,CAAC;IACD,OAAO,YAAE,CAAC,WAAW,CAAC,eAAe,CAAC,CAAC,MAAM,KAAK,CAAC,CAAC;AACtD,CAAC,CAAC;AALW,QAAA,kBAAkB,sBAK7B;AAEF;;;;GAIG;AACI,MAAM,sBAAsB,GAAG,CAAC,eAAuB,EAAQ,EAAE;IACtE,IAAA,2BAAmB,EAAC,8BAAsB,EAAE,eAAe,CAAC,CAAC;AAC/D,CAAC,CAAC;AAFW,QAAA,sBAAsB,0BAEjC;AAEF;;;;;GAKG;AACI,MAAM,mBAAmB,GAAG,CACjC,MAAsB,EACtB,eAAuB,EACjB,EAAE;IACR,KAAK,MAAM,IAAI,IAAI,MAAM,CAAC,KAAK,EAAE,CAAC;QAChC,MAAM,YAAY,GAAG,cAAI,CAAC,IAAI,CAAC,eAAe,EAAE,IAAI,CAAC,YAAY,CAAC,CAAC;QACnE,YAAE,CAAC,SAAS,CAAC,cAAI,CAAC,OAAO,CAAC,YAAY,CAAC,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,CAAC,CAAC;QAC9D,YAAE,CAAC,aAAa,CAAC,YAAY,EAAE,IAAI,CAAC,QAAQ,EAAE,MAAM,CAAC,CAAC;IACxD,CAAC;AACH,CAAC,CAAC;AATW,QAAA,mBAAmB,uBAS9B"}

package/dist/types/change-request-types.d.ts CHANGED Viewed

@@ -61,6 +61,15 @@ export interface CommentChangeItem {
     instruction: string;
     /** Base64 data-URL images attached as visual reference for the instruction */
     images?: string[];
+    /**
+     * Marks this comment as a request to run the MCP variants flow on the
+     * targeted element instead of performing a direct apply. Undefined → standard
+     * comment apply. When present, the MCP server skips beginApplyingRun and
+     * routes the batch through propose_variants → approval → continue → commit.
+     */
+    variantRequest?: {
+        count: number;
+    };
 }
 /**
  * A free-text chat instruction not tied to any specific element.
@@ -102,9 +111,12 @@ export interface VariantChangeItem {
             ref: string;
         };
     } | {
-        kind: 'new-project';
-        /** Absolute path to the variant's worktree (rsync/copy source) */
-        sourceWorktreePath: string;
+        kind: 'project-created';
+        /** Project files have already been copied to `destinationPath` and an
+         *  initial commit landed. The agent only needs to optionally run
+         *  `npm install` and continue from there — no further file
+         *  operations are required. */
+        note: string;
     };
 }
 /**

package/dist/types/change-request-types.d.ts.map CHANGED Viewed

	@@ -1 +1 @@
1	- {"version":3,"file":"change-request-types.d.ts","sourceRoot":"","sources":["../../src/types/change-request-types.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,MAAM,WAAW,aAAa;IAC5B,OAAO,EAAE,UAAU,EAAE,CAAC;IACtB;;;OAGG;IACH,WAAW,EAAE,MAAM,EAAE,CAAC;IACtB;;;OAGG;IACH,gBAAgB,CAAC,EAAE,gBAAgB,CAAC;IACpC;;OAEG;IACH,OAAO,CAAC,EAAE,MAAM,CAAC;IACjB;;OAEG;IACH,UAAU,CAAC,EAAE,MAAM,CAAC;CACrB;AAED;;;GAGG;AACH,MAAM,WAAW,gBAAgB;IAC/B,gBAAgB,CAAC,EAAE,MAAM,CAAC;IAC1B,iBAAiB,CAAC,EAAE,MAAM,CAAC;CAC5B;AAED,MAAM,MAAM,UAAU,GAClB,eAAe,GACf,cAAc,GACd,iBAAiB,GACjB,cAAc,GACd,iBAAiB,CAAC;AAEtB,4DAA4D;AAC5D,MAAM,WAAW,eAAe;IAC9B,IAAI,EAAE,OAAO,CAAC;IACd,OAAO,EAAE,UAAU,CAAC;IACpB,QAAQ,EAAE,MAAM,CAAC;IACjB,IAAI,EAAE,MAAM,CAAC;IACb,EAAE,EAAE,MAAM,CAAC;CACZ;AAED,4DAA4D;AAC5D,MAAM,WAAW,cAAc;IAC7B,IAAI,EAAE,MAAM,CAAC;IACb,OAAO,EAAE,UAAU,CAAC;IACpB,IAAI,EAAE,MAAM,CAAC;IACb,EAAE,EAAE,MAAM,CAAC;CACZ;AAED;;;;GAIG;AACH,MAAM,WAAW,iBAAiB;IAChC,IAAI,EAAE,SAAS,CAAC;IAChB,OAAO,EAAE,UAAU,CAAC;IACpB,yDAAyD;IACzD,QAAQ,CAAC,EAAE,UAAU,EAAE,CAAC;IACxB,WAAW,EAAE,MAAM,CAAC;IACpB,8EAA8E;IAC9E,MAAM,CAAC,EAAE,MAAM,EAAE,CAAC;~~CACnB~~;AAED;;;GAGG;AACH,MAAM,WAAW,cAAc;IAC7B,IAAI,EAAE,MAAM,CAAC;IACb,WAAW,EAAE,MAAM,CAAC;IACpB,0DAA0D;IAC1D,MAAM,CAAC,EAAE,MAAM,EAAE,CAAC;CACnB;AAED;;;;;;;GAOG;AACH,MAAM,WAAW,iBAAiB;IAChC,IAAI,EAAE,SAAS,CAAC;IAChB,mEAAmE;IACnE,eAAe,EAAE,MAAM,CAAC;IACxB,2DAA2D;IAC3D,SAAS,EAAE,MAAM,CAAC;IAClB,wDAAwD;IACxD,YAAY,EAAE,MAAM,CAAC;IACrB,sDAAsD;IACtD,eAAe,EAAE,MAAM,CAAC;IACxB,+DAA+D;IAC/D,iBAAiB,EAAE,MAAM,CAAC;IAC1B,OAAO,EACH;QACE,IAAI,EAAE,MAAM,CAAC;QACb,oEAAoE;QACpE,IAAI,EAAE,MAAM,CAAC;QACb,8DAA8D;QAC9D,MAAM,CAAC,EAAE;YAAE,IAAI,EAAE,SAAS,GAAG,MAAM,GAAG,OAAO,CAAC;YAAC,GAAG,EAAE,MAAM,CAAA;SAAE,CAAC;KAC9D,GACD;QACE,IAAI,EAAE,~~aAAa~~,CAAC;~~QACpB,kEAAkE~~;~~QAClE~~,~~kBAAkB~~,EAAE,MAAM,CAAC;~~KAC5B~~,CAAC;CACP;AAED;;;;GAIG;AACH,MAAM,WAAW,UAAU;IACzB,KAAK,EAAE,MAAM,CAAC;IACd,OAAO,EAAE,MAAM,CAAC;IAChB,SAAS,EAAE,MAAM,CAAC;IAClB,EAAE,EAAE,MAAM,CAAC;IACX,SAAS,EAAE,MAAM,EAAE,CAAC;IACpB,OAAO,CAAC,EAAE,MAAM,CAAC;CAClB"}
1	+ {"version":3,"file":"change-request-types.d.ts","sourceRoot":"","sources":["../../src/types/change-request-types.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,MAAM,WAAW,aAAa;IAC5B,OAAO,EAAE,UAAU,EAAE,CAAC;IACtB;;;OAGG;IACH,WAAW,EAAE,MAAM,EAAE,CAAC;IACtB;;;OAGG;IACH,gBAAgB,CAAC,EAAE,gBAAgB,CAAC;IACpC;;OAEG;IACH,OAAO,CAAC,EAAE,MAAM,CAAC;IACjB;;OAEG;IACH,UAAU,CAAC,EAAE,MAAM,CAAC;CACrB;AAED;;;GAGG;AACH,MAAM,WAAW,gBAAgB;IAC/B,gBAAgB,CAAC,EAAE,MAAM,CAAC;IAC1B,iBAAiB,CAAC,EAAE,MAAM,CAAC;CAC5B;AAED,MAAM,MAAM,UAAU,GAClB,eAAe,GACf,cAAc,GACd,iBAAiB,GACjB,cAAc,GACd,iBAAiB,CAAC;AAEtB,4DAA4D;AAC5D,MAAM,WAAW,eAAe;IAC9B,IAAI,EAAE,OAAO,CAAC;IACd,OAAO,EAAE,UAAU,CAAC;IACpB,QAAQ,EAAE,MAAM,CAAC;IACjB,IAAI,EAAE,MAAM,CAAC;IACb,EAAE,EAAE,MAAM,CAAC;CACZ;AAED,4DAA4D;AAC5D,MAAM,WAAW,cAAc;IAC7B,IAAI,EAAE,MAAM,CAAC;IACb,OAAO,EAAE,UAAU,CAAC;IACpB,IAAI,EAAE,MAAM,CAAC;IACb,EAAE,EAAE,MAAM,CAAC;CACZ;AAED;;;;GAIG;AACH,MAAM,WAAW,iBAAiB;IAChC,IAAI,EAAE,SAAS,CAAC;IAChB,OAAO,EAAE,UAAU,CAAC;IACpB,yDAAyD;IACzD,QAAQ,CAAC,EAAE,UAAU,EAAE,CAAC;IACxB,WAAW,EAAE,MAAM,CAAC;IACpB,8EAA8E;IAC9E,MAAM,CAAC,EAAE,MAAM,EAAE,CAAC;IAClB;;;;;OAKG;IACH,cAAc,CAAC,EAAE;QAAE,KAAK,EAAE,MAAM,CAAA;KAAE,CAAC;CACpC;AAED;;;GAGG;AACH,MAAM,WAAW,cAAc;IAC7B,IAAI,EAAE,MAAM,CAAC;IACb,WAAW,EAAE,MAAM,CAAC;IACpB,0DAA0D;IAC1D,MAAM,CAAC,EAAE,MAAM,EAAE,CAAC;CACnB;AAED;;;;;;;GAOG;AACH,MAAM,WAAW,iBAAiB;IAChC,IAAI,EAAE,SAAS,CAAC;IAChB,mEAAmE;IACnE,eAAe,EAAE,MAAM,CAAC;IACxB,2DAA2D;IAC3D,SAAS,EAAE,MAAM,CAAC;IAClB,wDAAwD;IACxD,YAAY,EAAE,MAAM,CAAC;IACrB,sDAAsD;IACtD,eAAe,EAAE,MAAM,CAAC;IACxB,+DAA+D;IAC/D,iBAAiB,EAAE,MAAM,CAAC;IAC1B,OAAO,EACH;QACE,IAAI,EAAE,MAAM,CAAC;QACb,oEAAoE;QACpE,IAAI,EAAE,MAAM,CAAC;QACb,8DAA8D;QAC9D,MAAM,CAAC,EAAE;YAAE,IAAI,EAAE,SAAS,GAAG,MAAM,GAAG,OAAO,CAAC;YAAC,GAAG,EAAE,MAAM,CAAA;SAAE,CAAC;KAC9D,GACD;QACE,IAAI,EAAE,iBAAiB,CAAC;QACxB;;;uCAG+B;QAC/B,IAAI,EAAE,MAAM,CAAC;KACd,CAAC;CACP;AAED;;;;GAIG;AACH,MAAM,WAAW,UAAU;IACzB,KAAK,EAAE,MAAM,CAAC;IACd,OAAO,EAAE,MAAM,CAAC;IAChB,SAAS,EAAE,MAAM,CAAC;IAClB,EAAE,EAAE,MAAM,CAAC;IACX,SAAS,EAAE,MAAM,EAAE,CAAC;IACpB,OAAO,CAAC,EAAE,MAAM,CAAC;CAClB"}

package/dist/utils/skills/claude-skill.d.ts CHANGED Viewed

@@ -1,5 +1,5 @@
-export declare const CLAUDE_SKILL_VERSION = 12;
+export declare const CLAUDE_SKILL_VERSION = 18;
 export declare const CLAUDE_SKILL_DIR = "rivet";
 export declare const CLAUDE_SKILL_FILENAME = "SKILL.md";
-export declare const CLAUDE_SKILL_CONTENT = "---\nname: rivet\ndescription: Rivet \u2014 two flows. Visual editor for point-and-click UI changes (\"open rivet\", \"use rivet\", \"make a visual change\"). Agent-variants for exploring N parallel design directions before committing (\"create variants of X\", \"show me 3-5 options for X\", \"build me a settings page from scratch\", \"create a new Vite todo app\", \"scaffold a Next.js dashboard\"). Pick the flow based on the user's request \u2014 see \"Picking the flow\" below.\n---\n\n[//]: # (rivet-skill-version: 12)\n# Rivet\n\nTwo flows: the **visual editor** (point-and-click changes to a running web app) and the **agent-variants flow** (explore N parallel design directions before committing).\n\n## Picking the flow\n\n| User says | Flow |\n|---|---|\n| \"open rivet\", \"make a visual change to X\" | **Visual editor** (below) |\n| \"create variants of X\", \"show me 3-5 options for X\", \"explore approaches to X\" | **Agent variants** |\n| \"build me a settings page from scratch\", \"add a feature for Y\" | **Agent variants** (no `target`) |\n| \"create a new Vite todo app\", \"scaffold a Next.js dashboard\" | **Agent variants** (`projectContext.kind=fresh`) |\n\n## Visual Editor flow\n\n## Starting a session\n\n1. Call `detect_project` \u2014 returns project info including `framework` and `projectPath`\n2. Call `open_visual_editor({ projectPath, framework })` \u2014 do NOT pass `startPort` or any port; the tool handles port selection automatically\n4. Tell the user: \"Rivet is ready \u2014 make your visual changes and click 'Send to Claude Code'.\"\n5. Start a background monitor to auto-detect when the user sends changes (see Monitoring below).\n6. You are now free to handle other requests while the monitor runs.\n\n## Monitoring for changes\n\nAfter opening the editor, start a Monitor to watch for changes. The `open_visual_editor` response includes `rivetPort` \u2014 use it:\n\n```\nMonitor:\n  description: \"Rivet changes\"\n  persistent: true\n  command: while sleep 2; do if curl -sf http://localhost:RIVET_PORT/api/mcp/status | grep -q '\"hasPendingIntent\":true'; then echo \"Rivet: user sent changes\"; exit 0; fi; done\n```\n\nReplace `RIVET_PORT` with the actual `rivetPort` from the `open_visual_editor` response.\n\nWhen the monitor notifies you, apply the changes (see below). After applying, **restart the monitor** to watch for the next round.\n\n## Applying changes\n\nWhen the monitor notifies you (or the user asks manually):\n\n1. Call `get_pending_changes({ sessionId })` to pick up queued changes\n2. If `hasChanges: false`, tell the user no changes are pending yet\n3. If `hasChanges: true`, apply the changes to the source files listed in `sourceFiles`\n4. Call `get_pending_changes({ sessionId, message: \"summary of changes\", refresh_git: true })` so the Rivet UI updates\n5. Hot reload happens automatically after file changes\n6. Tell the user what you changed\n7. Restart the monitor to watch for the next round\n\n## Ending a session\n\nWhen the user says they're done, call `close_visual_editor({ sessionId })`.\n\n## Rules\n\n- **Always call `detect_project` first** \u2014 never assume the dev server is running\n- **Never auto-commit** after applying visual changes \u2014 let the user decide\n- The dev server stays running after `close_visual_editor`\n\n---\n\n## Agent Variants flow\n\nFor requests like *\"create variants of X\"*, *\"show me 3-5 options for the dropdown\"*, *\"build me a settings page\"*, or *\"create a new Vite todo app\"* \u2014 DO NOT generate variants natively via the Task tool or parallel tool calls. Use this protocol so the user reviews design directions IN THIS CHAT, sees the actual code variants render in parallel, and picks based on the rendered code.\n\n### Step-by-step\n\n1. **Call `propose_variants`** with:\n   - `prompt`: the user's request verbatim\n   - `count`: 3-5 (default 4)\n   - `target` (optional): `{ type: 'element'|'file'|'route', ref }` \u2014 set this for refinement requests pinned to a specific element/file/route\n   - `projectContext` (optional):\n     - For brand-new projects: `{ kind: 'fresh', workspacePath: '/abs/path', framework: 'vite'|'next'|'astro'|'remix' }`\n     - Otherwise omit (defaults to existing project)\n\n   Response: `{ sessionId, briefWorkItem }`. The brief work item carries an `input` blob; you must run it next.\n\n2. **Run the brief work item using YOUR own LLM** \u2014 generate `count` design briefs as `{ briefId, label, body }`. Label is short (\u2264 4 words). Body is 1-2 sentences describing the design direction. Do NOT call any Rivet tool; this is your LLM doing creative work.\n\n3. **Call `report_variant_briefs`** with the briefs, plus the `workItemId` and `attempt: 0`.\n\n3.5. **Ensure the Rivet visual editor is open.** If you haven't already opened it in this session, call `detect_project` then `open_visual_editor({ projectPath, framework })` now \u2014 DON'T wait for the user to ask. The user will need the iframe open to see variants render. If a session is already active (`open_visual_editor` returns a friendly error), just continue. Once the editor opens, the chip at the bottom-center of the iframe will show generation progress.\n\n4. **Show the briefs to the user IN CHAT** as a numbered list. Ask \"Look good or want me to adjust any of them?\" \u2014 DO NOT ask which one to pick. The pick happens AFTER they've seen the actual code.\n   Example:\n   > Here are 4 directions:\n   > 1. **Spring blur** \u2014 Apple-style spring with ambient blur and soft edges\n   > 2. **Linear sharp** \u2014 Crisp, fast, minimal padding\n   > 3. **Notion soft** \u2014 Rounded, calm, neutral palette\n   > 4. **Monoline editorial** \u2014 Tight typography, single accent color\n   > Look good, or want me to adjust any of them?\n\n5. **Wait for the user's reply.** Affirmative (\"looks good\", \"go\", \"yep\") \u2192 proceed with all briefs. Tweak request (\"make #2 feel more like Linear\") \u2192 call `approve_variant_briefs` with `selections` containing `bodyOverride` per brief, OR re-run the brief work item with new framing. Reject all \u2192 call `cancel_variants` and start over.\n\n6. **Call `approve_variant_briefs({ sessionId, briefIds: [all chosen briefs] })`**. Response: `{ stage: 'work_items_ready', codeGenWorkItemIds: [...] }` \u2014 one work item per approved brief.\n\n7. **Lease the work** with `continue_variants({ sessionId, action: 'request_work' })`. Response has `leaseId`, `leaseTtlMs`, and `leasedWorkItems[]` \u2014 one per approved brief (plus a preceding `scaffold_base` for fresh-project; lease scaffold first, succeed it, then re-lease for the code-gens).\n\n8. **Run all leased code-gen items IN PARALLEL.** The preferred mechanism in Claude Code is to spawn one Task sub-agent per leased item in a single message \u2014 they execute concurrently. Each sub-agent:\n   - Reads `input.briefBody` and `input.target`\n   - Edits files in `input.worktreePath` (each variant has its own isolated worktree)\n   - Calls `report_variant_complete({ sessionId, workItemId, leaseId, attempt, status: 'succeeded' })` itself. On failure, status `'failed'` with error description.\n\n9. **When all variants are done (`stage: 'ready'` or `'degraded'`), tell the user the variants are ready and explain how to compare them.** Each variant has its own dev server running in an isolated worktree. The Rivet iframe shows a chip at the bottom-center: prev/label/next/check/dismiss. The user cycles between the live, running variants by clicking prev/next (the iframe re-mounts onto the variant's dev server in ~50ms via proxy retarget). When they like one, they click the check on the chip \u2014 that commits the variant.\n   Example reply:\n   > Variants are ready \u2014 open the Rivet preview and use the chip at the bottom of the iframe to cycle between them. Click the checkmark on the one you want and I'll apply it.\n\n   You do NOT need to print diffs in chat. The user picks visually in the iframe.\n\n10. **Watch for the user's pick.** Either:\n    a) Use `watch_for_changes({ sessionId })` (existing tool) which blocks until the user clicks the check on the chip, OR\n    b) Start a Monitor on `http://localhost:RIVET_PORT/api/mcp/status` like the visual-editor flow does.\n    When changes arrive, call `get_pending_changes({ sessionId })` and you'll see a `VariantChangeItem` in `changes[]`.\n\n11. **Apply the variant.** From the `VariantChangeItem` payload:\n    - `payload.kind === 'diff'` \u2192 `git apply` the unified diff against the user's project root\n    - `payload.kind === 'new-project'` \u2192 copy the contents of `payload.sourceWorktreePath` to `destinationPath`\n    Tell the user which variant you applied (use `variantLabel` from the change item).\n\n   You can also call `commit_variant({ sessionId, variantId })` yourself if the user expressed their pick in chat instead of clicking the chip (\"go with #2\", \"the spring one\") \u2014 same effect, just routed through the agent rather than the chip.\n\n### Rules\n\n- **Never** generate variants natively (Task sub-agents, parallel tool calls, your own creative process) without going through `propose_variants` first.\n- Always pass the user's prompt verbatim \u2014 don't paraphrase.\n- Briefs are shown as PLAIN TEXT in chat. Do not render UI, open a browser tab, or fabricate a URL.\n- The user picks AFTER seeing the variants render LIVE in the iframe, not before. Step 4 is \"look good or adjust the briefs?\"; step 9 hands off to the iframe chip for visual cycling + commit.\n- Don't dump diffs in chat by default. The iframe chip is the primary review surface. If the user explicitly asks \"show me the diffs\", then print them.\n- Step 8 (parallel code-gen) is the only step where you fan out \u2014 every other step is one tool call.\n- For fresh-project, `scaffold_base` runs first; only after it succeeds are the `code_gen` items leasable. Loop `continue_variants(action='request_work')` after each transition.\n";
+export declare const CLAUDE_SKILL_CONTENT: string;
 //# sourceMappingURL=claude-skill.d.ts.map

package/dist/utils/skills/claude-skill.d.ts.map CHANGED Viewed

	@@ -1 +1 @@
1	- {"version":3,"file":"claude-skill.d.ts","sourceRoot":"","sources":["../../../src/utils/skills/claude-skill.ts"],"names":[],"mappings":"~~AAAA~~,eAAO,MAAM,oBAAoB,KAAK,CAAC;AAGvC,eAAO,MAAM,gBAAgB,UAAU,CAAC;AACxC,eAAO,MAAM,qBAAqB,aAAa,CAAC;~~AAEhD~~,eAAO,MAAM,oBAAoB,~~oxTAyIhC~~,CAAC"}
1	+ {"version":3,"file":"claude-skill.d.ts","sourceRoot":"","sources":["../../../src/utils/skills/claude-skill.ts"],"names":[],"mappings":"AAKA,eAAO,MAAM,oBAAoB,KAAK,CAAC;AAGvC,eAAO,MAAM,gBAAgB,UAAU,CAAC;AACxC,eAAO,MAAM,qBAAqB,aAAa,CAAC;AAYhD,eAAO,MAAM,oBAAoB,QAgDhC,CAAC"}

package/dist/utils/skills/claude-skill.js CHANGED Viewed

@@ -1,10 +1,20 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.CLAUDE_SKILL_CONTENT = exports.CLAUDE_SKILL_FILENAME = exports.CLAUDE_SKILL_DIR = exports.CLAUDE_SKILL_VERSION = void 0;
-exports.CLAUDE_SKILL_VERSION = 12;
+const shared_variants_protocol_1 = require("./shared-variants-protocol");
+exports.CLAUDE_SKILL_VERSION = 18;
 const CLAUDE_SKILL_VERSION_MARKER = `[//]: # (rivet-skill-version: ${exports.CLAUDE_SKILL_VERSION})`;
 exports.CLAUDE_SKILL_DIR = 'rivet';
 exports.CLAUDE_SKILL_FILENAME = 'SKILL.md';
+const AGENT_VARIANTS_SECTION = (0, shared_variants_protocol_1.buildAgentVariantsSection)({
+    inChatEmphasis: 'IN THIS CHAT',
+    step9: `**Run all leased code-gen items IN PARALLEL.** The preferred mechanism in Claude Code is to spawn one Task sub-agent per leased item in a single message — they execute concurrently. Each sub-agent:
+   - Reads \`input.briefBody\` and \`input.target\`
+   - Edits files in \`input.worktreePath\` (each variant has its own isolated worktree)
+   - Calls \`report_variant_complete({ sessionId, workItemId, leaseId, attempt, status: 'succeeded' })\` itself. On failure, status \`'failed'\` with error description.`,
+    step11Suffix: `When changes arrive, call \`get_pending_changes({ sessionId })\` and you'll see a \`VariantChangeItem\` in \`changes[]\`.`,
+    nativeGenLabel: 'Task sub-agents',
+});
 exports.CLAUDE_SKILL_CONTENT = `---
 name: rivet
 description: Rivet — two flows. Visual editor for point-and-click UI changes ("open rivet", "use rivet", "make a visual change"). Agent-variants for exploring N parallel design directions before committing ("create variants of X", "show me 3-5 options for X", "build me a settings page from scratch", "create a new Vite todo app", "scaffold a Next.js dashboard"). Pick the flow based on the user's request — see "Picking the flow" below.
@@ -15,14 +25,7 @@ ${CLAUDE_SKILL_VERSION_MARKER}
 Two flows: the **visual editor** (point-and-click changes to a running web app) and the **agent-variants flow** (explore N parallel design directions before committing).
-## Picking the flow
-| User says | Flow |
-|---|---|
-| "open rivet", "make a visual change to X" | **Visual editor** (below) |
-| "create variants of X", "show me 3-5 options for X", "explore approaches to X" | **Agent variants** |
-| "build me a settings page from scratch", "add a feature for Y" | **Agent variants** (no \`target\`) |
-| "create a new Vite todo app", "scaffold a Next.js dashboard" | **Agent variants** (\`projectContext.kind=fresh\`) |
+${shared_variants_protocol_1.PICKING_THE_FLOW_TABLE}
 ## Visual Editor flow
@@ -30,28 +33,12 @@ Two flows: the **visual editor** (point-and-click changes to a running web app)
 1. Call \`detect_project\` — returns project info including \`framework\` and \`projectPath\`
 2. Call \`open_visual_editor({ projectPath, framework })\` — do NOT pass \`startPort\` or any port; the tool handles port selection automatically
-4. Tell the user: "Rivet is ready — make your visual changes and click 'Send to Claude Code'."
-5. Start a background monitor to auto-detect when the user sends changes (see Monitoring below).
-6. You are now free to handle other requests while the monitor runs.
-## Monitoring for changes
-After opening the editor, start a Monitor to watch for changes. The \`open_visual_editor\` response includes \`rivetPort\` — use it:
-\`\`\`
-Monitor:
-  description: "Rivet changes"
-  persistent: true
-  command: while sleep 2; do if curl -sf http://localhost:RIVET_PORT/api/mcp/status | grep -q '"hasPendingIntent":true'; then echo "Rivet: user sent changes"; exit 0; fi; done
-\`\`\`
-Replace \`RIVET_PORT\` with the actual \`rivetPort\` from the \`open_visual_editor\` response.
-When the monitor notifies you, apply the changes (see below). After applying, **restart the monitor** to watch for the next round.
+3. Tell the user: "Rivet is ready — make your visual changes and click 'Send to Claude Code'."
+4. Call \`watch_for_changes({ sessionId })\` to wait for the user's changes.
 ## Applying changes
-When the monitor notifies you (or the user asks manually):
+When \`watch_for_changes\` returns (or the user asks manually):
 1. Call \`get_pending_changes({ sessionId })\` to pick up queued changes
 2. If \`hasChanges: false\`, tell the user no changes are pending yet
@@ -59,7 +46,8 @@ When the monitor notifies you (or the user asks manually):
 4. Call \`get_pending_changes({ sessionId, message: "summary of changes", refresh_git: true })\` so the Rivet UI updates
 5. Hot reload happens automatically after file changes
 6. Tell the user what you changed
-7. Restart the monitor to watch for the next round
+7. **STOP and ask the user:** "Want me to keep watching for more Rivet changes, or go back to normal prompting?"
+8. If they want to keep watching, go back to step 1 in the "Applying changes" section
 ## Ending a session
@@ -68,79 +56,12 @@ When the user says they're done, call \`close_visual_editor({ sessionId })\`.
 ## Rules
 - **Always call \`detect_project\` first** — never assume the dev server is running
+- **Always use \`watch_for_changes\`** to wait for user changes — do NOT use Monitor, background shell commands, or manual polling
 - **Never auto-commit** after applying visual changes — let the user decide
 - The dev server stays running after \`close_visual_editor\`
 ---
-## Agent Variants flow
-For requests like *"create variants of X"*, *"show me 3-5 options for the dropdown"*, *"build me a settings page"*, or *"create a new Vite todo app"* — DO NOT generate variants natively via the Task tool or parallel tool calls. Use this protocol so the user reviews design directions IN THIS CHAT, sees the actual code variants render in parallel, and picks based on the rendered code.
-### Step-by-step
-1. **Call \`propose_variants\`** with:
-   - \`prompt\`: the user's request verbatim
-   - \`count\`: 3-5 (default 4)
-   - \`target\` (optional): \`{ type: 'element'|'file'|'route', ref }\` — set this for refinement requests pinned to a specific element/file/route
-   - \`projectContext\` (optional):
-     - For brand-new projects: \`{ kind: 'fresh', workspacePath: '/abs/path', framework: 'vite'|'next'|'astro'|'remix' }\`
-     - Otherwise omit (defaults to existing project)
-   Response: \`{ sessionId, briefWorkItem }\`. The brief work item carries an \`input\` blob; you must run it next.
-2. **Run the brief work item using YOUR own LLM** — generate \`count\` design briefs as \`{ briefId, label, body }\`. Label is short (≤ 4 words). Body is 1-2 sentences describing the design direction. Do NOT call any Rivet tool; this is your LLM doing creative work.
-3. **Call \`report_variant_briefs\`** with the briefs, plus the \`workItemId\` and \`attempt: 0\`.
-3.5. **Ensure the Rivet visual editor is open.** If you haven't already opened it in this session, call \`detect_project\` then \`open_visual_editor({ projectPath, framework })\` now — DON'T wait for the user to ask. The user will need the iframe open to see variants render. If a session is already active (\`open_visual_editor\` returns a friendly error), just continue. Once the editor opens, the chip at the bottom-center of the iframe will show generation progress.
-4. **Show the briefs to the user IN CHAT** as a numbered list. Ask "Look good or want me to adjust any of them?" — DO NOT ask which one to pick. The pick happens AFTER they've seen the actual code.
-   Example:
-   > Here are 4 directions:
-   > 1. **Spring blur** — Apple-style spring with ambient blur and soft edges
-   > 2. **Linear sharp** — Crisp, fast, minimal padding
-   > 3. **Notion soft** — Rounded, calm, neutral palette
-   > 4. **Monoline editorial** — Tight typography, single accent color
-   > Look good, or want me to adjust any of them?
-5. **Wait for the user's reply.** Affirmative ("looks good", "go", "yep") → proceed with all briefs. Tweak request ("make #2 feel more like Linear") → call \`approve_variant_briefs\` with \`selections\` containing \`bodyOverride\` per brief, OR re-run the brief work item with new framing. Reject all → call \`cancel_variants\` and start over.
-6. **Call \`approve_variant_briefs({ sessionId, briefIds: [all chosen briefs] })\`**. Response: \`{ stage: 'work_items_ready', codeGenWorkItemIds: [...] }\` — one work item per approved brief.
-7. **Lease the work** with \`continue_variants({ sessionId, action: 'request_work' })\`. Response has \`leaseId\`, \`leaseTtlMs\`, and \`leasedWorkItems[]\` — one per approved brief (plus a preceding \`scaffold_base\` for fresh-project; lease scaffold first, succeed it, then re-lease for the code-gens).
-8. **Run all leased code-gen items IN PARALLEL.** The preferred mechanism in Claude Code is to spawn one Task sub-agent per leased item in a single message — they execute concurrently. Each sub-agent:
-   - Reads \`input.briefBody\` and \`input.target\`
-   - Edits files in \`input.worktreePath\` (each variant has its own isolated worktree)
-   - Calls \`report_variant_complete({ sessionId, workItemId, leaseId, attempt, status: 'succeeded' })\` itself. On failure, status \`'failed'\` with error description.
-9. **When all variants are done (\`stage: 'ready'\` or \`'degraded'\`), tell the user the variants are ready and explain how to compare them.** Each variant has its own dev server running in an isolated worktree. The Rivet iframe shows a chip at the bottom-center: prev/label/next/check/dismiss. The user cycles between the live, running variants by clicking prev/next (the iframe re-mounts onto the variant's dev server in ~50ms via proxy retarget). When they like one, they click the check on the chip — that commits the variant.
-   Example reply:
-   > Variants are ready — open the Rivet preview and use the chip at the bottom of the iframe to cycle between them. Click the checkmark on the one you want and I'll apply it.
-   You do NOT need to print diffs in chat. The user picks visually in the iframe.
-10. **Watch for the user's pick.** Either:
-    a) Use \`watch_for_changes({ sessionId })\` (existing tool) which blocks until the user clicks the check on the chip, OR
-    b) Start a Monitor on \`http://localhost:RIVET_PORT/api/mcp/status\` like the visual-editor flow does.
-    When changes arrive, call \`get_pending_changes({ sessionId })\` and you'll see a \`VariantChangeItem\` in \`changes[]\`.
-11. **Apply the variant.** From the \`VariantChangeItem\` payload:
-    - \`payload.kind === 'diff'\` → \`git apply\` the unified diff against the user's project root
-    - \`payload.kind === 'new-project'\` → copy the contents of \`payload.sourceWorktreePath\` to \`destinationPath\`
-    Tell the user which variant you applied (use \`variantLabel\` from the change item).
-   You can also call \`commit_variant({ sessionId, variantId })\` yourself if the user expressed their pick in chat instead of clicking the chip ("go with #2", "the spring one") — same effect, just routed through the agent rather than the chip.
-### Rules
-- **Never** generate variants natively (Task sub-agents, parallel tool calls, your own creative process) without going through \`propose_variants\` first.
-- Always pass the user's prompt verbatim — don't paraphrase.
-- Briefs are shown as PLAIN TEXT in chat. Do not render UI, open a browser tab, or fabricate a URL.
-- The user picks AFTER seeing the variants render LIVE in the iframe, not before. Step 4 is "look good or adjust the briefs?"; step 9 hands off to the iframe chip for visual cycling + commit.
-- Don't dump diffs in chat by default. The iframe chip is the primary review surface. If the user explicitly asks "show me the diffs", then print them.
-- Step 8 (parallel code-gen) is the only step where you fan out — every other step is one tool call.
-- For fresh-project, \`scaffold_base\` runs first; only after it succeeds are the \`code_gen\` items leasable. Loop \`continue_variants(action='request_work')\` after each transition.
+${AGENT_VARIANTS_SECTION}
 `;
 //# sourceMappingURL=claude-skill.js.map

package/dist/utils/skills/claude-skill.js.map CHANGED Viewed

	@@ -1 +1 @@
1	- {"version":3,"file":"claude-skill.js","sourceRoot":"","sources":["../../../src/utils/skills/claude-skill.ts"],"names":[],"mappings":";;;~~AAAa~~,QAAA,oBAAoB,GAAG,EAAE,CAAC;AACvC,MAAM,2BAA2B,GAAG,iCAAiC,4BAAoB,GAAG,CAAC;AAEhF,QAAA,gBAAgB,GAAG,OAAO,CAAC;AAC3B,QAAA,qBAAqB,GAAG,UAAU,CAAC;~~AAEnC~~,QAAA,oBAAoB,GAAG;;;;;EAKlC,2BAA2B~~;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAoI5B~~,CAAC"}
1	+ {"version":3,"file":"claude-skill.js","sourceRoot":"","sources":["../../../src/utils/skills/claude-skill.ts"],"names":[],"mappings":";;;AAAA,yEAGoC;AAEvB,QAAA,oBAAoB,GAAG,EAAE,CAAC;AACvC,MAAM,2BAA2B,GAAG,iCAAiC,4BAAoB,GAAG,CAAC;AAEhF,QAAA,gBAAgB,GAAG,OAAO,CAAC;AAC3B,QAAA,qBAAqB,GAAG,UAAU,CAAC;AAEhD,MAAM,sBAAsB,GAAG,IAAA,oDAAyB,EAAC;IACvD,cAAc,EAAE,cAAc;IAC9B,KAAK,EAAE;;;yKAGgK;IACvK,YAAY,EAAE,2HAA2H;IACzI,cAAc,EAAE,iBAAiB;CAClC,CAAC,CAAC;AAEU,QAAA,oBAAoB,GAAG;;;;;EAKlC,2BAA2B;;;;;EAK3B,iDAAsB;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;EAqCtB,sBAAsB;CACvB,CAAC"}

package/dist/utils/skills/cursor-rules.d.ts CHANGED Viewed

@@ -1,4 +1,4 @@
-export declare const CURSOR_RULES_VERSION = 12;
+export declare const CURSOR_RULES_VERSION = 18;
 export declare const CURSOR_RULES_FILENAME = "rivet.mdc";
-export declare const CURSOR_RULES_CONTENT = "---\ndescription: Rivet \u2014 apply when the user says \"open rivet\", \"open the visual editor\", \"create variants\", \"show me options for X\", \"build me X from scratch\", \"create a new Y app\", or wants to make visual/UI changes or explore design directions\nalwaysApply: false\n---\n<!-- rivet-rules-version: 12 -->\n# Rivet\n\nTwo flows: the **visual editor** (point-and-click changes to a running web app) and the **agent-variants flow** (explore N parallel design directions before committing).\n\n> Tip: type `@rivet.mdc` in chat to invoke this rule manually.\n\n## Picking the flow\n\n| User says | Flow |\n|---|---|\n| \"open rivet\", \"make a visual change to X\" | **Visual editor** (below) |\n| \"create variants of X\", \"show me 3-5 options for X\", \"explore approaches to X\" | **Agent variants** |\n| \"build me a settings page from scratch\", \"add a feature for Y\" | **Agent variants** (no `target`) |\n| \"create a new Vite todo app\", \"scaffold a Next.js dashboard\" | **Agent variants** (`projectContext.kind=fresh`) |\n\n## Visual Editor flow\n\n## Starting a session\n\n1. Call `detect_project` \u2014 returns project info including `framework` and `projectPath`\n2. Call `open_visual_editor({ projectPath, framework })` \u2014 do NOT pass `startPort` or any port; the tool handles port selection automatically\n4. Tell the user: \"Rivet is ready \u2014 make your visual changes and click 'Send to Cursor'.\"\n5. Call `watch_for_changes({ sessionId })` to wait for the user's changes.\n\n## Watching and applying\n\n1. Call `watch_for_changes({ sessionId })` \u2014 blocks until the user clicks \"Send to Cursor\"\n2. If it times out (`hasChanges: false`), call it again to keep waiting\n3. When `hasChanges: true`, apply the changes to the source files listed in `sourceFiles`\n4. Call `get_pending_changes({ sessionId, message: \"summary of changes\", refresh_git: true })` so the Rivet UI updates\n5. Hot reload happens automatically after file changes\n6. Tell the user what you changed\n7. **STOP and ask the user:** \"Want me to keep watching for more Rivet changes, or go back to normal prompting?\"\n8. If they want to keep watching, go back to step 1\n\n## Ending a session\n\nWhen the user says they're done, call `close_visual_editor({ sessionId })`.\n\n## Rules\n\n- **Always call `detect_project` first** \u2014 never assume the dev server is running\n- **Always use `watch_for_changes`** to wait for user changes \u2014 do NOT use Monitor, background shell commands, or manual polling\n- **Never auto-commit** after applying visual changes \u2014 let the user decide\n- Always stop and ask before re-entering the watch loop\n- The dev server stays running after `close_visual_editor`\n\n---\n\n## Agent Variants flow\n\nFor requests like *\"create variants of X\"*, *\"show me 3-5 options for the dropdown\"*, *\"build me a settings page\"*, or *\"create a new Vite todo app\"* \u2014 DO NOT generate variants natively via parallel tool calls. Use this protocol so the user reviews design directions in chat, sees the actual code variants render in parallel, and picks based on the rendered code.\n\n### Step-by-step\n\n1. **Call `propose_variants`** with:\n   - `prompt`: the user's request verbatim\n   - `count`: 3-5 (default 4)\n   - `target` (optional): `{ type: 'element'|'file'|'route', ref }` \u2014 set this for refinement requests pinned to a specific element/file/route\n   - `projectContext` (optional):\n     - For brand-new projects: `{ kind: 'fresh', workspacePath: '/abs/path', framework: 'vite'|'next'|'astro'|'remix' }`\n     - Otherwise omit (defaults to existing project)\n\n   Response: `{ sessionId, briefWorkItem }`. The brief work item carries an `input` blob; you must run it next.\n\n2. **Run the brief work item using YOUR own LLM** \u2014 generate `count` design briefs as `{ briefId, label, body }`. Label is short (\u2264 4 words). Body is 1-2 sentences describing the design direction. Do NOT call any Rivet tool; this is your LLM doing creative work.\n\n3. **Call `report_variant_briefs`** with the briefs, plus the `workItemId` and `attempt: 0`.\n\n3.5. **Ensure the Rivet visual editor is open.** If you haven't already opened it in this session, call `detect_project` then `open_visual_editor({ projectPath, framework })` now \u2014 DON'T wait for the user to ask. The user will need the iframe open to see variants render. If a session is already active (`open_visual_editor` returns a friendly error), just continue. Once the editor opens, the chip at the bottom-center of the iframe will show generation progress.\n\n4. **Show the briefs to the user IN CHAT** as a numbered list. Ask \"Look good or want me to adjust any of them?\" \u2014 DO NOT ask which one to pick. The pick happens AFTER they've seen the actual code.\n   Example:\n   > Here are 4 directions:\n   > 1. **Spring blur** \u2014 Apple-style spring with ambient blur and soft edges\n   > 2. **Linear sharp** \u2014 Crisp, fast, minimal padding\n   > 3. **Notion soft** \u2014 Rounded, calm, neutral palette\n   > 4. **Monoline editorial** \u2014 Tight typography, single accent color\n   > Look good, or want me to adjust any of them?\n\n5. **Wait for the user's reply.** Affirmative (\"looks good\", \"go\", \"yep\") \u2192 proceed with all briefs. Tweak request (\"make #2 feel more like Linear\") \u2192 call `approve_variant_briefs` with `selections` containing `bodyOverride` per brief, OR re-run the brief work item with new framing. Reject all \u2192 call `cancel_variants` and start over.\n\n6. **Call `approve_variant_briefs({ sessionId, briefIds: [all chosen briefs] })`**. Response: `{ stage: 'work_items_ready', codeGenWorkItemIds: [...] }` \u2014 one work item per approved brief.\n\n7. **Lease the work** with `continue_variants({ sessionId, action: 'request_work' })`. Response has `leaseId`, `leaseTtlMs`, and `leasedWorkItems[]` \u2014 one per approved brief (plus a preceding `scaffold_base` for fresh-project; lease scaffold first, succeed it, then re-lease for the code-gens).\n\n8. **Run all leased code-gen items IN PARALLEL** via parallel tool calls in a single response. For each:\n   - Read `input.briefBody` and `input.target`\n   - Edit files in `input.worktreePath` (each variant has its own isolated worktree)\n   - Call `report_variant_complete({ sessionId, workItemId, leaseId, attempt, status: 'succeeded' })`. On failure, status `'failed'` with error description.\n\n9. **When all variants are done (`stage: 'ready'` or `'degraded'`), tell the user the variants are ready and explain how to compare them.** Each variant has its own dev server running in an isolated worktree. The Rivet iframe shows a chip at the bottom-center: prev/label/next/check/dismiss. The user cycles between the live, running variants by clicking prev/next (the iframe re-mounts onto the variant's dev server in ~50ms via proxy retarget). When they like one, they click the check on the chip \u2014 that commits the variant.\n   Example reply:\n   > Variants are ready \u2014 open the Rivet preview and use the chip at the bottom of the iframe to cycle between them. Click the checkmark on the one you want and I'll apply it.\n\n   You do NOT need to print diffs in chat. The user picks visually in the iframe.\n\n10. **Watch for the user's pick.** Either:\n    a) Use `watch_for_changes({ sessionId })` (existing tool) which blocks until the user clicks the check on the chip, OR\n    b) Poll `get_pending_changes({ sessionId })` periodically.\n    When `hasChanges: true`, you'll see a `VariantChangeItem` in `changes[]`.\n\n11. **Apply the variant.** From the `VariantChangeItem` payload:\n    - `payload.kind === 'diff'` \u2192 `git apply` the unified diff against the user's project root\n    - `payload.kind === 'new-project'` \u2192 copy the contents of `payload.sourceWorktreePath` to `destinationPath`\n    Tell the user which variant you applied (use `variantLabel` from the change item).\n\n   You can also call `commit_variant({ sessionId, variantId })` yourself if the user expressed their pick in chat instead of clicking the chip (\"go with #2\", \"the spring one\") \u2014 same effect, just routed through the agent rather than the chip.\n\n### Rules\n\n- **Never** generate variants natively (Task tool, parallel tool calls, your own creative process) without going through `propose_variants` first.\n- Always pass the user's prompt verbatim \u2014 don't paraphrase.\n- Briefs are shown as PLAIN TEXT in chat. Do not render UI, open a browser tab, or fabricate a URL.\n- The user picks AFTER seeing the variants render LIVE in the iframe, not before. Step 4 is \"look good or adjust the briefs?\"; step 9 hands off to the iframe chip for visual cycling + commit.\n- Don't dump diffs in chat by default. The iframe chip is the primary review surface. If the user explicitly asks \"show me the diffs\", then print them.\n- Step 8 (parallel code-gen) is the only step where you fan out \u2014 every other step is one tool call.\n- For fresh-project, `scaffold_base` runs first; only after it succeeds are the `code_gen` items leasable. Loop `continue_variants(action='request_work')` after each transition.\n";
+export declare const CURSOR_RULES_CONTENT: string;
 //# sourceMappingURL=cursor-rules.d.ts.map

package/dist/utils/skills/cursor-rules.d.ts.map CHANGED Viewed

	@@ -1 +1 @@
1	- {"version":3,"file":"cursor-rules.d.ts","sourceRoot":"","sources":["../../../src/utils/skills/cursor-rules.ts"],"names":[],"mappings":"~~AAAA~~,eAAO,MAAM,oBAAoB,KAAK,CAAC;AACvC,eAAO,MAAM,qBAAqB,cAAc,CAAC;~~AAGjD~~,eAAO,MAAM,oBAAoB,~~g+RA2HhC~~,CAAC"}
1	+ {"version":3,"file":"cursor-rules.d.ts","sourceRoot":"","sources":["../../../src/utils/skills/cursor-rules.ts"],"names":[],"mappings":"AAKA,eAAO,MAAM,oBAAoB,KAAK,CAAC;AACvC,eAAO,MAAM,qBAAqB,cAAc,CAAC;AAajD,eAAO,MAAM,oBAAoB,QAgDhC,CAAC"}