takomi 2.0.4 → 2.0.6

package/assets/.agent/skills/takomi/workflows/remotion-build.md

@@ -0,0 +1,323 @@
+---
+description: The Remotion Builder - Generate a detailed video spec, get approval, then build. Two-phase workflow for programmatic video creation.
+---
+
+# Remotion Builder Workflow
+
+> **Purpose**: Create programmatic videos using Remotion. This workflow forces mandatory rule reading, detailed planning, and an asset audit before any code is written.
+
+---
+
+## ⚠️ CRITICAL: MANDATORY RULE READING
+
+**YOU ARE NOT SMART ENOUGH TO GUESS REMOTION PATTERNS.**
+
+Before writing ANY Remotion code, you MUST read the relevant rule files. Do NOT proceed without reading these. Do NOT assume you know what you're doing.
+
+### Step 0.1: Read the Main Skill
+// turbo
+```bash
+cat ".agent/skills/remotion/SKILL.md"
+```
+
+### Step 0.2: Read REQUIRED Rule Files
+
+Based on what the video needs, you MUST read the corresponding rule files. This is NOT optional.
+
+**For ANY animation work (ALWAYS READ THESE):**
+// turbo
+```bash
+cat ".agent/skills/remotion/rules/animations.md"
+cat ".agent/skills/remotion/rules/timing.md"
+cat ".agent/skills/remotion/rules/sequencing.md"
+```
+
+**If using scene transitions:**
+// turbo
+```bash
+cat ".agent/skills/remotion/rules/transitions.md"
+```
+
+**If using text animations (typewriter, highlights, etc):**
+// turbo
+```bash
+cat ".agent/skills/remotion/rules/text-animations.md"
+cat ".agent/skills/remotion/rules/fonts.md"
+```
+
+**If using images, videos, or audio:**
+// turbo
+```bash
+cat ".agent/skills/remotion/rules/assets.md"
+cat ".agent/skills/remotion/rules/images.md"
+cat ".agent/skills/remotion/rules/videos.md"
+cat ".agent/skills/remotion/rules/audio.md"
+```
+
+**If using 3D elements:**
+// turbo
+```bash
+cat ".agent/skills/remotion/rules/3d.md"
+```
+
+**If using captions/subtitles:**
+// turbo
+```bash
+cat ".agent/skills/remotion/rules/display-captions.md"
+cat ".agent/skills/remotion/rules/transcribe-captions.md"
+```
+
+**If using charts/data visualization:**
+// turbo
+```bash
+cat ".agent/skills/remotion/rules/charts.md"
+```
+
+**If using Lottie animations:**
+// turbo
+```bash
+cat ".agent/skills/remotion/rules/lottie.md"
+```
+
+**If using GIFs:**
+// turbo
+```bash
+cat ".agent/skills/remotion/rules/gifs.md"
+```
+
+> ⛔ **DO NOT PROCEED TO PHASE 1 UNTIL YOU HAVE READ THE RELEVANT RULES.**
+
+---
+
+## PHASE 1: Video Specification
+
+Generate a **Video Spec Document** in `docs/remotion/[video_name]_spec.md`.
+
+### Step 1.1: Generate the Video Spec
+
+Create the spec with this structure:
+
+```markdown
+# 🎬 Video Spec: [Video Name]
+
+## Overview
+| Property | Value |
+|----------|-------|
+| **Type** | [Main/Short/B-Roll/Intro/Outro] |
+| **Duration** | [X seconds] (Y frames @ Zfps) |
+| **Resolution** | [WxH] |
+| **FPS** | 30 |
+| **Composition ID** | `[CompositionId]` |
+
+## Rules I Read Before Writing This Spec
+- [x] animations.md
+- [x] timing.md
+- [x] sequencing.md
+- [ ] transitions.md (if applicable)
+- [ ] text-animations.md (if applicable)
+- [ ] ... (list all rules you read)
+
+## Creative Direction
+[1-2 sentences describing the visual concept]
+
+### Color Palette
+| Color | Hex | Usage |
+|-------|-----|-------|
+| Primary | #XXXXXX | [usage] |
+
+### Typography
+| Font | Weight | Size | Usage |
+|------|--------|------|-------|
+| [Font Name] | [weight] | [px] | [usage] |
+
+---
+
+## Scene Breakdown
+
+### Scene 1: [Name] (0s - Xs)
+**Duration**: X seconds (Y frames)
+
+#### Visual Elements
+- [ ] Element 1: [Description]
+
+#### Animations (from timing.md / animations.md)
+| Element | Type | Start | End | Easing |
+|---------|------|-------|-----|--------|
+| [Element] | [fadeIn/spring/interpolate] | X | Y | [spring({damping:200}) / Easing.out(Easing.exp)] |
+
+#### Code Approach
+\```tsx
+// Frame-by-frame animation using useCurrentFrame() - NEVER CSS transitions
+const frame = useCurrentFrame();
+const opacity = interpolate(frame, [0, 30], [0, 1], { extrapolateRight: 'clamp' });
+\```
+
+---
+
+## Technical Requirements
+
+### Props Schema (Zod)
+\```ts
+import { z } from "zod";
+export const [Id]Schema = z.object({ ... });
+\```
+
+### Critical Rules (MEMORIZE THESE)
+> ⛔ FORBIDDEN: CSS transitions, CSS animations, Tailwind animation classes
+> ✅ REQUIRED: All animations via useCurrentFrame() + interpolate()/spring()
+> ✅ REQUIRED: premountFor={1 * fps} on all <Sequence> components
+> ✅ REQUIRED: staticFile() for public folder assets
+> ✅ REQUIRED: Clamp extrapolation to prevent values going beyond range
+```
+
+### Step 1.2: Request Approval
+
+Use `notify_user` with `BlockedOnUser: true` to request spec approval.
+
+---
+
+## PHASE 2: Asset Audit
+
+After spec approval, generate an **Asset Manifest**.
+
+### Step 2.1: Generate Asset Manifest
+
+Create `docs/remotion/[video_name]_assets.md`:
+
+```markdown
+# 🎨 Asset Manifest: [Video Name]
+
+## 1. Code-Generatable Components ✅
+*These can be built entirely with React/SVG code*
+
+| Component | Description | Complexity |
+|-----------|-------------|------------|
+| `ComponentName.tsx` | Description | Low/Medium/High |
+
+---
+
+## 2. Image Prompts for User 🖼️
+*I CANNOT generate these myself. I am providing prompts for YOU to generate.*
+
+> **Instructions for User:**
+> Use these prompts with your preferred image generation tool (Midjourney, DALL-E, generate_image tool, etc.)
+> After generating, save the images to `public/assets/[video_name]/`
+
+| Asset | Prompt | Size | Save As |
+|-------|--------|------|---------|
+| Background | "Abstract dark gradient with subtle grid pattern, cyberpunk aesthetic, 16:9 aspect ratio" | 1920x1080 | `bg_hero.png` |
+| Logo Icon | "Minimal geometric logo, neon cyan glow, dark background, icon style, square" | 512x512 | `logo.png` |
+
+**Total prompts**: X images for you to generate
+
+---
+
+## 3. External Assets Needed 📦
+*These require you to provide - stock footage, your logos, audio files*
+
+| Asset | Type | Description | Action |
+|-------|------|-------------|--------|
+| Your Logo | SVG/PNG | Your brand logo | You provide |
+| Background Music | MP3 | Ambient tech music | Source from [Epidemic Sound](https://epidemicsound.com) |
+| Screen Recording | MP4 | Demo of your app | You record |
+
+---
+
+## 4. Your Choices ⚡
+
+Tell me for each:
+
+| Item | Options |
+|------|---------|
+| UI Mockups | [ ] I'll build code components / [ ] I'll provide screenshots |
+| Background | [ ] Generate with prompt above / [ ] I'll provide my own |
+| Logo | [ ] Generate with prompt above / [ ] I'll provide my own |
+
+---
+
+## After You Decide
+
+**If you want me to proceed with code components:**
+Reply: "Build the components"
+
+**If you want to generate images first:**
+Run the prompts yourself, then reply: "Assets ready in public/assets/[folder]"
+
+**If you're providing your own assets:**
+Reply: "I'm providing: [list files] - they're in public/assets/[folder]"
+```
+
+### Step 2.2: Wait for User
+
+Use `notify_user` with `BlockedOnUser: true`. Do NOT proceed until user responds with their choices.
+
+---
+
+## PHASE 3: Component Building
+
+Only after user confirms assets OR chooses code-gen:
+
+### Step 3.1: Create Components
+
+For each component in the manifest:
+1. Re-read the relevant rule files (animations.md, timing.md, etc.)
+2. Create the component following patterns from the rules EXACTLY
+3. Use `useCurrentFrame()` for ALL animations
+4. NEVER use CSS transitions or Tailwind animation classes
+
+### Step 3.2: Create Main Composition
+
+1. Import all components
+2. Set up `<Sequence>` structure per the spec
+3. Add `premountFor={1 * fps}` to every Sequence
+4. Register in `Root.tsx`
+
+---
+
+## PHASE 4: Verification
+
+### Step 4.1: Start Studio
+// turbo
+```bash
+pnpm start
+```
+
+### Step 4.2: Manual Verification
+1. Open composition in browser
+2. Scrub through timeline
+3. Verify all animations trigger at correct frames
+4. Check console for errors
+
+---
+
+## Quick Reference (From Rules)
+
+### Interpolation (from timing.md)
+```tsx
+const opacity = interpolate(frame, [0, 30], [0, 1], {
+  extrapolateRight: 'clamp',
+  extrapolateLeft: 'clamp',
+});
+```
+
+### Spring (from timing.md)
+```tsx
+const scale = spring({
+  frame,
+  fps,
+  config: { damping: 200 }, // Smooth, no bounce
+});
+```
+
+### Sequence (from sequencing.md)
+```tsx
+<Sequence from={1 * fps} durationInFrames={2 * fps} premountFor={1 * fps}>
+  <MyComponent />
+</Sequence>
+```
+
+### Assets (from assets.md)
+```tsx
+import { Img, staticFile } from 'remotion';
+<Img src={staticFile('image.png')} />
+```

