rivet-dev · jog1t · Jan 20, 2026
diff --git a/CLAUDE.md b/CLAUDE.md
@@ -193,3 +193,7 @@ Data structures often include:
 
 - Write comments as normal, complete sentences. Avoid fragmented structures with parentheticals and dashes like `// Spawn engine (if configured) - regardless of start kind`. Instead, write `// Spawn the engine if configured`. Especially avoid dashes (hyphens are OK).
 - Documenting deltas is not important or useful. A developer who has never worked on the project will not gain extra information if you add a comment stating that something was removed or changed because they don't know what was there before. The only time you would be adding a comment for something NOT being there is if its unintuitive for why its not there in the first place.
+
+### Examples
+
+- When adding new examples, or updating existing ones, ensure that the user also modified the vercel equivalent, if applicable. This ensures parity between local and vercel examples. In order to generate vercel example, run `./scripts/vercel-examples/generate-vercel-examples.ts ` after making changes to examples.
diff --git a/examples/CLAUDE.md b/examples/CLAUDE.md
diff --git a/examples/actor-actions-vercel/.gitignore b/examples/actor-actions-vercel/.gitignore
diff --git a/examples/actor-actions-vercel/README.md b/examples/actor-actions-vercel/README.md
diff --git a/examples/actor-actions-vercel/api/index.ts b/examples/actor-actions-vercel/api/index.ts