[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CPHSAXGFNR3VG6BKQESQ45":3,"skill-same:01M7CPHSAXGFNR3VG6BKQESQ45":59},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7CPHSAXGFNR3VG6BKQESQ45","motion-canvas",null,"Carchaloneo22\u002FClaude-Code-template","Carchaloneo22","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F159488757?v=4","01M7CK5MQXAFZE3W7SAP69KNYR","Carlos Chaparro","01M7CK5MRFE26CDPEQDN5RSQPK",2,"MIT","https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fvideo\u002Fmotion-canvas\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: motion-canvas\ndescription: Complete production-ready guide for Motion Canvas with ESM\u002FCommonJS workarounds, full setup templates, and troubleshooting for programmatic video creation using TypeScript\nversion: 2.0.0\nauthor: motion-canvas\nrepo: https:\u002F\u002Fgithub.com\u002Fmotion-canvas\u002Fmotion-canvas\nlicense: MIT\ntags: [Video, TypeScript, Animation, Motion Canvas, Signals, Generators, Canvas API, Vector, Audio Sync, Vite, ESM]\ndependencies: [@motion-canvas\u002Fcore>=3.0.0, @motion-canvas\u002F2d>=3.0.0, @motion-canvas\u002Fui>=3.0.0, @motion-canvas\u002Fvite-plugin>=3.0.0]\n---\n\n# Motion Canvas - Production-Ready Video Creation with TypeScript\n\nComplete production-ready skill for creating programmatic videos using Motion Canvas, including critical ESM\u002FCommonJS workarounds, full configuration templates, and comprehensive troubleshooting.\n\n## ⚠️ CRITICAL: ESM\u002FCommonJS Interoperability Issue\n\n**IMPORTANT**: The `@motion-canvas\u002Fvite-plugin` package is distributed as CommonJS, which causes import errors in modern ESM projects. The standard `import motionCanvas from '@motion-canvas\u002Fvite-plugin'` **WILL NOT WORK**.\n\nYou MUST use the `createRequire` workaround documented in the Setup section below.\n\n## When to use\n\nUse this skill whenever you are dealing with Motion Canvas code to obtain domain-specific knowledge about:\n\n- Creating animated videos using TypeScript and generator functions\n- Building animations with signals and reactive values\n- Working with vector graphics and Canvas API\n- Synchronizing animations with voice-overs and audio\n- Using the real-time preview editor for instant feedback\n- Implementing procedural animations with flow control\n- Creating informative visualizations and diagrams\n- Animating text, shapes, and custom components\n- **Setting up Motion Canvas projects from scratch with correct configuration**\n- **Troubleshooting common setup and build errors**\n\n## Core Concepts\n\nMotion Canvas allows you to create videos using:\n- **Generator Functions**: Describe animations using JavaScript generators with `yield*` syntax\n- **Signals**: Reactive values that automatically update dependent properties\n- **Real-time Preview**: Live editor with instant preview powered by Vite\n- **TypeScript-First**: Write animations in TypeScript with full IDE support\n- **Canvas API**: Leverage 2D Canvas for high-performance vector rendering\n- **Audio Synchronization**: Sync animations precisely with voice-overs\n\n## Complete Setup Guide\n\n### Step 1: Initialize Project\n\n```bash\n# Create project directory\nmkdir my-motion-canvas-project\ncd my-motion-canvas-project\n\n# Initialize package.json\nnpm init -y\n```\n\n### Step 2: Configure package.json for ESM\n\n**CRITICAL**: Add `\"type\": \"module\"` to enable ESM imports.\n\n```json\n{\n  \"name\": \"my-motion-canvas-project\",\n  \"version\": \"1.0.0\",\n  \"type\": \"module\",\n  \"scripts\": {\n    \"dev\": \"vite\",\n    \"build\": \"vite build\",\n    \"preview\": \"vite preview\"\n  }\n}\n```\n\n### Step 3: Install ALL Required Dependencies\n\n**CRITICAL**: Must include `@motion-canvas\u002Fui` - the plugin will fail without it.\n\n```bash\nnpm install --save-dev @motion-canvas\u002Fcore @motion-canvas\u002F2d @motion-canvas\u002Fvite-plugin @motion-canvas\u002Fui vite typescript\n```\n\n### Step 4: Create Project Structure\n\n```\nmy-motion-canvas-project\u002F\n├── package.json          # \"type\": \"module\" required\n├── vite.config.js        # Use .js NOT .ts (see Step 5)\n├── tsconfig.json         # TypeScript configuration\n├── index.html            # HTML entry point\n└── src\u002F\n    ├── project.ts        # Project configuration with scenes\n    └── scenes\u002F\n        └── example.tsx   # Animation scene\n```\n\n### Step 5: Create vite.config.js with ESM\u002FCommonJS Workaround\n\n**CRITICAL**: Use `vite.config.js` (NOT `.ts`) with the `createRequire` workaround.\n\n**File: `vite.config.js`**\n```javascript\nimport {defineConfig} from 'vite';\nimport {createRequire} from 'module';\n\n\u002F\u002F WORKAROUND: @motion-canvas\u002Fvite-plugin is CommonJS, must use require\nconst require = createRequire(import.meta.url);\nconst motionCanvasModule = require('@motion-canvas\u002Fvite-plugin');\nconst motionCanvas = motionCanvasModule.default || motionCanvasModule;\n\nexport default defineConfig({\n  plugins: [\n    motionCanvas({\n      project: '.\u002Fsrc\u002Fproject.ts',\n    }),\n  ],\n});\n```\n\n**Why .js instead of .ts?**\n- Vite config runs before TypeScript compilation\n- The `createRequire` workaround works reliably in plain JavaScript\n- Avoids additional type resolution complexity\n\n### Step 6: Create tsconfig.json\n\n**CRITICAL**: Include `esModuleInterop` and `allowSyntheticDefaultImports`.\n\n**File: `tsconfig.json`**\n```json\n{\n  \"compilerOptions\": {\n    \"target\": \"ES2020\",\n    \"module\": \"ES2020\",\n    \"lib\": [\"ES2020\", \"DOM\"],\n    \"jsx\": \"react-jsx\",\n    \"jsxImportSource\": \"@motion-canvas\u002F2d\u002Flib\",\n    \"moduleResolution\": \"node\",\n    \"esModuleInterop\": true,\n    \"allowSyntheticDefaultImports\": true,\n    \"strict\": true,\n    \"skipLibCheck\": true,\n    \"resolveJsonModule\": true,\n    \"isolatedModules\": true,\n    \"noEmit\": true\n  },\n  \"include\": [\"src\u002F**\u002F*\"],\n  \"exclude\": [\"node_modules\"]\n}\n```\n\n### Step 7: Create index.html\n\n**File: `index.html`**\n```html\n\u003C!DOCTYPE html>\n\u003Chtml lang=\"en\">\n\u003Chead>\n  \u003Cmeta charset=\"UTF-8\">\n  \u003Cmeta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n  \u003Ctitle>Motion Canvas Project\u003C\u002Ftitle>\n\u003C\u002Fhead>\n\u003Cbody>\n  \u003Cdiv id=\"root\">\u003C\u002Fdiv>\n  \u003Cscript type=\"module\" src=\"\u002Fsrc\u002Fproject.ts\">\u003C\u002Fscript>\n\u003C\u002Fbody>\n\u003C\u002Fhtml>\n```\n\n### Step 8: Create src\u002Fproject.ts\n\n**File: `src\u002Fproject.ts`**\n```typescript\nimport {makeProject} from '@motion-canvas\u002Fcore';\nimport example from '.\u002Fscenes\u002Fexample?scene';\n\nexport default makeProject({\n  scenes: [example],\n});\n```\n\n### Step 9: Create First Animation Scene\n\n**File: `src\u002Fscenes\u002Fexample.tsx`**\n```typescript\nimport {makeScene2D} from '@motion-canvas\u002F2d\u002Flib\u002Fscenes';\nimport {Circle} from '@motion-canvas\u002F2d\u002Flib\u002Fcomponents';\nimport {createRef} from '@motion-canvas\u002Fcore\u002Flib\u002Futils';\nimport {all} from '@motion-canvas\u002Fcore\u002Flib\u002Fflow';\n\nexport default makeScene2D(function* (view) {\n  const circleRef = createRef\u003CCircle>();\n\n  view.add(\n    \u003CCircle\n      ref={circleRef}\n      size={70}\n      fill=\"#e13238\"\n    \u002F>,\n  );\n\n  \u002F\u002F Animate circle size and position\n  yield* circleRef().size(140, 1);\n  yield* circleRef().position.x(300, 1);\n  yield* circleRef().fill('#e6a700', 1);\n\n  \u002F\u002F Parallel animations\n  yield* all(\n    circleRef().scale(1.5, 0.5),\n    circleRef().rotation(360, 1)\n  );\n});\n```\n\n### Step 10: Run Development Server\n\n```bash\nnpm run dev\n```\n\nOpen browser at `http:\u002F\u002Flocalhost:5173` to see the Motion Canvas editor.\n\n## Troubleshooting\n\n### Error: `TypeError: motionCanvas is not a function`\n\n**Cause**: ESM\u002FCommonJS interoperability issue with `@motion-canvas\u002Fvite-plugin`\n\n**Solution**: Use the `createRequire` workaround in `vite.config.js` (see Step 5)\n\n```javascript\n\u002F\u002F ❌ WRONG - Will not work\nimport motionCanvas from '@motion-canvas\u002Fvite-plugin';\n\n\u002F\u002F ✅ CORRECT - Use createRequire\nimport {createRequire} from 'module';\nconst require = createRequire(import.meta.url);\nconst motionCanvasModule = require('@motion-canvas\u002Fvite-plugin');\nconst motionCanvas = motionCanvasModule.default || motionCanvasModule;\n```\n\n### Error: `Cannot find module '@motion-canvas\u002Fui'`\n\n**Cause**: Missing required dependency\n\n**Solution**: Install the UI package:\n```bash\nnpm install --save-dev @motion-canvas\u002Fui\n```\n\n### Error: `Property 'default' does not exist on type ...`\n\n**Cause**: TypeScript configuration missing ESM interop settings\n\n**Solution**: Add to `tsconfig.json`:\n```json\n{\n  \"compilerOptions\": {\n    \"esModuleInterop\": true,\n    \"allowSyntheticDefaultImports\": true\n  }\n}\n```\n\n### Warning: `The CJS build of Vite's Node API is deprecated`\n\n**Status**: This is a known warning and can be safely ignored. It appears because `@motion-canvas\u002Fvite-plugin` is CommonJS. The workaround ensures functionality despite the warning.\n\n### Error: `Failed to resolve import \"*.tsx?scene\"`\n\n**Cause**: Vite plugin not properly loaded or configured\n\n**Solution**:\n1. Verify `vite.config.js` has the correct workaround\n2. Check `project` path points to correct file: `'.\u002Fsrc\u002Fproject.ts'`\n3. Ensure scene imports use `?scene` suffix: `import example from '.\u002Fscenes\u002Fexample?scene';`\n\n### Build fails with TypeScript errors\n\n**Solution**:\n1. Verify `tsconfig.json` includes all required options (see Step 6)\n2. Check `jsxImportSource` is set to `@motion-canvas\u002F2d\u002Flib`\n3. Ensure all dependencies are installed\n\n## How to use\n\nRead individual rule files for detailed explanations and code examples:\n\n### Core Animation Concepts\n- **[references\u002Fgenerators.md](references\u002Fgenerators.md)** - Generator functions for describing animations\n- **[references\u002Fsignals.md](references\u002Fsignals.md)** - Reactive signals for dynamic properties and dependencies\n- **[references\u002Fanimations.md](references\u002Fanimations.md)** - Tweening properties and creating smooth animations\n\nFor additional topics like scenes, shapes, text rendering, audio synchronization, and advanced features, refer to the comprehensive [Motion Canvas official documentation](https:\u002F\u002Fmotioncanvas.io\u002Fdocs).\n\n## Complete Working Example\n\nThis is a complete, tested project structure that works out of the box:\n\n```\nmy-motion-canvas-project\u002F\n├── package.json\n│   {\n│     \"name\": \"my-motion-canvas-project\",\n│     \"type\": \"module\",\n│     \"scripts\": {\n│       \"dev\": \"vite\",\n│       \"build\": \"vite build\"\n│     },\n│     \"devDependencies\": {\n│       \"@motion-canvas\u002Fcore\": \"^3.0.0\",\n│       \"@motion-canvas\u002F2d\": \"^3.0.0\",\n│       \"@motion-canvas\u002Fvite-plugin\": \"^3.0.0\",\n│       \"@motion-canvas\u002Fui\": \"^3.0.0\",\n│       \"vite\": \"^5.0.0\",\n│       \"typescript\": \"^5.0.0\"\n│     }\n│   }\n│\n├── vite.config.js (with createRequire workaround)\n├── tsconfig.json (with esModuleInterop)\n├── index.html\n└── src\u002F\n    ├── project.ts (makeProject with scenes array)\n    └── scenes\u002F\n        └── example.tsx (makeScene2D with animations)\n```\n\n## Best Practices\n\n1. **Always use the createRequire workaround** - Don't try standard ESM imports for the Vite plugin\n2. **Use vite.config.js not .ts** - Avoids additional compilation complexity\n3. **Include all dependencies** - Don't forget `@motion-canvas\u002Fui`\n4. **Use generator functions** - All scene animations should use `function*` and `yield*` syntax\n5. **Leverage signals** - Create reactive dependencies between properties\n6. **Think in durations** - Specify animation duration in seconds as the second parameter\n7. **Use refs for control** - Create references to nodes for precise animation control\n8. **Preview frequently** - Take advantage of the real-time editor for instant feedback\n9. **Organize scenes** - Break complex animations into multiple scenes\n10. **Type everything** - Use TypeScript for better IDE support and fewer errors\n\n## Common Pitfalls to Avoid\n\n1. ❌ Forgetting `\"type\": \"module\"` in package.json\n2. ❌ Using standard import for `@motion-canvas\u002Fvite-plugin`\n3. ❌ Not installing `@motion-canvas\u002Fui`\n4. ❌ Missing `esModuleInterop` in tsconfig.json\n5. ❌ Using `vite.config.ts` instead of `vite.config.js`\n6. ❌ Forgetting `?scene` suffix in scene imports\n\n## Resources\n\n- **Documentation**: https:\u002F\u002Fmotioncanvas.io\u002Fdocs\n- **Repository**: https:\u002F\u002Fgithub.com\u002Fmotion-canvas\u002Fmotion-canvas\n- **Examples**: https:\u002F\u002Fmotioncanvas.io\u002Fdocs\u002Fquickstart\n- **Community**: Discord and GitHub Discussions\n- **License**: MIT\n","# Motion Canvas - Production-Ready Video Creation with TypeScript\n\nComplete production-ready skill for creating programmatic videos using Motion Canvas, including critical ESM\u002FCommonJS workarounds, full configuration templates, and comprehensive troubleshooting.\n\n## ⚠️ CRITICAL: ESM\u002FCommonJS Interoperability Issue\n\n**IMPORTANT**: The `@motion-canvas\u002Fvite-plugin` package is distributed as CommonJS, which causes import errors in modern ESM projects. The standard `import motionCanvas from '@motion-canvas\u002Fvite-plugin'` **WILL NOT WORK**.\n\nYou MUST use the `createRequire` workaround documented in the Setup section below.\n\n## When to use\n\nUse this skill whenever you are dealing with Motion Canvas code to obtain domain-specific knowledge about:\n\n- Creating animated videos using TypeScript and generator functions\n- Building animations with signals and reactive values\n- Working with vector graphics and Canvas API\n- Synchronizing animations with voice-overs and audio\n- Using the real-time preview editor for instant feedback\n- Implementing procedural animations with flow control\n- Creating informative visualizations and diagrams\n- Animating text, shapes, and custom components\n- **Setting up Motion Canvas projects from scratch with correct configuration**\n- **Troubleshooting common setup and build errors**\n\n## Core Concepts\n\nMotion Canvas allows you to create videos using:\n- **Generator Functions**: Describe animations using JavaScript generators with `yield*` syntax\n- **Signals**: Reactive values that automatically update dependent properties\n- **Real-time Preview**: Live editor with instant preview powered by Vite\n- **TypeScript-First**: Write animations in TypeScript with full IDE support\n- **Canvas API**: Leverage 2D Canvas for high-performance vector rendering\n- **Audio Synchronization**: Sync animations precisely with voice-overs\n\n## Complete Setup Guide\n\n### Step 1: Initialize Project\n\n```bash\n# Create project directory\nmkdir my-motion-canvas-project\ncd my-motion-canvas-project\n\n# Initialize package.json\nnpm init -y\n```\n\n### Step 2: Configure package.json for ESM\n\n**CRITICAL**: Add `\"type\": \"module\"` to enable ESM imports.\n\n```json\n{\n  \"name\": \"my-motion-canvas-project\",\n  \"version\": \"1.0.0\",\n  \"type\": \"module\",\n  \"scripts\": {\n    \"dev\": \"vite\",\n    \"build\": \"vite build\",\n    \"preview\": \"vite preview\"\n  }\n}\n```\n\n### Step 3: Install ALL Required Dependencies\n\n**CRITICAL**: Must include `@motion-canvas\u002Fui` - the plugin will fail without it.\n\n```bash\nnpm install --save-dev @motion-canvas\u002Fcore @motion-canvas\u002F2d @motion-canvas\u002Fvite-plugin @motion-canvas\u002Fui vite typescript\n```\n\n### Step 4: Create Project Structure\n\n```\nmy-motion-canvas-project\u002F\n├── package.json          # \"type\": \"module\" required\n├── vite.config.js        # Use .js NOT .ts (see Step 5)\n├── tsconfig.json         # TypeScript configuration\n├── index.html            # HTML entry point\n└── src\u002F\n    ├── project.ts        # Project configuration with scenes\n    └── scenes\u002F\n        └── example.tsx   # Animation scene\n```\n\n### Step 5: Create vite.config.js with ESM\u002FCommonJS Workaround\n\n**CRITICAL**: Use `vite.config.js` (NOT `.ts`) with the `createRequire` workaround.\n\n**File: `vite.config.js`**\n```javascript\nimport {defineConfig} from 'vite';\nimport {createRequire} from 'module';\n\n\u002F\u002F WORKAROUND: @motion-canvas\u002Fvite-plugin is CommonJS, must use require\nconst require = createRequire(import.meta.url);\nconst motionCanvasModule = require('@motion-canvas\u002Fvite-plugin');\nconst motionCanvas = motionCanvasModule.default || motionCanvasModule;\n\nexport default defineConfig({\n  plugins: [\n    motionCanvas({\n      project: '.\u002Fsrc\u002Fproject.ts',\n    }),\n  ],\n});\n```\n\n**Why .js instead of .ts?**\n- Vite config runs before TypeScript compilation\n- The `createRequire` workaround works reliably in plain JavaScript\n- Avoids additional type resolution complexity\n\n### Step 6: Create tsconfig.json\n\n**CRITICAL**: Include `esModuleInterop` and `allowSyntheticDefaultImports`.\n\n**File: `tsconfig.json`**\n```json\n{\n  \"compilerOptions\": {\n    \"target\": \"ES2020\",\n    \"module\": \"ES2020\",\n    \"lib\": [\"ES2020\", \"DOM\"],\n    \"jsx\": \"react-jsx\",\n    \"jsxImportSource\": \"@motion-canvas\u002F2d\u002Flib\",\n    \"moduleResolution\": \"node\",\n    \"esModuleInterop\": true,\n    \"allowSyntheticDefaultImports\": true,\n    \"strict\": true,\n    \"skipLibCheck\": true,\n    \"resolveJsonModule\": true,\n    \"isolatedModules\": true,\n    \"noEmit\": true\n  },\n  \"include\": [\"src\u002F**\u002F*\"],\n  \"exclude\": [\"node_modules\"]\n}\n```\n\n### Step 7: Create index.html\n\n**File: `index.html`**\n```html\n\u003C!DOCTYPE html>\n\u003Chtml lang=\"en\">\n\u003Chead>\n  \u003Cmeta charset=\"UTF-8\">\n  \u003Cmeta name=\"viewport\" content=\"width=device-width, initial-scale=1.0\">\n  \u003Ctitle>Motion Canvas Project\u003C\u002Ftitle>\n\u003C\u002Fhead>\n\u003Cbody>\n  \u003Cdiv id=\"root\">\u003C\u002Fdiv>\n  \u003Cscript type=\"module\" src=\"\u002Fsrc\u002Fproject.ts\">\u003C\u002Fscript>\n\u003C\u002Fbody>\n\u003C\u002Fhtml>\n```\n\n### Step 8: Create src\u002Fproject.ts\n\n**File: `src\u002Fproject.ts`**\n```typescript\nimport {makeProject} from '@motion-canvas\u002Fcore';\nimport example from '.\u002Fscenes\u002Fexample?scene';\n\nexport default makeProject({\n  scenes: [example],\n});\n```\n\n### Step 9: Create First Animation Scene\n\n**File: `src\u002Fscenes\u002Fexample.tsx`**\n```typescript\nimport {makeScene2D} from '@motion-canvas\u002F2d\u002Flib\u002Fscenes';\nimport {Circle} from '@motion-canvas\u002F2d\u002Flib\u002Fcomponents';\nimport {createRef} from '@motion-canvas\u002Fcore\u002Flib\u002Futils';\nimport {all} from '@motion-canvas\u002Fcore\u002Flib\u002Fflow';\n\nexport default makeScene2D(function* (view) {\n  const circleRef = createRef\u003CCircle>();\n\n  view.add(\n    \u003CCircle\n      ref={circleRef}\n      size={70}\n      fill=\"#e13238\"\n    \u002F>,\n  );\n\n  \u002F\u002F Animate circle size and position\n  yield* circleRef().size(140, 1);\n  yield* circleRef().position.x(300, 1);\n  yield* circleRef().fill('#e6a700', 1);\n\n  \u002F\u002F Parallel animations\n  yield* all(\n    circleRef().scale(1.5, 0.5),\n    circleRef().rotation(360, 1)\n  );\n});\n```\n\n### Step 10: Run Development Server\n\n```bash\nnpm run dev\n```\n\nOpen browser at `http:\u002F\u002Flocalhost:5173` to see the Motion Canvas editor.\n\n## Troubleshooting\n\n### Error: `TypeError: motionCanvas is not a function`\n\n**Cause**: ESM\u002FCommonJS interoperability issue with `@motion-canvas\u002Fvite-plugin`\n\n**Solution**: Use the `createRequire` workaround in `vite.config.js` (see Step 5)\n\n```javascript\n\u002F\u002F ❌ WRONG - Will not work\nimport motionCanvas from '@motion-canvas\u002Fvite-plugin';\n\n\u002F\u002F ✅ CORRECT - Use createRequire\nimport {createRequire} from 'module';\nconst require = createRequire(import.meta.url);\nconst motionCanvasModule = require('@motion-canvas\u002Fvite-plugin');\nconst motionCanvas = motionCanvasModule.default || motionCanvasModule;\n```\n\n### Error: `Cannot find module '@motion-canvas\u002Fui'`\n\n**Cause**: Missing required dependency\n\n**Solution**: Install the UI package:\n```bash\nnpm install --save-dev @motion-canvas\u002Fui\n```\n\n### Error: `Property 'default' does not exist on type ...`\n\n**Cause**: TypeScript configuration missing ESM interop settings\n\n**Solution**: Add to `tsconfig.json`:\n```json\n{\n  \"compilerOptions\": {\n    \"esModuleInterop\": true,\n    \"allowSyntheticDefaultImports\": true\n  }\n}\n```\n\n### Warning: `The CJS build of Vite's Node API is deprecated`\n\n**Status**: This is a known warning and can be safely ignored. It appears because `@motion-canvas\u002Fvite-plugin` is CommonJS. The workaround ensures functionality despite the warning.\n\n### Error: `Failed to resolve import \"*.tsx?scene\"`\n\n**Cause**: Vite plugin not properly loaded or configured\n\n**Solution**:\n1. Verify `vite.config.js` has the correct workaround\n2. Check `project` path points to correct file: `'.\u002Fsrc\u002Fproject.ts'`\n3. Ensure scene imports use `?scene` suffix: `import example from '.\u002Fscenes\u002Fexample?scene';`\n\n### Build fails with TypeScript errors\n\n**Solution**:\n1. Verify `tsconfig.json` includes all required options (see Step 6)\n2. Check `jsxImportSource` is set to `@motion-canvas\u002F2d\u002Flib`\n3. Ensure all dependencies are installed\n\n## How to use\n\nRead individual rule files for detailed explanations and code examples:\n\n### Core Animation Concepts\n- **[references\u002Fgenerators.md](references\u002Fgenerators.md)** - Generator functions for describing animations\n- **[references\u002Fsignals.md](references\u002Fsignals.md)** - Reactive signals for dynamic properties and dependencies\n- **[references\u002Fanimations.md](references\u002Fanimations.md)** - Tweening properties and creating smooth animations\n\nFor additional topics like scenes, shapes, text rendering, audio synchronization, and advanced features, refer to the comprehensive [Motion Canvas official documentation](https:\u002F\u002Fmotioncanvas.io\u002Fdocs).\n\n## Complete Working Example\n\nThis is a complete, tested project structure that works out of the box:\n\n```\nmy-motion-canvas-project\u002F\n├── package.json\n│   {\n│     \"name\": \"my-motion-canvas-project\",\n│     \"type\": \"module\",\n│     \"scripts\": {\n│       \"dev\": \"vite\",\n│       \"build\": \"vite build\"\n│     },\n│     \"devDependencies\": {\n│       \"@motion-canvas\u002Fcore\": \"^3.0.0\",\n│       \"@motion-canvas\u002F2d\": \"^3.0.0\",\n│       \"@motion-canvas\u002Fvite-plugin\": \"^3.0.0\",\n│       \"@motion-canvas\u002Fui\": \"^3.0.0\",\n│       \"vite\": \"^5.0.0\",\n│       \"typescript\": \"^5.0.0\"\n│     }\n│   }\n│\n├── vite.config.js (with createRequire workaround)\n├── tsconfig.json (with esModuleInterop)\n├── index.html\n└── src\u002F\n    ├── project.ts (makeProject with scenes array)\n    └── scenes\u002F\n        └── example.tsx (makeScene2D with animations)\n```\n\n## Best Practices\n\n1. **Always use the createRequire workaround** - Don't try standard ESM imports for the Vite plugin\n2. **Use vite.config.js not .ts** - Avoids additional compilation complexity\n3. **Include all dependencies** - Don't forget `@motion-canvas\u002Fui`\n4. **Use generator functions** - All scene animations should use `function*` and `yield*` syntax\n5. **Leverage signals** - Create reactive dependencies between properties\n6. **Think in durations** - Specify animation duration in seconds as the second parameter\n7. **Use refs for control** - Create references to nodes for precise animation control\n8. **Preview frequently** - Take advantage of the real-time editor for instant feedback\n9. **Organize scenes** - Break complex animations into multiple scenes\n10. **Type everything** - Use TypeScript for better IDE support and fewer errors\n\n## Common Pitfalls to Avoid\n\n1. ❌ Forgetting `\"type\": \"module\"` in package.json\n2. ❌ Using standard import for `@motion-canvas\u002Fvite-plugin`\n3. ❌ Not installing `@motion-canvas\u002Fui`\n4. ❌ Missing `esModuleInterop` in tsconfig.json\n5. ❌ Using `vite.config.ts` instead of `vite.config.js`\n6. ❌ Forgetting `?scene` suffix in scene imports\n\n## Resources\n\n- **Documentation**: https:\u002F\u002Fmotioncanvas.io\u002Fdocs\n- **Repository**: https:\u002F\u002Fgithub.com\u002Fmotion-canvas\u002Fmotion-canvas\n- **Examples**: https:\u002F\u002Fmotioncanvas.io\u002Fdocs\u002Fquickstart\n- **Community**: Discord and GitHub Discussions\n- **License**: MIT\n",{},"add-x-twitter-scraper-skill","7bc347b2f7dc2dde2761a965585925e0d0171748","cli-tool\u002Fcomponents\u002Fskills\u002Fvideo\u002Fmotion-canvas",0,"https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template","https:\u002F\u002Fgithub.com\u002FCarchaloneo22","Ingeniero Informático | Ingeniero en Desarrollo de Software | Consultor TIC en Gestión Publica | Docente Análisis y Desarrollo de Software. ","2026-09-12 11:10:56",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Carchaloneo22\u002FClaude-Code-template --skill motion-canvas",{"tool":37,"command":38},"bunx","bunx skills add Carchaloneo22\u002FClaude-Code-template --skill motion-canvas",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Carchaloneo22\u002FClaude-Code-template --skill motion-canvas","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fvideo\u002Fmotion-canvas\u002FSKILL.md",true,[45,51,55],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Fanimations.md","REFERENCE","参考文档",3328,"https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fvideo\u002Fmotion-canvas\u002Freferences\u002Fanimations.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fgenerators.md",2038,"https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fvideo\u002Fmotion-canvas\u002Freferences\u002Fgenerators.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fsignals.md",2632,"https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fvideo\u002Fmotion-canvas\u002Freferences\u002Fsignals.md",[60,67,76,83,90,97],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7CPQFVGKX7H3Q5Y9CN0XAZN","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fzapier-make-patterns\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":71,"licenseFileUrl":72,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":18},"01M7CPQDR2HMKAYHAAY99EA4B2","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M7CPQ7K5MAQSXEB027HZFM2G","workflow-automation","Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off.  This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation.  Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility","https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fworkflow-automation\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":18},"01M7CPQ34F18JHMEM8NHQS1N7K","trigger-dev","Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.","https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Ftrigger-dev\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":18},"01M7CPPZSXXDB1SAWT5N63ACZT","planning-with-files","Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.","https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fplanning-with-files\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":18},"01M7CPPTQSBVWSK0R10FJNMP0F","n8n-workflow-patterns","Proven workflow architectural patterns from real n8n workflows. Use when building new workflows, designing workflow structure, choosing workflow patterns, planning workflow architecture, or asking about webhook processing, HTTP API integration, database operations, AI agent workflows, or scheduled tasks.","https:\u002F\u002Fgithub.com\u002FCarchaloneo22\u002FClaude-Code-template\u002Fblob\u002Fadd-x-twitter-scraper-skill\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fworkflow-automation\u002Fn8n\u002Fn8n-workflow-patterns\u002FSKILL.md",[],[]]