creator-editing-studio 1.3.2 → 1.3.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "creator-editing-studio",
-  "version": "1.3.2",
+  "version": "1.3.3",
   "description": "Scaffolds a Creator Editing OS studio — components, scripts and rules for editing video from a plain-English brief.",
   "license": "UNLICENSED",
   "type": "module",

package/template/CLAUDE.md

@@ -134,6 +134,51 @@ The plan is there to save them a rebuild, not to put a form in front of them.
 The failure this is guarding against is a whole edit rendered the wrong way. Anything that does
 not risk that should move fast.
 
+## What makes motion read as expensive
+
+The twelve motion laws stop an edit looking broken. These seven are what separate motion that
+looks competent from motion that looks paid for. They were taken from studying reference edits
+frame by frame, and they apply to UI, graphics and footage alike.
+
+**1. Blur anything that moves fast.** In the edits that feel most expensive, nothing travels
+sharp. An element crossing the frame in six frames should be a smear that only resolves as it
+slows — and that includes digits rolling from one number to another, and a line redrawing on a
+chart. Sharp fast motion is the single clearest tell of cheap animation, because real cameras and
+real eyes do not work that way. Use the velocity blur helpers rather than deciding per element.
+
+**2. Morph, don't replace.** When something becomes something else, animate the thing itself
+rather than fading one out and another in. A row that is clicked and confirmed should stretch and
+turn into the confirmation; it should not be covered by a new element that happens to sit in the
+same place. An element that exists in two moments travels between them. This is the law that most
+reliably makes a sequence feel connected rather than assembled.
+
+**3. Overshoot, then settle.** Things that arrive exactly at their final size and stop look
+pasted on. Let an arrival come in slightly too large, or slightly past its mark, and ease back.
+The overshoot is small — a few per cent — and it is the difference between landing and being
+placed.
+
+**4. Animate the data, not the container.** When a value, a chart or a list changes, hold the
+frame still and change only what actually changed. Re-entering the whole panel to show a new
+number throws away the viewer's orientation and makes the change read as a new scene instead of
+an update.
+
+**5. Reveal one thing at a time.** Rows, cards, icons and bullets arrive in reading order with a
+few frames between them, never as a group. If a container also needs to grow, grow it slowly
+underneath while the contents arrive — two speeds, not one.
+
+**6. Earn the hard cut.** In a piece built from continuous motion, a single hard cut to a flat
+colour lands hard precisely because it is the only one. Bursts of hard cuts are their own beat
+and work too, but mixing the two at random wastes both. Decide which the piece is.
+
+**7. Show what is coming.** Small anticipations make an interface feel alive: text typing into a
+pill that grows with it, with the next word already faintly present; a cursor that starts moving
+before the thing it will click appears. The viewer reads intent, not just motion.
+
+A note on where these come from. Every one of them was found by studying an edit frame by frame
+and writing down what it actually did — not by reading about animation. When something looks good
+to you, save the clip and the timecode and do the same. That habit is worth more than any list,
+including this one.
+
 ## Verify the render before you call it done
 
 You have not seen the video. The timeline in your head is not evidence. Before you say an

package/template/scripts/refs.mjs

@@ -7,7 +7,7 @@
  *   npm run refs -- --all   redo every sheet
  *
  * Reads entries shaped like:
- *   ## 4. `farza.mp4` — Farza
+ *   ## 4. `clip-name.mp4` — Creator name
  *   - **00:11–00:14** — what happens...
  * Writes work/refs/<clip>-<mm.ss>-<mm.ss>.jpg and work/refs/INDEX.md (moment -> sheet), and lists
  * clips that are in the folder but have no entry yet, or entries whose clip is missing.

package/template/src/components/CommandCard.tsx

@@ -205,7 +205,7 @@ export const CONNECT_SEGMENTS: Segment[] = [
   {kind: 'plain', text: 'claude mcp add '},
   {kind: 'flag', text: '--scope user --transport http '},
   {kind: 'accent', text: 'creator-editing-os'},
-  {kind: 'plain', text: ' https://creator-editing-os.mahipal-231.workers.dev/mcp/'},
+  {kind: 'plain', text: ' <your connector URL>'},
   {kind: 'redacted', text: 'XXXX-XXXX-XXXX-XXXX'},
 ];