package/assets/.agent/skills/takomi/workflows/reverse_genesis.md

@@ -0,0 +1,132 @@
+---
+description: Onboard an AI to an existing codebase by generating an "Autopsy Report".
+---
+# Workflow: Reverse Genesis (Codebase Onboarding)
+
+**System Instruction:**
+This workflow is the OPPOSITE of `/init_vibecode_genesis`.
+Instead of planning a NEW project, you are **onboarding to an EXISTING codebase**.
+
+Your job is to generate a **Project Autopsy Report** — a comprehensive analysis of the current state of the code.
+
+---
+
+## Steps
+
+### 1. Reconnaissance (Auto-Scan)
+
+**A. Project Overview:**
+```bash
+cat README.md 2>/dev/null || echo "No README found"
+cat docs/Project_Requirements.md 2>/dev/null || echo "No PRD found"
+```
+
+**B. Tech Stack Detection:**
+```bash
+# Node/JS
+cat package.json 2>/dev/null | head -50
+# Python
+cat requirements.txt 2>/dev/null || cat pyproject.toml 2>/dev/null
+# Rust
+cat Cargo.toml 2>/dev/null
+```
+
+**C. Architecture Scan:**
+```bash
+# List top-level structure
+ls -la
+# List source structure
+find src -type f -name "*.ts" -o -name "*.py" -o -name "*.rs" 2>/dev/null | head -30
+```
+
+**D. Database Schema (if applicable):**
+```bash
+cat prisma/schema.prisma 2>/dev/null | head -100
+```
+
+**E. Recent Activity:**
+```bash
+git log --oneline -10
+```
+
+### 2. Generate Autopsy Report
+Create `docs/autopsy_report.md` with the following:
+
+```markdown
+# Project Autopsy Report
+
+**Generated:** [Current Date/Time]
+**Purpose:** Onboard a new AI Orchestrator to this existing codebase.
+
+---
+
+## 1. Project Elevator Pitch
+[One-sentence purpose of this application]
+
+## 2. Core Technology Stack
+| Category | Technology |
+| :--- | :--- |
+| Language | TypeScript / Python / etc. |
+| Framework | Next.js / FastAPI / etc. |
+| Database | PostgreSQL / SQLite / etc. |
+| Key Libraries | [List major dependencies] |
+
+## 3. Inferred Architecture
+[Describe the architectural pattern observed]
+- e.g., "Next.js App Router with Feature-Sliced Design"
+- e.g., "Modular Python with central event bus"
+
+## 4. Key Modules & Responsibilities
+| File/Module | Responsibility |
+| :--- | :--- |
+| `src/app/` | Next.js pages and routes |
+| `src/features/` | Domain-specific logic |
+| `src/lib/` | Shared utilities |
+
+## 5. Inferred Coding Conventions
+- **Naming:** snake_case / PascalCase / camelCase
+- **Components:** Server Components by default
+- **Validation:** Zod for all inputs
+- **Styling:** Tailwind CSS utility-first
+
+## 6. Entry Points
+- Main: `src/app/page.tsx` or `main.py`
+- API: `src/app/api/`
+
+## 7. Current State
+**Recent Commits:**
+[List from git log]
+
+**Open Issues:**
+[List from gh issue list]
+
+---
+
+## MISSION BRIEFING (For Orchestrator)
+
+You have now assimilated this codebase.
+
+**Your Directive:**
+1. Acknowledge you understand the existing architecture.
+2. Adopt the project's coding conventions.
+3. Ask the user: "What would you like to build or fix?"
+```
+
+### 3. Full File Embedding (Optional)
+If the project is complex, embed key files directly:
+- `src/lib/utils.ts`
+- Main config files
+- Core business logic
+
+### 4. Confirmation
+Tell the user:
+"🔬 **Autopsy Report Generated.**
+Saved to: `docs/autopsy_report.md`
+
+This report contains:
+- Tech stack analysis
+- Architecture breakdown
+- Coding conventions
+- Current state
+
+To onboard a new AI, paste this report into the new session."

