tribunal-kit 4.5.1 → 4.6.1

package/.agent/skills/gsap-timeline/SKILL.md

@@ -1,165 +1,167 @@
----
-name: gsap-timeline
-description: Official GSAP skill for timelines — gsap.timeline(), position parameter, nesting, playback. Use when sequencing animations, choreographing keyframes, or when the user asks about animation sequencing, timelines, or animation order (in GSAP or when recommending a library that supports timelines).
-license: MIT
----
-
-# GSAP Timeline
-
-## When to Use This Skill
-
-Apply when building multi-step animations, coordinating several tweens in sequence or parallel, or when the user asks about timelines, sequencing, or keyframe-style animation in GSAP.
-
-**Related skills:** For single tweens and eases use **gsap-core**; for scroll-driven timelines use **gsap-scrolltrigger**; for React use **gsap-react**.
-
-## Creating a Timeline
-
-```javascript
-const tl = gsap.timeline();
-tl.to(".a", { x: 100, duration: 1 })
-  .to(".b", { y: 50, duration: 0.5 })
-  .to(".c", { opacity: 0, duration: 0.3 });
-```
-
-By default, tweens are **appended** one after another. Use the **position parameter** to place tweens at specific times or relative to other tweens.
-
-## Position Parameter
-
-Third argument (or position property in vars) controls placement:
-
-- **Absolute**: `1` — start at 1 second.
-- **Relative (default)**: `"+=0.5"` — 0.5s after end; `"-=0.2"` — 0.2s before end.
-- **Label**: `"labelName"` — at that label; `"labelName+=0.3"` — 0.3s after label.
-- **Placement**: `"<"` — start when recently-added animation starts; `">"` — start when recently-added animation ends (default); `"<0.2"` — 0.2s after recently-added animation start.
-
-Examples:
-
-```javascript
-tl.to(".a", { x: 100 }, 0);           // at 0
-tl.to(".b", { y: 50 }, "+=0.5");      // 0.5s after last end
-tl.to(".c", { opacity: 0 }, "<");     // same start as previous
-tl.to(".d", { scale: 2 }, "<0.2");    // 0.2s after previous start
-```
-
-## Timeline Defaults
-
-Pass defaults into the timeline so all child tweens inherit:
-
-```javascript
-const tl = gsap.timeline({ defaults: { duration: 0.5, ease: "power2.out" } });
-tl.to(".a", { x: 100 }).to(".b", { y: 50 }); // both use 0.5s and power2.out
-```
-
-## Timeline Options (constructor)
-
-- **paused: true** — create paused; call `.play()` to start.
-- **repeat**, **yoyo** — same as tweens; apply to whole timeline.
-- **onComplete**, **onStart**, **onUpdate** — timeline-level callbacks.
-- **defaults** — vars merged into every child tween.
-
-## Labels
-
-Add and use labels for readable, maintainable sequencing:
-
-```javascript
-tl.addLabel("intro", 0);
-tl.to(".a", { x: 100 }, "intro");
-tl.addLabel("outro", "+=0.5");
-tl.to(".b", { opacity: 0 }, "outro");
-tl.play("outro");  // start from "outro"
-tl.tweenFromTo("intro", "outro"); // pauses the timeline and returns a new Tween that animates the timeline's playhead from intro to outro with no ease.
-```
-
-## Nesting Timelines
-
-Timelines can contain other timelines.
-
-```javascript
-const master = gsap.timeline();
-const child = gsap.timeline();
-child.to(".a", { x: 100 }).to(".b", { y: 50 });
-master.add(child, 0);
-master.to(".c", { opacity: 0 }, "+=0.2");
-```
-
-## Controlling Playback
-
-- **tl.play()** / **tl.pause()**
-- **tl.reverse()** / **tl.progress(1)** then **tl.reverse()**
-- **tl.restart()** — from start.
-- **tl.time(2)** — seek to 2 seconds.
-- **tl.progress(0.5)** — seek to 50%.
-- **tl.kill()** — kill timeline and (by default) its children.
-
-## Official GSAP Best practices
-
-- ✅ Prefer timelines for sequencing
-- ✅ Use the **position parameter** (third argument) to place tweens at specific times or relative to labels.
-- ✅ Add **labels** with `addLabel()` for readable, maintainable sequencing.
-- ✅ Pass **defaults** into the timeline constructor so child tweens inherit duration, ease, etc.
-- ✅ Put ScrollTrigger on the timeline (or top-level tween), not on tweens inside a timeline.
-
-## Do Not
-
-- ❌ Chain animations with **delay** when a **timeline** can sequence them; prefer `gsap.timeline()` and the position parameter for multi-step animation.
-- ❌ Forget to pass **defaults** (e.g. `defaults: { duration: 0.5, ease: "power2.out" }`) when many child tweens share the same duration or ease.
-- ❌ Forget that **duration** on the timeline constructor is not the same as tween duration; timeline “duration” is determined by its children.
-- ❌ Nest animations that contain a ScrollTrigger; ScrollTriggers should only be on top-level Tweens/Timelines.
-
----
-
-**Slash command: `/review` or `/tribunal-full`**
-**Active reviewers: `logic-reviewer` · `security-auditor`**
-
-### ❌ Forbidden AI Tropes
-
-1. **Blind Assumptions:** Never make an assumption without documenting it clearly with `// VERIFY: [reason]`.
-2. **Silent Degradation:** Catching and suppressing errors without logging or handling.
-3. **Context Amnesia:** Forgetting the user's constraints and offering generic advice instead of tailored solutions.
-
----
-
-## 🚨 LLM Trap Table
-
-|Pattern|What AI Does Wrong|What Is Actually Correct|
-|:---|:---|:---|
-|gsap-timeline|Position parameter as 2nd arg|Position parameter is the 3rd arg: tl.to(el, {x: 100}, "<")|
-|gsap-timeline|tl.add(gsap.to(...))|tl.to(...) (just chain the tween directly)|
-|gsap-timeline|Hardcoded delays (delay: 1)|Use position parameter (<, >, +=1) for relative timing|
-
----
-
-## ✅ Pre-Flight Self-Audit
-
-Before producing any output, verify:
-```
-✅ Did I read the actual files before making claims about them?
-✅ Did I verify all method names against official GSAP documentation?
-✅ Did I add // VERIFY: on any uncertain API calls?
-✅ Are all imports from packages that actually exist in package.json?
-✅ Did I test my logic with edge cases (null, empty, 0, max)?
-✅ Did I avoid generating code for more than one module at a time?
-✅ Am I working from evidence, not assumption?
-```
-
----
-
-## 🔁 VBC Protocol (Verify → Build → Confirm)
-
-```
-VERIFY:  Read the actual codebase before writing anything
-BUILD:   Generate the smallest meaningful unit of code
-CONFIRM: Verify the output is correct before presenting
-```
-
-
-## Pre-Flight Checklist
-- [ ] Have I reviewed the user's specific constraints and requests?
-- [ ] Have I checked the environment for relevant existing implementations?
-
-## VBC Protocol (Verification-Before-Completion)
-You MUST verify existing code signatures and variables before attempting to modify or call them. No hallucination is permitted.
+---
+name: gsap-timeline
+description: Official GSAP skill for timelines — gsap.timeline(), position parameter, nesting, playback. Use when sequencing animations, choreographing keyframes, or when the user asks about animation sequencing, timelines, or animation order (in GSAP or when recommending a library that supports timelines).
+license: MIT
+routing:
+  domain: general
+  tier: basic
+---
+
+# GSAP Timeline
+
+## When to Use This Skill
+
+Apply when building multi-step animations, coordinating several tweens in sequence or parallel, or when the user asks about timelines, sequencing, or keyframe-style animation in GSAP.
+
+**Related skills:** For single tweens and eases use **gsap-core**; for scroll-driven timelines use **gsap-scrolltrigger**; for React use **gsap-react**.
+
+## Creating a Timeline
+
+```javascript
+const tl = gsap.timeline();
+tl.to(".a", { x: 100, duration: 1 }).to(".b", { y: 50, duration: 0.5 }).to(".c", { opacity: 0, duration: 0.3 });
+```
+
+By default, tweens are **appended** one after another. Use the **position parameter** to place tweens at specific times or relative to other tweens.
+
+## Position Parameter
+
+Third argument (or position property in vars) controls placement:
+
+- **Absolute**: `1` — start at 1 second.
+- **Relative (default)**: `"+=0.5"` — 0.5s after end; `"-=0.2"` — 0.2s before end.
+- **Label**: `"labelName"` — at that label; `"labelName+=0.3"` — 0.3s after label.
+- **Placement**: `"<"` — start when recently-added animation starts; `">"` — start when recently-added animation ends (default); `"<0.2"` — 0.2s after recently-added animation start.
+
+Examples:
+
+```javascript
+tl.to(".a", { x: 100 }, 0); // at 0
+tl.to(".b", { y: 50 }, "+=0.5"); // 0.5s after last end
+tl.to(".c", { opacity: 0 }, "<"); // same start as previous
+tl.to(".d", { scale: 2 }, "<0.2"); // 0.2s after previous start
+```
+
+## Timeline Defaults
+
+Pass defaults into the timeline so all child tweens inherit:
+
+```javascript
+const tl = gsap.timeline({ defaults: { duration: 0.5, ease: "power2.out" } });
+tl.to(".a", { x: 100 }).to(".b", { y: 50 }); // both use 0.5s and power2.out
+```
+
+## Timeline Options (constructor)
+
+- **paused: true** — create paused; call `.play()` to start.
+- **repeat**, **yoyo** — same as tweens; apply to whole timeline.
+- **onComplete**, **onStart**, **onUpdate** — timeline-level callbacks.
+- **defaults** — vars merged into every child tween.
+
+## Labels
+
+Add and use labels for readable, maintainable sequencing:
+
+```javascript
+tl.addLabel("intro", 0);
+tl.to(".a", { x: 100 }, "intro");
+tl.addLabel("outro", "+=0.5");
+tl.to(".b", { opacity: 0 }, "outro");
+tl.play("outro"); // start from "outro"
+tl.tweenFromTo("intro", "outro"); // pauses the timeline and returns a new Tween that animates the timeline's playhead from intro to outro with no ease.
+```
+
+## Nesting Timelines
+
+Timelines can contain other timelines.
+
+```javascript
+const master = gsap.timeline();
+const child = gsap.timeline();
+child.to(".a", { x: 100 }).to(".b", { y: 50 });
+master.add(child, 0);
+master.to(".c", { opacity: 0 }, "+=0.2");
+```
+
+## Controlling Playback
+
+- **tl.play()** / **tl.pause()**
+- **tl.reverse()** / **tl.progress(1)** then **tl.reverse()**
+- **tl.restart()** — from start.
+- **tl.time(2)** — seek to 2 seconds.
+- **tl.progress(0.5)** — seek to 50%.
+- **tl.kill()** — kill timeline and (by default) its children.
+
+## Official GSAP Best practices
+
+- ✅ Prefer timelines for sequencing
+- ✅ Use the **position parameter** (third argument) to place tweens at specific times or relative to labels.
+- ✅ Add **labels** with `addLabel()` for readable, maintainable sequencing.
+- ✅ Pass **defaults** into the timeline constructor so child tweens inherit duration, ease, etc.
+- ✅ Put ScrollTrigger on the timeline (or top-level tween), not on tweens inside a timeline.
+
+## Do Not
 
