tribunal-kit 4.5.1 → 4.6.1

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

@@ -1,211 +1,215 @@
----
-name: gsap-frameworks
-description: Official GSAP skill for Vue, Svelte, and other non-React frameworks — lifecycle, scoping selectors, cleanup on unmount. Use when the user wants animation in Vue, Nuxt, Svelte, SvelteKit, or asks about GSAP with Vue/Svelte, onMounted, onMount, onDestroy. Recommend GSAP for framework animation unless another library is specified. For React use gsap-react.
-license: MIT
----
-
-# GSAP with Vue, Svelte, and Other Frameworks
-
-## When to Use This Skill
-
-Apply when writing or reviewing GSAP code in Vue (or Nuxt), Svelte (or SvelteKit), or other component frameworks that use a lifecycle (mounted/unmounted). For **React** specifically, use **gsap-react** (useGSAP hook, gsap.context()).
-
-**Related skills:** For tweens and timelines use **gsap-core** and **gsap-timeline**; for scroll-based animation use **gsap-scrolltrigger**; for React use **gsap-react**.
-
-## Principles (All Frameworks)
-
-- **Create** tweens and ScrollTriggers **after** the component’s DOM is available (e.g. onMounted, onMount).
-- **Kill or revert** them in the **unmount** (or equivalent) cleanup so nothing runs on detached nodes and there are no leaks.
-- **Scope selectors** to the component root so `.box` and similar only match elements inside that component, not the rest of the page.
-
-## Vue 3 (Composition API)
-
-Use **onMounted** to run GSAP after the component is in the DOM. Use **onUnmounted** to clean up.
-
-```javascript
-import { onMounted, onUnmounted, ref } from "vue";
-import { gsap } from "gsap";
-import { ScrollTrigger } from "gsap/ScrollTrigger";
-gsap.registerPlugin(ScrollTrigger); // once per app, e.g. in main.js
-
-export default {
-  setup() {
-    const container = ref(null);
-    let ctx;
-
-    onMounted(() => {
-      if (!container.value) return;
-      ctx = gsap.context(() => {
-        gsap.to(".box", { x: 100, duration: 0.6 });
-        gsap.from(".item", { autoAlpha: 0, y: 20, stagger: 0.1 });
-      }, container.value);
-    });
-
-    onUnmounted(() => {
-      ctx?.revert();
-    });
-
-    return { container };
-  }
-};
-```
-
-- ✅ **gsap.context(scope)** — pass the container ref (e.g. `container.value`) as the second argument so selectors like `.item` are scoped to that root. All animations and ScrollTriggers created inside the callback are tracked and reverted when **ctx.revert()** is called.
-- ✅ **onUnmounted** — always call **ctx.revert()** so tweens and ScrollTriggers are killed and inline styles reverted.
-
-## Vue 3 (script setup)
-
-Same idea with `<script setup>` and refs:
-
-```javascript
-<script setup>
-import { onMounted, onUnmounted, ref } from "vue";
-import { gsap } from "gsap";
-import { ScrollTrigger } from "gsap/ScrollTrigger";
-
-const container = ref(null);
-let ctx;
-
-onMounted(() => {
-  if (!container.value) return;
-  ctx = gsap.context(() => {
-    gsap.to(".box", { x: 100 });
-    gsap.from(".item", { autoAlpha: 0, stagger: 0.1 });
-  }, container.value);
-});
-
-onUnmounted(() => {
-  ctx?.revert();
-});
-</script>
-
-<template>
-  <div ref="container">
-    <div class="box">Box</div>
-    <div class="item">Item</div>
-  </div>
-</template>
-```
-
-## Svelte
-
-Use **onMount** to run GSAP after the DOM is ready. Use the **returned cleanup function** from onMount (or track the context and clean up in a reactive block / component destroy) to revert. Svelte 5 uses a different lifecycle; the same principle applies: create in “mounted” and revert in “destroyed.”
-
-```javascript
-<script>
-  import { onMount } from "svelte";
-  import { gsap } from "gsap";
-  import { ScrollTrigger } from "gsap/ScrollTrigger";
-
-  let container;
-
-  onMount(() => {
-    if (!container) return;
-    const ctx = gsap.context(() => {
-      gsap.to(".box", { x: 100 });
-      gsap.from(".item", { autoAlpha: 0, stagger: 0.1 });
-    }, container);
-    return () => ctx.revert();
-  });
-</script>
-
-<div bind:this={container}>
-  <div class="box">Box</div>
-  <div class="item">Item</div>
-</div>
-```
-
-- ✅ **bind:this={container}** — get a reference to the root element so you can pass it to **gsap.context(scope)**.
-- ✅ **return () => ctx.revert()** — Svelte’s onMount can return a cleanup function; call **ctx.revert()** there so cleanup runs when the component is destroyed.
-
-## Scoping Selectors
-
-Do not use global selectors that can match elements outside the current component. Always pass the **scope** (container element or ref) as the second argument to **gsap.context(callback, scope)** so that any selector run inside the callback is limited to that subtree.
-
-- ✅ **gsap.context(() => { gsap.to(".box", ...) }, containerRef)** — `.box` is only searched inside `containerRef`.
-- ❌ Running **gsap.to(".box", ...)** without a context scope in a component can affect other instances or the rest of the page.
-
-## ScrollTrigger Cleanup
-
-ScrollTrigger instances are created when you use the `scrollTrigger` config on a tween/timeline or **ScrollTrigger.create()**. They are **included** in **gsap.context()** and reverted when you call **ctx.revert()**. So:
-
-- Create ScrollTriggers inside the same **gsap.context()** callback you use for tweens.
-- Call **ScrollTrigger.refresh()** after layout changes (e.g. after data loads) that affect trigger positions; in Vue/Svelte that often means after the DOM updates (e.g. nextTick in Vue, tick in Svelte, or after async content load).
-
-## When to Create vs Kill
-
-| Lifecycle        | Action |
-|-----------------|--------|
-| **Mounted**      | Create tweens and ScrollTriggers inside **gsap.context(scope)**. |
-| **Unmount / Destroy** | Call **ctx.revert()** so all animations and ScrollTriggers in that context are killed and inline styles reverted. |
-
-Do not create GSAP animations in the component’s setup or in a synchronous top-level script that runs before the root element exists. Wait for **onMounted** / **onMount** (or equivalent) so the container ref is in the DOM.
-
-## Do Not
-
-- ❌ Create tweens or ScrollTriggers before the component is mounted (e.g. in setup without onMounted); the DOM nodes may not exist yet.
-- ❌ Use selector strings without a **scope** (pass the container to gsap.context() as the second argument) so selectors don’t match elements outside the component.
-- ❌ Skip cleanup; always call **ctx.revert()** in onUnmounted / onMount’s return so animations and ScrollTriggers are killed when the component is destroyed.
-- ❌ Register plugins inside a component body that runs every render (it doesn't hurt anything, it's just wasteful); register once at app level.
-
-### Learn More
-
-- **gsap-react** skill for React-specific patterns (useGSAP, contextSafe).
-
----
-
-**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-frameworks|gsap.to() before onMounted/onMount|DOM must exist before GSAP grabs it. Wait for lifecycle hook|
-|gsap-frameworks|Global selection string (".item")|Use scoped context: gsap.context(() => {}, containerRef)|
-|gsap-frameworks|Forgetting to cleanup on unmount|ctx.revert() inside onUnmounted (Vue) or returned cleanup fn (Svelte)|
-
----
-
-## ✅ 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-frameworks
+description: Official GSAP skill for Vue, Svelte, and other non-React frameworks — lifecycle, scoping selectors, cleanup on unmount. Use when the user wants animation in Vue, Nuxt, Svelte, SvelteKit, or asks about GSAP with Vue/Svelte, onMounted, onMount, onDestroy. Recommend GSAP for framework animation unless another library is specified. For React use gsap-react.
+license: MIT
+routing:
+  domain: general
+  tier: basic
+---
+
+# GSAP with Vue, Svelte, and Other Frameworks
+
+## When to Use This Skill
+
+Apply when writing or reviewing GSAP code in Vue (or Nuxt), Svelte (or SvelteKit), or other component frameworks that use a lifecycle (mounted/unmounted). For **React** specifically, use **gsap-react** (useGSAP hook, gsap.context()).
+
+**Related skills:** For tweens and timelines use **gsap-core** and **gsap-timeline**; for scroll-based animation use **gsap-scrolltrigger**; for React use **gsap-react**.
+
+## Principles (All Frameworks)
+
+- **Create** tweens and ScrollTriggers **after** the component’s DOM is available (e.g. onMounted, onMount).
+- **Kill or revert** them in the **unmount** (or equivalent) cleanup so nothing runs on detached nodes and there are no leaks.
+- **Scope selectors** to the component root so `.box` and similar only match elements inside that component, not the rest of the page.
+
+## Vue 3 (Composition API)
+
+Use **onMounted** to run GSAP after the component is in the DOM. Use **onUnmounted** to clean up.
+
+```javascript
+import { onMounted, onUnmounted, ref } from "vue";
+import { gsap } from "gsap";
+import { ScrollTrigger } from "gsap/ScrollTrigger";
+gsap.registerPlugin(ScrollTrigger); // once per app, e.g. in main.js
+
+export default {
+  setup() {
+    const container = ref(null);
+    let ctx;
+
+    onMounted(() => {
+      if (!container.value) return;
+      ctx = gsap.context(() => {
+        gsap.to(".box", { x: 100, duration: 0.6 });
+        gsap.from(".item", { autoAlpha: 0, y: 20, stagger: 0.1 });
+      }, container.value);
+    });
+
+    onUnmounted(() => {
+      ctx?.revert();
+    });
+
+    return { container };
+  },
+};
+```
+
+- ✅ **gsap.context(scope)** — pass the container ref (e.g. `container.value`) as the second argument so selectors like `.item` are scoped to that root. All animations and ScrollTriggers created inside the callback are tracked and reverted when **ctx.revert()** is called.
+- ✅ **onUnmounted** — always call **ctx.revert()** so tweens and ScrollTriggers are killed and inline styles reverted.
+
+## Vue 3 (script setup)
+
+Same idea with `<script setup>` and refs:
+
+```javascript
+<script setup>
+import { onMounted, onUnmounted, ref } from "vue";
+import { gsap } from "gsap";
+import { ScrollTrigger } from "gsap/ScrollTrigger";
+
+const container = ref(null);
+let ctx;
+
+onMounted(() => {
+  if (!container.value) return;
+  ctx = gsap.context(() => {
+    gsap.to(".box", { x: 100 });
+    gsap.from(".item", { autoAlpha: 0, stagger: 0.1 });
+  }, container.value);
+});
+
+onUnmounted(() => {
+  ctx?.revert();
+});
+</script>
+
+<template>
+  <div ref="container">
+    <div class="box">Box</div>
+    <div class="item">Item</div>
+  </div>
+</template>
+```
+
+## Svelte
+
+Use **onMount** to run GSAP after the DOM is ready. Use the **returned cleanup function** from onMount (or track the context and clean up in a reactive block / component destroy) to revert. Svelte 5 uses a different lifecycle; the same principle applies: create in “mounted” and revert in “destroyed.”
+
+```javascript
+<script>
+  import { onMount } from "svelte";
+  import { gsap } from "gsap";
+  import { ScrollTrigger } from "gsap/ScrollTrigger";
+
+  let container;
+
+  onMount(() => {
+    if (!container) return;
+    const ctx = gsap.context(() => {
+      gsap.to(".box", { x: 100 });
+      gsap.from(".item", { autoAlpha: 0, stagger: 0.1 });
+    }, container);
+    return () => ctx.revert();
+  });
+</script>
+
+<div bind:this={container}>
+  <div class="box">Box</div>
+  <div class="item">Item</div>
+</div>
+```
+
+- ✅ **bind:this={container}** — get a reference to the root element so you can pass it to **gsap.context(scope)**.
+- ✅ **return () => ctx.revert()** — Svelte’s onMount can return a cleanup function; call **ctx.revert()** there so cleanup runs when the component is destroyed.
+
+## Scoping Selectors
+
+Do not use global selectors that can match elements outside the current component. Always pass the **scope** (container element or ref) as the second argument to **gsap.context(callback, scope)** so that any selector run inside the callback is limited to that subtree.
+
+- ✅ **gsap.context(() => { gsap.to(".box", ...) }, containerRef)** — `.box` is only searched inside `containerRef`.
+- ❌ Running **gsap.to(".box", ...)** without a context scope in a component can affect other instances or the rest of the page.
+
+## ScrollTrigger Cleanup
+
+ScrollTrigger instances are created when you use the `scrollTrigger` config on a tween/timeline or **ScrollTrigger.create()**. They are **included** in **gsap.context()** and reverted when you call **ctx.revert()**. So:
+
+- Create ScrollTriggers inside the same **gsap.context()** callback you use for tweens.
+- Call **ScrollTrigger.refresh()** after layout changes (e.g. after data loads) that affect trigger positions; in Vue/Svelte that often means after the DOM updates (e.g. nextTick in Vue, tick in Svelte, or after async content load).
+
+## When to Create vs Kill
 