package/assets/.agent/skills/takomi/workflows/review_code.md

@@ -0,0 +1,96 @@
+---
+description: Run the up-to-date J-Star review and audit loop for a change set.
+---
+
+# J-Star Review Workflow
+
+Use this workflow when the repository already has J-Star installed and you need to verify a change set.
+
+## Core Rule
+
+`review` and `audit` are separate steps.
+
+For a serious verification pass, run both.
+
+## 1. Build the Local Index
+
+If the repository is missing `.jstar/storage`, or if major files were added, run:
+
+```bash
+jstar init
+```
+
+## 2. Choose the Scope
+
+### Staged changes
+
+```bash
+git add .
+jstar review
+jstar audit
+```
+
+### Last commit
+
+```bash
+jstar review --last
+jstar audit --last
+```
+
+### Branch or PR scope
+
+```bash
+jstar review --pr
+jstar audit --pr
+```
+
+## 3. Read the Outputs
+
+Review outputs:
+- `.jstar/last-review.md`
+- `.jstar/session.json`
+
+Audit outputs:
+- `.jstar/audit_report.md`
+- `.jstar/audit_report.json`
+
+## 4. Fix Loop
+
+Agent instructions:
+1. Read both the review and audit outputs.
+2. Prioritize review `P0_CRITICAL` and `P1_HIGH` issues first.
+3. Prioritize audit `CRITICAL` and `HIGH` findings first.
+4. Apply fixes.
+5. Stage changes with `git add .`.
+6. Re-run both `review` and `audit` for the same scope.
+7. If only lower-priority review issues remain, stop when the remaining work is not worth another loop.
+8. Maximum loops: 3. If issues persist, stop and ask the user.
+
+## 5. False Positives and Debate
+
+For review findings that need challenge or adjudication:
+
+```bash
+jstar chat --headless
+```
+
+Headless commands:
+- `{"action":"list"}`
+- `{"action":"debate","issueId":0,"argument":"..."}`
+- `{"action":"ignore","issueId":0}`
+- `{"action":"accept","issueId":0}`
+- `{"action":"exit"}`
+
+For known deterministic audit false positives, use:
+- `.jstar/audit-ignore.json`
+
+## 6. Automation Mode
+
+Machine-readable review output:
+
+```bash
+jstar review --json > .jstar/last-review.json
+jstar audit --json > .jstar/audit_report.json
+```
+
+Use `review --json` and `audit --json` for automation. Do not rely on `review --headless`.