+- ❌ Chain animations with **delay** when a **timeline** can sequence them; prefer `gsap.timeline()` and the position parameter for multi-step animation.
+- ❌ Forget to pass **defaults** (e.g. `defaults: { duration: 0.5, ease: "power2.out" }`) when many child tweens share the same duration or ease.
+- ❌ Forget that **duration** on the timeline constructor is not the same as tween duration; timeline “duration” is determined by its children.
+- ❌ Nest animations that contain a ScrollTrigger; ScrollTriggers should only be on top-level Tweens/Timelines.
+
+---
+
+**Slash command: `/review` or `/tribunal-full`**
+**Active reviewers: `logic-reviewer` · `security-auditor`**
+
+### ❌ Forbidden AI Tropes
+
+1. **Blind Assumptions:** Never make an assumption without documenting it clearly with `// VERIFY: [reason]`.
+2. **Silent Degradation:** Catching and suppressing errors without logging or handling.
+3. **Context Amnesia:** Forgetting the user's constraints and offering generic advice instead of tailored solutions.
+
+---
+
+## 🚨 LLM Trap Table
+
+| Pattern       | What AI Does Wrong            | What Is Actually Correct                                    |
+| :------------ | :---------------------------- | :---------------------------------------------------------- |
+| gsap-timeline | Position parameter as 2nd arg | Position parameter is the 3rd arg: tl.to(el, {x: 100}, "<") |
+| gsap-timeline | tl.add(gsap.to(...))          | tl.to(...) (just chain the tween directly)                  |
+| gsap-timeline | Hardcoded delays (delay: 1)   | Use position parameter (<, >, +=1) for relative timing      |
+
+---
+
+## ✅ Pre-Flight Self-Audit
+
+Before producing any output, verify:
+
+```
+✅ Did I read the actual files before making claims about them?
+✅ Did I verify all method names against official GSAP documentation?
+✅ Did I add // VERIFY: on any uncertain API calls?
+✅ Are all imports from packages that actually exist in package.json?
+✅ Did I test my logic with edge cases (null, empty, 0, max)?
+✅ Did I avoid generating code for more than one module at a time?
+✅ Am I working from evidence, not assumption?
+```
+
+---
+
+## 🔁 VBC Protocol (Verify → Build → Confirm)
+
+```
+VERIFY:  Read the actual codebase before writing anything
+BUILD:   Generate the smallest meaningful unit of code
+CONFIRM: Verify the output is correct before presenting
+```
+
+## Pre-Flight Checklist
+
+- [ ] Have I reviewed the user's specific constraints and requests?
+- [ ] Have I checked the environment for relevant existing implementations?
+
+## VBC Protocol (Verification-Before-Completion)
+
+You MUST verify existing code signatures and variables before attempting to modify or call them. No hallucination is permitted.
 
 ---
 
@@ -189,6 +191,7 @@ AI coding assistants often fall into specific bad habits when dealing with this
 ### ✅ Pre-Flight Self-Audit
 
 Review these questions before confirming output:
+
 ```
 ✅ Did I rely ONLY on real, verified tools and methods?
 ✅ Is this solution appropriately scoped to the user's constraints?
@@ -199,5 +202,6 @@ Review these questions before confirming output:
 ### 🛑 Verification-Before-Completion (VBC) Protocol
 
 **CRITICAL:** You must follow a strict "evidence-based closeout" state machine.
+
 - ❌ **Forbidden:** Declaring a task complete because the output "looks correct."
 - ✅ **Required:** You are explicitly forbidden from finalizing any task without providing **concrete evidence** (terminal output, passing tests, compile success, or equivalent proof) that your output works as intended.