docs(skills): switch entrance examples to gsap.fromTo()

transitions/overview.md rule #2 and gsap-easing-and-stagger.md stagger
examples used gsap.from({opacity: 0}), which contradicts the
"prefer fromTo() for entrances" guidance in gsap-timeline-and-labels.md,
motion-principles.md, and sub-compositions.md. The inconsistency teaches
agents the from() pattern, which becomes a 0→0 noop (all-black render)
when paired with CSS opacity: 0 — exactly the case PR #1001
adds an error-level lint rule for. Aligning all 5 skill files on fromTo().

Author: WaterrrForever

skills/hyperframes-animation/adapters/gsap-easing-and-stagger.md

@@ -38,26 +38,30 @@ Setting defaults at timeline scope is preferred — it documents the motion lang
 ## Stagger
 
 ```javascript
-gsap.from(".item", { y: 24, opacity: 0, duration: 0.5, stagger: 0.08 });
+gsap.fromTo(".item", { y: 24, opacity: 0 }, { y: 0, opacity: 1, duration: 0.5, stagger: 0.08 });
 ```
 
 Object form:
 
 ```javascript
-gsap.from(".item", {
-  y: 24,
-  opacity: 0,
-  stagger: {
-    each: 0.08, // delay between each
-    from: "center", // "start" | "end" | "center" | "edges" | "random" | index
-    amount: 0.6, // total stagger time (overrides each if both set)
-    grid: "auto", // for 2D stagger
-    axis: "x" | "y",
+gsap.fromTo(
+  ".item",
+  { y: 24, opacity: 0 },
+  {
+    y: 0,
+    opacity: 1,
+    stagger: {
+      each: 0.08, // delay between each
+      from: "center", // "start" | "end" | "center" | "edges" | "random" | index
+      amount: 0.6, // total stagger time (overrides each if both set)
+      grid: "auto", // for 2D stagger
+      axis: "x" | "y",
+    },
   },
-});
+);
 ```
 
-Prefer `stagger` over N separate tweens with manual delays — it stays correct when the target count or order changes.
+Prefer `stagger` over N separate tweens with manual delays — it stays correct when the target count or order changes. Use `fromTo()` rather than `from()` so the start state is explicit (see `gsap-timeline-and-labels.md` → sub-composition entrances).
 
 ## Function-Based Values
 

skills/hyperframes-animation/transitions/overview.md

@@ -19,7 +19,7 @@ A transition tells the viewer how two scenes relate. A crossfade says "this cont
 These are non-negotiable for every multi-scene composition:
 
 1. **Every composition uses transitions.** No exceptions. Scenes without transitions feel like jump cuts.
-2. **Every scene uses entrance animations.** Elements animate IN via `gsap.from()` — opacity, position, scale, etc. No scene should pop fully-formed onto screen.
+2. **Every scene uses entrance animations.** Elements animate IN — opacity, position, scale, etc. No scene should pop fully-formed onto screen. Use `gsap.fromTo()` (not `gsap.from()`) so the start state is explicit: `from()` animates _to_ current CSS, so pairing it with CSS `opacity: 0` is a 0→0 noop and the element never appears (see `/hyperframes-core` → sub-compositions).
 3. **Exit animations are BANNED** except on the final scene. Do NOT use `gsap.to()` to animate elements out before a transition fires. The transition IS the exit. Outgoing scene content must be fully visible when the transition starts — the transition handles the visual handoff.
 4. **Final scene exception:** The last scene MAY fade elements out (e.g., fade to black at the end of the composition). This is the only scene where exit animations are allowed.