internal: Add changeset instructions

Author: ntucker

CONTRIBUTING.md

@@ -34,6 +34,14 @@ If your idea requires design considerations, it's best to [start a discussion][4
 * Add tests for your feature. You should be able to look at other tests for
   examples. If you're unsure, don't hesitate to [open an issue][1] and ask!
 
+* Add a changeset for user-facing changes in published packages:
+  * Run `yarn changeset` from repo root (run it once per distinct change).
+  * Write **terse changelog text** (1–3 short lines); include only **minimal examples** if needed.
+  * For **breaking changes**, include a minimal migration example with:
+    * `#### before`
+    * `#### after`
+  * If multiple packages are affected in different ways, generate **separate changesets** for each respective change.
+
 * Submit your pull request!
 
 ## Support Requests

packages/.cursor/rules/general-instrudctions.mdc

@@ -0,0 +1,17 @@
+---
+alwaysApply: true
+---
+
+## Changesets (release notes)
+
+- **When to add**: Any user-facing change in a published package (`packages/*`) should include a changeset.
+- **Command**: Run `yarn changeset` from repo root (run it once per distinct change).
+- **Terse changelog text**:
+  - **Keep it short**: 1–3 short lines describing the outcome (not implementation details).
+  - **Minimal examples only**: If an example helps, prefer a tiny snippet (typically import + 1 call). Avoid long blocks.
+  - **Breaking changes**: Include a tiny migration example using:
+    - `#### before`
+    - `#### after`
+- **Split changesets by impact**:
+  - If **multiple packages are affected in different ways**, create **separate changesets** so each package’s changelog is focused.
+  - If the same change applies uniformly to multiple packages, a single changeset is fine.