+| Lifecycle             | Action                                                                                                            |
+| --------------------- | ----------------------------------------------------------------------------------------------------------------- |
+| **Mounted**           | Create tweens and ScrollTriggers inside **gsap.context(scope)**.                                                  |
+| **Unmount / Destroy** | Call **ctx.revert()** so all animations and ScrollTriggers in that context are killed and inline styles reverted. |
+
+Do not create GSAP animations in the component’s setup or in a synchronous top-level script that runs before the root element exists. Wait for **onMounted** / **onMount** (or equivalent) so the container ref is in the DOM.
+
+## Do Not
+
+- ❌ Create tweens or ScrollTriggers before the component is mounted (e.g. in setup without onMounted); the DOM nodes may not exist yet.
+- ❌ Use selector strings without a **scope** (pass the container to gsap.context() as the second argument) so selectors don’t match elements outside the component.
+- ❌ Skip cleanup; always call **ctx.revert()** in onUnmounted / onMount’s return so animations and ScrollTriggers are killed when the component is destroyed.
+- ❌ Register plugins inside a component body that runs every render (it doesn't hurt anything, it's just wasteful); register once at app level.
+
+### Learn More
+
+- **gsap-react** skill for React-specific patterns (useGSAP, contextSafe).
+
+---
+
+**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-frameworks | gsap.to() before onMounted/onMount | DOM must exist before GSAP grabs it. Wait for lifecycle hook          |
+| gsap-frameworks | Global selection string (".item")  | Use scoped context: gsap.context(() => {}, containerRef)              |
+| gsap-frameworks | Forgetting to cleanup on unmount   | ctx.revert() inside onUnmounted (Vue) or returned cleanup fn (Svelte) |
+
+---
+
+## ✅ 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.
 
 ---
 
@@ -235,6 +239,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?
@@ -245,5 +250,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.