package/assets/.agent/skills/takomi/workflows/spawn-jstar-code-review.md

@@ -0,0 +1,161 @@
+---
+description: Install J-Star Reviewer in the current repository and set up the up-to-date review and audit flows.
+---
+
+# /spawn-jstar - Install J-Star Reviewer in This Repository
+
+Use this workflow to install the `jstar-reviewer` npm package and wire the repository for both code review and security audit.
+
+## Core Rule
+
+`review` and `audit` are separate steps.
+
+For a serious verification pass, run both. Do not present one as a substitute for the other.
+
+## Command Prefix
+
+Examples below use `jstar`.
+
+If you do not want a global install, replace `jstar` with `npx jstar-reviewer`.
+
+## 1. Prerequisites
+
+- Node.js 18+
+- Git repository
+- Gemini API key
+- Groq API key
+
+## 2. Install the CLI
+
+Preferred:
+
+```bash
+pnpm add -g jstar-reviewer
+```
+
+Fallback:
+
+```bash
+npm install -g jstar-reviewer
+```
+
+No global install:
+
+```bash
+npx jstar-reviewer --help
+```
+
+## 3. Set Up the Repository
+
+```bash
+jstar setup
+```
+
+This should create or update:
+- `.jstar/`
+- `.env.example`
+- `.gitignore`
+
+## 4. Create `.env.local`
+
+PowerShell:
+
+```powershell
+Copy-Item .env.example .env.local
+```
+
+POSIX shell:
+
+```bash
+cp .env.example .env.local
+```
+
+Required variables:
+
+```env
+GEMINI_API_KEY=your_gemini_key
+GROQ_API_KEY=your_groq_key
+```
+
+Optional but useful:
+
+```env
+GEMINI_EMBEDDING_MODEL=gemini-embedding-001
+REVIEW_MODEL_NAME=moonshotai/kimi-k2-instruct-0905
+```
+
+## 5. Build the Local Index
+
+```bash
+jstar init
+```
+
+If indexing fails with a Google 404 for the embedding model, set:
+
+```env
+GEMINI_EMBEDDING_MODEL=gemini-embedding-001
+```
+
+## 6. First Verification Pass
+
+### Option A: Interactive user flow
+
+```bash
+jstar review
+jstar audit
+```
+
+Use this when the user wants the normal CLI/TUI experience.
+
+### Option B: Agent automation flow
+
+```bash
+jstar review --json > .jstar/last-review.json
+jstar audit --json > .jstar/audit_report.json
+```
+
+Use this when an agent needs machine-readable output.
+
+### Option C: Review debate flow
+
+```bash
+jstar chat --headless
+```
+
+Headless commands:
+- `{"action":"list"}`
+- `{"action":"debate","issueId":0,"argument":"..."}`
+- `{"action":"ignore","issueId":0}`
+- `{"action":"accept","issueId":0}`
+- `{"action":"exit"}`
+
+## 7. Common Target Modes
+
+Staged changes:
+
+```bash
+jstar review
+jstar audit
+```
+
+Last commit:
+
+```bash
+jstar review --last
+jstar audit --last
+```
+
+Branch or PR scope:
+
+```bash
+jstar review --pr
+jstar audit --pr
+```
+
+## Outputs
+
+- `.jstar/last-review.md`
+- `.jstar/session.json`
+- `.jstar/audit_report.md`
+- `.jstar/audit_report.json`
+- `.jstar/audit-ignore.json`