mirror of
https://github.com/affaan-m/everything-claude-code.git
synced 2026-04-09 02:43:29 +08:00
* fix(ci): resolve cross-platform test failures - Sanity check script (check-codex-global-state.sh) now falls back to grep -E when ripgrep is not available, fixing the codex-hooks sync test on all CI platforms. Patterns converted to POSIX ERE for portability. - Unicode safety test accepts both / and \ path separators so the executable-file assertion passes on Windows. - Gacha test sets PYTHONUTF8=1 so Python uses UTF-8 stdout encoding on Windows instead of cp1252, preventing UnicodeEncodeError on box-drawing characters. - Quoted-hook-path test skipped on Windows where NTFS disallows double-quote characters in filenames. * feat: port remotion-video-creation skill (29 rules), restore missing files New skill: - remotion-video-creation: 29 domain-specific Remotion rules covering 3D/Three.js, animations, audio, captions, charts, compositions, fonts, GIFs, Lottie, measuring, sequencing, tailwind, text animations, timing, transitions, trimming, and video embedding. Ported from personal skills. Restored: - autonomous-agent-harness/SKILL.md (was in commit but missing from worktree) - lead-intelligence/ (full directory restored from branch commit) Updated: - manifests/install-modules.json: added remotion-video-creation to media-generation - README.md + AGENTS.md: synced counts to 139 skills Catalog validates: 30 agents, 60 commands, 139 skills. * fix(security): pin MCP server versions, add dependabot, pin github-script SHA Critical: - Pin all npx -y MCP server packages to specific versions in .mcp.json to prevent supply chain attacks via version hijacking: - @modelcontextprotocol/server-github@2025.4.8 - @modelcontextprotocol/server-memory@2026.1.26 - @modelcontextprotocol/server-sequential-thinking@2025.12.18 - @playwright/mcp@0.0.69 (was 0.0.68) Medium: - Add .github/dependabot.yml for weekly npm + github-actions updates with grouped minor/patch PRs - Pin actions/github-script to SHA (was @v7 tag, now pinned to commit) * feat: add social-graph-ranker skill — weighted network proximity scoring New skill: social-graph-ranker - Weighted social graph traversal with exponential decay across hops - Bridge Score: B(m) = Σ w(t) · λ^(d(m,t)-1) ranks mutuals by target proximity - Extended Score incorporates 2nd-order network (mutual-of-mutual connections) - Final ranking includes engagement bonus for responsive connections - Runs in parallel with lead-intelligence skill for combined warm+cold outreach - Supports X API + LinkedIn CSV for graph harvesting - Outputs tiered action list: warm intros, direct outreach, network gap analysis Added to business-content install module. Catalog validates: 30/60/140. * fix(security): npm audit fix — resolve all dependency vulnerabilities Applied npm audit fix --force to resolve: - minimatch ReDoS (3 vulnerabilities, HIGH) - smol-toml DoS (MODERATE) - brace-expansion memory exhaustion (MODERATE) - markdownlint-cli upgraded from 0.47.0 to 0.48.0 npm audit now reports 0 vulnerabilities. * fix: resolve markdown lint and yarn lockfile sync - MD047: ensure single trailing newline on all remotion rule files - MD012: remove consecutive blank lines in lottie, measuring-dom-nodes, trimming - MD034: wrap bare URLs in angle brackets (tailwind, transcribe-captions) - yarn.lock: regenerated to sync with npm audit changes in package.json * fix: replace unicode arrows in lead-intelligence (CI unicode safety check)
123 lines
3.6 KiB
Markdown
123 lines
3.6 KiB
Markdown
---
|
|
name: transitions
|
|
description: Fullscreen scene transitions for Remotion.
|
|
metadata:
|
|
tags: transitions, fade, slide, wipe, scenes
|
|
---
|
|
|
|
## Fullscreen transitions
|
|
|
|
Using `<TransitionSeries>` to animate between multiple scenes or clips.
|
|
This will absolutely position the children.
|
|
|
|
## Prerequisites
|
|
|
|
First, the @remotion/transitions package needs to be installed.
|
|
If it is not, use the following command:
|
|
|
|
```bash
|
|
npx remotion add @remotion/transitions # If project uses npm
|
|
bunx remotion add @remotion/transitions # If project uses bun
|
|
yarn remotion add @remotion/transitions # If project uses yarn
|
|
pnpm exec remotion add @remotion/transitions # If project uses pnpm
|
|
```
|
|
|
|
## Example usage
|
|
|
|
```tsx
|
|
import {TransitionSeries, linearTiming} from '@remotion/transitions';
|
|
import {fade} from '@remotion/transitions/fade';
|
|
|
|
<TransitionSeries>
|
|
<TransitionSeries.Sequence durationInFrames={60}>
|
|
<SceneA />
|
|
</TransitionSeries.Sequence>
|
|
<TransitionSeries.Transition presentation={fade()} timing={linearTiming({durationInFrames: 15})} />
|
|
<TransitionSeries.Sequence durationInFrames={60}>
|
|
<SceneB />
|
|
</TransitionSeries.Sequence>
|
|
</TransitionSeries>;
|
|
```
|
|
|
|
## Available Transition Types
|
|
|
|
Import transitions from their respective modules:
|
|
|
|
```tsx
|
|
import {fade} from '@remotion/transitions/fade';
|
|
import {slide} from '@remotion/transitions/slide';
|
|
import {wipe} from '@remotion/transitions/wipe';
|
|
import {flip} from '@remotion/transitions/flip';
|
|
import {clockWipe} from '@remotion/transitions/clock-wipe';
|
|
```
|
|
|
|
## Slide Transition with Direction
|
|
|
|
Specify slide direction for enter/exit animations.
|
|
|
|
```tsx
|
|
import {slide} from '@remotion/transitions/slide';
|
|
|
|
<TransitionSeries.Transition presentation={slide({direction: 'from-left'})} timing={linearTiming({durationInFrames: 20})} />;
|
|
```
|
|
|
|
Directions: `"from-left"`, `"from-right"`, `"from-top"`, `"from-bottom"`
|
|
|
|
## Timing Options
|
|
|
|
```tsx
|
|
import {linearTiming, springTiming} from '@remotion/transitions';
|
|
|
|
// Linear timing - constant speed
|
|
linearTiming({durationInFrames: 20});
|
|
|
|
// Spring timing - organic motion
|
|
springTiming({config: {damping: 200}, durationInFrames: 25});
|
|
```
|
|
|
|
## Duration calculation
|
|
|
|
Transitions overlap adjacent scenes, so the total composition length is **shorter** than the sum of all sequence durations.
|
|
|
|
For example, with two 60-frame sequences and a 15-frame transition:
|
|
|
|
- Without transitions: `60 + 60 = 120` frames
|
|
- With transition: `60 + 60 - 15 = 105` frames
|
|
|
|
The transition duration is subtracted because both scenes play simultaneously during the transition.
|
|
|
|
### Getting the duration of a transition
|
|
|
|
Use the `getDurationInFrames()` method on the timing object:
|
|
|
|
```tsx
|
|
import {linearTiming, springTiming} from '@remotion/transitions';
|
|
|
|
const linearDuration = linearTiming({durationInFrames: 20}).getDurationInFrames({fps: 30});
|
|
// Returns 20
|
|
|
|
const springDuration = springTiming({config: {damping: 200}}).getDurationInFrames({fps: 30});
|
|
// Returns calculated duration based on spring physics
|
|
```
|
|
|
|
For `springTiming` without an explicit `durationInFrames`, the duration depends on `fps` because it calculates when the spring animation settles.
|
|
|
|
### Calculating total composition duration
|
|
|
|
```tsx
|
|
import {linearTiming} from '@remotion/transitions';
|
|
|
|
const scene1Duration = 60;
|
|
const scene2Duration = 60;
|
|
const scene3Duration = 60;
|
|
|
|
const timing1 = linearTiming({durationInFrames: 15});
|
|
const timing2 = linearTiming({durationInFrames: 20});
|
|
|
|
const transition1Duration = timing1.getDurationInFrames({fps: 30});
|
|
const transition2Duration = timing2.getDurationInFrames({fps: 30});
|
|
|
|
const totalDuration = scene1Duration + scene2Duration + scene3Duration - transition1Duration - transition2Duration;
|
|
// 60 + 60 + 60 - 15 - 20 = 145 frames
|
|
```
|