USEthree steps

Téléchargez. Donnez-le à l'IA.Faites-le vôtre.

Choisissez un style, puis ajoutez votre propre texte et vos ressources. Réalisez une première prévisualisation avec votre assistant et affinez-la jusqu'à obtenir votre vidéo.

Choisissez un assistant et regardez la démo ↓
  1. 01

    Télécharger .motion

    Prévisualisez un modèle, choisissez un style et téléchargez-le. Le package inclut le code source, les paramètres, les variantes de style et les licences.

    Parcourir les modèles →
  2. 02

    Donnez-le à votre assistant IA

    Donnez le fichier à votre assistant et dites « Utilisez ce modèle pour mon contenu. » Il lira motion.json, expliquera ce que vous pouvez modifier et identifiera les entrées manquantes.

    Instructions pour l'IA →
  3. 03

    Exporter votre vidéo

    Ajoutez votre texte, vos images ou vos données. Vérifiez les dépendances d'exécution et examinez l'aperçu avant d'exporter, et conservez le projet modifiable pour plus tard.

    Full creation tutorial →
WALKTHROUGH.motion → your video

Choisissez votre assistant. Suivez le guide.

Choose your assistant and follow the conversation. Each walkthrough includes its controls, starting brief and practical tips.

Flux de production local

Claude desktop · Code tab; CLI alternative

Choose a local environment and project folder, then preview and revise in a Code session.

Mode de travail
Claude desktop · Code tab; CLI alternative
Modèle recommandé
Choose an available model with the required tools; verify actual file and runtime access before production.
Illustration du flux de travail01 / 03
my-video.motionTélécharger et conserver l'original
↓
Vous

Utilisez ce modèle et guidez-moi pour commencer à créer ma vidéo.

Claude Code
Prévisualisez d'abord. Continuez à affiner.
Official instructions ↗Full creation tutorial →
Controls and tips for Claude Code

Ordinary mobile or web chat can prepare content. Remote continuation needs a real connection to the original session; uploading a file does not connect your computer environment.

  1. Open the Code tab

    Sign in to Claude desktop and choose Code. Select a local execution environment below the composer; a cloud repository session does not automatically see your Downloads folder.

  2. Choose this project folder

    Use the project-folder control beside the environment selector, or the folder settings of a saved environment. For CLI, run claude from this project directory.

  3. Read the entry and approve a plan

    Provide the package path and brief. Use Plan to review the approach, then switch to an editing/execution mode for production and handle tool requests as prompted.

  4. Open the preview and revise

    In a local session, open the returned HTML or video path, or the preview server card. Review picture and sound, revise in the same session, and approve export.

Plan does not start production

After approving the plan, switch to an execution mode and ask for a real preview and instructions for opening it.

Envoyez ceci avec votre modèle
I am working in a local Claude Code session. Confirm this project directory and the actual .motion path, read the package entry point, and prepare a reviewable plan before preview production.

Topic: [fill in]
Platform and aspect ratio: [fill in]
Target duration: [fill in]
Available copy, assets or audio: [fill in / none yet]

Preserve the original .motion. Read only its outer entries first; if present, read 00-START-HERE.md and assistant/guide.json without extracting personal identity or protected content. Otherwise identify the author project structure. For production, follow the packaged entry to verify tools and identity, read the real input contract and check updates and dependencies. Explain update impact and preserve approved versions. Help me complete the brief, approve a plan and generate a real preview in a separate production folder. After approval, export through the template entry and deliver video and editable project paths. Report actual errors and unfinished work. Keep private assets and keys out of public files and explain service and budget before paid generation.
Flux de production local

Codex local project / CLI

Have Codex read the original package, run production and deliver real files from this project folder.

Mode de travail
Codex local project / CLI
Modèle recommandé
Choose an available model with the required tools; verify actual file and runtime access before production.
Illustration du flux de travail01 / 03
my-video.motionTélécharger et conserver l'original
↓
Vous

Utilisez ce modèle et guidez-moi pour commencer à créer ma vidéo.

Codex
Prévisualisez d'abord. Continuez à affiner.
Official instructions ↗Full creation tutorial →
Controls and tips for Codex

Prepare the brief on your phone. To continue desktop work, check the connected task or environment; cloud tasks do not inherit local asset paths.

  1. Choose Codex and the local project

    Select Codex in the desktop product selector and open or choose this local project folder. Add the downloaded package and assets and check the task directory.

  2. CLI alternative

    Install the CLI using its official guide, run codex from this video directory, and sign in when prompted. Use either desktop or CLI; cloud tasks need their own files and environment.

  3. Send the exact path and brief

    Ask it to verify the package, entry and tools using the brief below. After planning, switch to task execution and handle tool requests for the actual operation.

  4. Open the real preview

    Open the preview path or browser URL. If it fails, ask it to verify file existence and server status. Review picture and sound before requesting video export and editable sources.

The path looks right but is not accessible

Ask for the current working directory and visible files. Check for a cloud environment or different project, then supply the file in the actual workspace or choose the correct local folder.

Envoyez ceci avec votre modèle
I am using a local Codex production project. Check the working directory and .motion path, read the real package, identify missing inputs and runtime tools, and provide an opening link when the preview is ready.

Topic: [fill in]
Platform and aspect ratio: [fill in]
Target duration: [fill in]
Available copy, assets or audio: [fill in / none yet]

Preserve the original .motion. Read only its outer entries first; if present, read 00-START-HERE.md and assistant/guide.json without extracting personal identity or protected content. Otherwise identify the author project structure. For production, follow the packaged entry to verify tools and identity, read the real input contract and check updates and dependencies. Explain update impact and preserve approved versions. Help me complete the brief, approve a plan and generate a real preview in a separate production folder. After approval, export through the template entry and deliver video and editable project paths. Report actual errors and unfinished work. Keep private assets and keys out of public files and explain service and budget before paid generation.
Flux de production local

Cursor desktop · Agent

Use Agent in the editor project to read files, run commands and inspect the preview.

Mode de travail
Cursor desktop · Agent
Modèle recommandé
Choose an available model with the required tools; verify actual file and runtime access before production.
Illustration du flux de travail01 / 03
my-video.motionTélécharger et conserver l'original
↓
Vous

Utilisez ce modèle et guidez-moi pour commencer à créer ma vidéo.

Cursor
Prévisualisez d'abord. Continuez à affiner.
Official instructions ↗Full creation tutorial →
Controls and tips for Cursor

These steps use the desktop local Agent. For cloud or mobile remote access, recheck the task environment and asset availability.

  1. Open this project folder

    Open the folder containing the package and assets in Cursor, check the file tree, and start an Agent conversation for this video.

  2. Open the Agent side pane

    Open Agent with Cmd+I on macOS or Ctrl+I on Windows. Use an agent that can work with files and the terminal, switching from planning when ready to produce.

  3. Send the path and check tools

    Provide the package path and brief below. Check the actual entry point before preparing inputs, review terminal requests and resolve specific dependency errors.

  4. Review the running preview

    Open the returned preview URL and check terminal results. Revise by timestamp; inspect a checkpoint’s file scope before restoring, and save approved versions separately.

The preview URL does not open

Ask Agent to check the running process, actual port and startup log, and send the browser error to this conversation.

Envoyez ceci avec votre modèle
I am producing this video in Cursor Agent with the original package and assets in this workspace. Check the files, package entry and terminal tools, then start a real preview after plan approval.

Topic: [fill in]
Platform and aspect ratio: [fill in]
Target duration: [fill in]
Available copy, assets or audio: [fill in / none yet]

Preserve the original .motion. Read only its outer entries first; if present, read 00-START-HERE.md and assistant/guide.json without extracting personal identity or protected content. Otherwise identify the author project structure. For production, follow the packaged entry to verify tools and identity, read the real input contract and check updates and dependencies. Explain update impact and preserve approved versions. Help me complete the brief, approve a plan and generate a real preview in a separate production folder. After approval, export through the template entry and deliver video and editable project paths. Report actual errors and unfinished work. Keep private assets and keys out of public files and explain service and budget before paid generation.
Flux de production local

豆包 desktop · work mode

Desktop only: turn on work mode, then read the template, make a preview and export the video.

Mode de travail
豆包 desktop · work mode
Modèle recommandé
Choose an available model with the required tools; verify actual file and runtime access before production.
Illustration du flux de travail01 / 03
my-video.motionTélécharger et conserver l'original
↓
Vous

Utilisez ce modèle et guidez-moi pour commencer à créer ma vidéo.

豆包
Prévisualisez d'abord. Continuez à affiner.
Official instructions ↗Full creation tutorial →
Controls and tips for 豆包

Desktop only. You can draft copy and gather assets in the mobile or web version, then preview and export in desktop work mode.

  1. Install the desktop app

    Download the 豆包 desktop app from the official website and sign in. The web and mobile versions cannot read a local project folder, so this workflow needs the desktop app.

  2. Switch to work mode

    Choose work mode for a new task instead of an ordinary chat. If you cannot find it, update the desktop app to the latest version.

  3. Choose the folder and send the brief

    Create a folder for this video with the .motion package and your assets, select it in work mode and send the brief below. Ask it to report the files it actually read and any missing assets.

  4. Review the preview and export

    Open the preview file or URL it produces and request changes by timestamp. When you are satisfied, ask it to export using the template instructions and report where the video and project are saved.

It answers in text without reading files

Check that you are in work mode with the project folder selected; an ordinary chat cannot see local files. Ask it to list the folder’s files to confirm.

It generates a different AI video

Explain that you want this .motion template’s visuals and animation, and ask it to run the template as packaged. A separately generated clip is not the template preview.

Envoyez ceci avec votre modèle
I selected this video’s project folder in 豆包 desktop work mode. Confirm the folder, read the original .motion package, and report its actual filename and production entry.

Topic: [fill in]
Platform and aspect ratio: [fill in]
Target duration: [fill in]
Available copy, assets or audio: [fill in / none yet]

Preserve the original .motion. Read only its outer entries first; if present, read 00-START-HERE.md and assistant/guide.json without extracting personal identity or protected content. Otherwise identify the author project structure. For production, follow the packaged entry to verify tools and identity, read the real input contract and check updates and dependencies. Explain update impact and preserve approved versions. Help me complete the brief, approve a plan and generate a real preview in a separate production folder. After approval, export through the template entry and deliver video and editable project paths. Report actual errors and unfinished work. Keep private assets and keys out of public files and explain service and budget before paid generation.
Flux de production local

DeepSeek desktop · work mode

Desktop only: turn on work mode, then read the template, make a preview and export the video.

Mode de travail
DeepSeek desktop · work mode
Modèle recommandé
Choose an available model with the required tools; verify actual file and runtime access before production.
Illustration du flux de travail01 / 03
my-video.motionTélécharger et conserver l'original
↓
Vous

Utilisez ce modèle et guidez-moi pour commencer à créer ma vidéo.

DeepSeek
Prévisualisez d'abord. Continuez à affiner.
Official instructions ↗Full creation tutorial →
Controls and tips for DeepSeek

Desktop only. You can draft copy and gather assets in the mobile or web version, then preview and export in desktop work mode.

  1. Install the desktop app

    Download the DeepSeek desktop app from the official website and sign in. The web and mobile versions cannot read a local project folder, so this workflow needs the desktop app.

  2. Switch to work mode

    Choose work mode for a new task instead of an ordinary chat. If you cannot find it, update the desktop app to the latest version.

  3. Choose the folder and send the brief

    Create a folder for this video with the .motion package and your assets, select it in work mode and send the brief below. Ask it to report the files it actually read and any missing assets.

  4. Review the preview and export

    Open the preview file or URL it produces and request changes by timestamp. When you are satisfied, ask it to export using the template instructions and report where the video and project are saved.

It answers in text without reading files

Check that you are in work mode with the project folder selected; an ordinary chat cannot see local files. Ask it to list the folder’s files to confirm.

It generates a different AI video

Explain that you want this .motion template’s visuals and animation, and ask it to run the template as packaged. A separately generated clip is not the template preview.

Envoyez ceci avec votre modèle
I selected this video’s project folder in DeepSeek desktop work mode. Confirm the folder, read the original .motion package, and report its actual filename and production entry.

Topic: [fill in]
Platform and aspect ratio: [fill in]
Target duration: [fill in]
Available copy, assets or audio: [fill in / none yet]

Preserve the original .motion. Read only its outer entries first; if present, read 00-START-HERE.md and assistant/guide.json without extracting personal identity or protected content. Otherwise identify the author project structure. For production, follow the packaged entry to verify tools and identity, read the real input contract and check updates and dependencies. Explain update impact and preserve approved versions. Help me complete the brief, approve a plan and generate a real preview in a separate production folder. After approval, export through the template entry and deliver video and editable project paths. Report actual errors and unfinished work. Keep private assets and keys out of public files and explain service and budget before paid generation.
Flux de production local

TRAE desktop · SOLO mode

Read and run the template in a project, then inspect the preview in the tool panel.

Mode de travail
TRAE desktop · SOLO mode
Modèle recommandé
Choose an available model with the required tools; verify actual file and runtime access before production.
Illustration du flux de travail01 / 03
my-video.motionTélécharger et conserver l'original
↓
Vous

Utilisez ce modèle et guidez-moi pour commencer à créer ma vidéo.

TRAE
Prévisualisez d'abord. Continuez à affiner.
Official instructions ↗Full creation tutorial →
Controls and tips for TRAE

Use the desktop client for this route. Prepare copy and assets on your phone, then continue in the same desktop project.

  1. Prepare this project

    Create a folder for this video, add the .motion package and your assets, and open that folder in TRAE.

  2. Switch to SOLO

    Use the mode selector at the top left to enter SOLO and start a task in this project with the task-executing Agent.

  3. Send the path and brief

    Provide the exact package path and the brief below. Check its file report and missing inputs, approve the plan, then ask it to make the preview.

  4. Inspect the tool panel

    Expand the tool panel at the top right. Check Terminal output, open the preview URL in Browser, and inspect changed files with View changes. Ask for the URL and server status if needed.

It only returns code

Check that you are in a SOLO execution task. Ask it to verify terminal access, start the preview and return the log and URL.

Envoyez ceci avec votre modèle
I have opened this video project in TRAE SOLO. Confirm the project path, read the .motion package, and report its actual filename and production entry point.

Topic: [fill in]
Platform and aspect ratio: [fill in]
Target duration: [fill in]
Available copy, assets or audio: [fill in / none yet]

Preserve the original .motion. Read only its outer entries first; if present, read 00-START-HERE.md and assistant/guide.json without extracting personal identity or protected content. Otherwise identify the author project structure. For production, follow the packaged entry to verify tools and identity, read the real input contract and check updates and dependencies. Explain update impact and preserve approved versions. Help me complete the brief, approve a plan and generate a real preview in a separate production folder. After approval, export through the template entry and deliver video and editable project paths. Report actual errors and unfinished work. Keep private assets and keys out of public files and explain service and budget before paid generation.
Flux de production local

WorkBuddy desktop · selected workspace

Run the task against this video folder and locate the files it actually produces.

Mode de travail
WorkBuddy desktop · selected workspace
Modèle recommandé
Choose an available model with the required tools; verify actual file and runtime access before production.
Illustration du flux de travail01 / 03
my-video.motionTélécharger et conserver l'original
↓
Vous

Utilisez ce modèle et guidez-moi pour commencer à créer ma vidéo.

WorkBuddy
Prévisualisez d'abord. Continuez à affiner.
Official instructions ↗Full creation tutorial →
Controls and tips for WorkBuddy

In the WeChat mini program, use the Cloud / Local (Connect computer) control above the composer. Local work needs the linked desktop app running; cloud tasks do not inherit your computer paths.

  1. Choose a workspace for a new task

    On the desktop new-task page, click Select workspace at the lower left of the composer. Choose the folder containing this video’s .motion package and assets.

  2. Check the task directory

    Ask it to list the package in the selected workspace, then send the brief below. Tasks started without a selected folder may use a default location.

  3. Follow task progress

    Answer asset and planning questions in this task. Inspect file and command requests, and ask for a saved brief and missing-tool list if production cannot run.

  4. Open the result

    Locate the preview in Results or workspace files. Use Open folder in the task menu to find local outputs, and keep revisions in this task.

A phone task cannot see desktop assets

Check the Local / Connect computer environment, desktop availability and linked account. For a cloud task, supply files through its own interface and recheck dependencies.

Envoyez ceci avec votre modèle
I selected this video’s workspace in a new WorkBuddy task. List its .motion package and assets, and tell me where previews and exports will be saved.

Topic: [fill in]
Platform and aspect ratio: [fill in]
Target duration: [fill in]
Available copy, assets or audio: [fill in / none yet]

Preserve the original .motion. Read only its outer entries first; if present, read 00-START-HERE.md and assistant/guide.json without extracting personal identity or protected content. Otherwise identify the author project structure. For production, follow the packaged entry to verify tools and identity, read the real input contract and check updates and dependencies. Explain update impact and preserve approved versions. Help me complete the brief, approve a plan and generate a real preview in a separate production folder. After approval, export through the template entry and deliver video and editable project paths. Report actual errors and unfinished work. Keep private assets and keys out of public files and explain service and budget before paid generation.
Flux de production local

Kimi Code Desktop; CLI alternative

Start production in a Kimi Code local workspace, with ordinary Kimi chat treated separately.

Mode de travail
Kimi Code Desktop; CLI alternative
Modèle recommandé
Choose an available model with the required tools; verify actual file and runtime access before production.
Illustration du flux de travail01 / 03
my-video.motionTélécharger et conserver l'original
↓
Vous

Utilisez ce modèle et guidez-moi pour commencer à créer ma vidéo.

Kimi Code
Prévisualisez d'abord. Continuez à affiner.
Official instructions ↗Full creation tutorial →
Controls and tips for Kimi Code

Ordinary Kimi mobile chat can prepare a script. The workspace, Changes and terminal steps here use Kimi Code Desktop or CLI.

  1. Install and sign in

    Install Kimi Code Desktop from its official source, complete authorization, and check the model picker and your account’s available access.

  2. New session → Choose folder

    Click New session, click the folder name above the composer, then Choose folder… and select this video folder. Check the displayed workspace before sending.

  3. Send the brief and check file access

    Send the brief below and review the package report before planning. For CLI, run kimi in this project directory and use /login in the first session.

  4. Review changes and preview

    Inspect Changes, open File Preview or the returned browser URL, and check terminal output. Give timestamped feedback and request the exported video and project paths.

There is no folder picker in Kimi chat

Open Kimi Code Desktop or install its CLI using the official guide. A chat attachment alone does not create a local production workspace.

Envoyez ceci avec votre modèle
I am producing this video in a Kimi Code local workspace containing the template and assets. Check the workspace path and actual package before helping me prepare the first version.

Topic: [fill in]
Platform and aspect ratio: [fill in]
Target duration: [fill in]
Available copy, assets or audio: [fill in / none yet]

Preserve the original .motion. Read only its outer entries first; if present, read 00-START-HERE.md and assistant/guide.json without extracting personal identity or protected content. Otherwise identify the author project structure. For production, follow the packaged entry to verify tools and identity, read the real input contract and check updates and dependencies. Explain update impact and preserve approved versions. Help me complete the brief, approve a plan and generate a real preview in a separate production folder. After approval, export through the template entry and deliver video and editable project paths. Report actual errors and unfinished work. Keep private assets and keys out of public files and explain service and budget before paid generation.
Flux de production local

Grok Build CLI; ordinary Grok chat needs a separate handoff

Produce with Grok Build file and command tools, distinguishing chat from template rendering.

Mode de travail
Grok Build CLI; ordinary Grok chat needs a separate handoff
Modèle recommandé
Choose an available model with the required tools; verify actual file and runtime access before production.
Illustration du flux de travail01 / 03
my-video.motionTélécharger et conserver l'original
↓
Vous

Utilisez ce modèle et guidez-moi pour commencer à créer ma vidéo.

Grok Build / Grok
Prévisualisez d'abord. Continuez à affiner.
Official instructions ↗Full creation tutorial →
Controls and tips for Grok Build / Grok

Ordinary Grok mobile chat can attach supported sources and prepare scripts. Local Build production needs a work interface with access to that computer project.

  1. Install Grok Build

    Follow the current official Build installation and login guide. Ordinary grok.com chat and the Build CLI are different interfaces; production here uses Build.

  2. Run grok in this video folder

    Open a terminal in the folder containing the package and assets and run grok. Follow first-run sign-in, or use grok login as documented.

  3. Send the path and production brief

    Ask it to check the project, package entry and tools, then execute the approved preview plan. A conversation-export command is different from video export.

  4. Review preview and export

    Open the returned preview URL or video and revise by timestamp. Ordinary chat’s + control can attach supported source material; hand off to Build or another local tool if it cannot run the template.

grok export returns text

That command exports a conversation transcript. Ask the assistant to use the template’s actual rendering entry and return the video path.

Envoyez ceci avec votre modèle
I am in this video project directory in Grok Build. Check the path, original .motion package and file/command tools, then follow its entry point. Deliver video and editable sources rather than a chat transcript export.

Topic: [fill in]
Platform and aspect ratio: [fill in]
Target duration: [fill in]
Available copy, assets or audio: [fill in / none yet]

Preserve the original .motion. Read only its outer entries first; if present, read 00-START-HERE.md and assistant/guide.json without extracting personal identity or protected content. Otherwise identify the author project structure. For production, follow the packaged entry to verify tools and identity, read the real input contract and check updates and dependencies. Explain update impact and preserve approved versions. Help me complete the brief, approve a plan and generate a real preview in a separate production folder. After approval, export through the template entry and deliver video and editable project paths. Report actual errors and unfinished work. Keep private assets and keys out of public files and explain service and budget before paid generation.

Un flux de travail illustré, pas une capture d'écran d'un assistant ni une exportation réelle. Suivez les instructions du package et vos outils actuels.

HANDOFFTexte de transfert

Envoyez ceci avec le fichier

Ceci est un package de modèle MotionGit (fichier .motion, un conteneur ZIP).
Extrayez-le en toute sécurité dans un nouveau répertoire. Lisez motion.json, guide.json, les « Instructions pour l'IA » au début de README.md, puis params.schema.json dans cet ordre.
N'exécutez pas directement le code du package. Dites-moi ce que fait le modèle, ce que je peux remplacer, ses exigences d'exécution et quelles entrées sont manquantes.
Spécification : https://motiongit.com/spec
Exigences d'exécution et tests enregistrés

Runtime compatibility

Production and export depend on execution tools and the template’s runtime dependencies, rather than the model brand. Creative tools such as Claude, Codex, Cursor, GitHub Copilot and Grok are not partnership endorsements or a claim that every client has been tested.

Tool typeWhat it can doExport requirements
Chat-only web or mobile assistantExplain instructions and prepare copy and inputsExport cannot be promised; hand off to a tool with execution capabilities
Desktop or CLI assistant with real file access, unpacking and commandsInspect packages, edit content and run production stepsMust also support the package’s runtime.profile and rendering dependencies
The local renderer specified by the templateRead production instances and create previews and videoFollow motion.json, README and motion.lock.json; common HTML/Canvas templates need Node.js and a browser, and video assembly may need FFmpeg

Work modes and model selection

Use a work / Agent mode with file operations and command execution. The recommendations below are MotionGit guidance. A capable model handles understanding and execution; prepare the browser, Node.js, FFmpeg or other dependencies specified by the package.

Creative toolEntry to useRecommended model
ClaudeClaude Code execution tasks, or a desktop Code / Cowork workspace with file and command toolsThe most capable coding / Agent model available to you
ChatGPT / CodexChatGPT desktop local Work only when actual file and execution tools are available; a local Codex project is another entryThe most capable coding model available; use a higher reasoning setting when offered
CursorOpen the production directory in Cursor Agent; approve file edits and terminal commands as neededChoose the most capable coding / Agent model available to your account
GitHub CopilotStart Copilot CLI in the production directory; use ask / execute mode for productionChoose the most capable coding / Agent model available to your account
GrokGrok Build Agent environment with file and terminal tools; ordinary Grok chat can prepare contentThe most capable coding / Agent model available in that environment

Copilot CLI plan mode prepares an approach; switch back to execution to produce files. Approve required tools as needed. Entries and models depend on your client and account. In ordinary chat, prepare content and hand off to a tool with execution access.

Work entries checked against official documentation on 2026-10-07: OpenAI app and local tasks, Claude work and computer use, and Grok Build CLI. Cursor and Copilot entries checked on 2026-10-08: Cursor Agent and GitHub Copilot CLI. The Claude Code installation entry was also checked on 2026-10-10: Claude Code quickstart. These describe tool capabilities, not completed template export tests.

Recorded tests and unverified environments

  • 2026-10-14: Scoped personal-package first read, plan, prepare and preview passed in actual macOS WorkBuddy and Codex cases. This does not establish acceptance for all ChatGPT desktop conversations, templates or full exports.
  • ChatGPT entry/permission guidance was checked against the official Work guide and permissions guide. Use actual conversation capabilities. Explain usage from public instructions first; report file/approval failures promptly and do not reuse inactive approval requests.
  • 2026-10-06: dark-tech-kit 0.1.0 completed cold unpacking, still rendering and video with audio on macOS, Node 23.11.0, Chrome 154.0.8037.98, Playwright Core 1.58.2 and FFmpeg 9.0.1. Evidence: the project’s C4 acceptance record (internal archive). This proves only that version’s execution workflow, not approval of the latest version, other templates or visual quality.
  • Windows, Linux, other versions and each specific client of the brands above: full production and export remain unverified. Website browser tests are not template rendering tests.

Read the package’s instructions and dependencies first. Confirm file and command access, and obtain user authorization before installing dependencies, using the network or reading external assets. Inspect, preview, then export. Chat-only tools can prepare inputs but must not claim they rendered a video.

HELPFAQ

Quelques points à connaître pour votre premier essai

La pièce jointe reste en cours de chargement ou n’est pas reçue ?

Attendez la fin de l’envoi, puis faites confirmer le nom, la taille et les entrées externes. Une miniature ne confirme pas la réception. Réessayez ou utilisez le ZIP compatible de la fenêtre de téléchargement, sans emballer .motion dans un autre ZIP. Si la lecture échoue, utilisez un assistant local ayant accès au dossier du projet. Les tâches cloud ne reçoivent pas automatiquement les chemins locaux.

L'assistant ne reconnaît pas l'extension .motion ?

Liste les entrées externes du ZIP en lecture seule. Si 00-START-HERE.md et assistant/guide.json existent, lis-les d’abord et suis le point d’entrée inclus. Conserve l’original ; n’extrais ni l’identité personnelle ni le contenu protégé. Signale immédiatement un fichier inaccessible.

Dois-je installer le Skill ?

Les téléchargements personnels actuels incluent leur point d’entrée. Aucun autre Skill ou hôte ni aucune copie d’identifiant ne sont nécessaires. Les outils d’empaquetage de l’auteur ont un autre rôle ; suis les instructions pour les dépendances de rendu.

Comment utiliser ChatGPT sur ordinateur ou le chat web ?

Explique d’abord l’utilisation à partir des instructions publiques. Privilégie le mode local connecté au dossier de production et vérifie la lecture du fichier et l’exécution. Les tâches cloud n’accèdent pas automatiquement aux chemins ni aux outils de l’ordinateur. Un chat sans exécution peut préparer le contenu pour un environnement adapté.

Une approbation a expiré ou le fichier est illisible ?

Indique l’opération inachevée et cesse de réutiliser la demande expirée. Une nouvelle demande doit concerner l’opération actuelle. Explique rapidement les étapes disponibles sans désactiver les approbations ni l’isolation.

L'exportation diffère de la prévisualisation, ou le texte ne s'ajuste pas ?

Indiquez l'horodatage, le texte ou la trame exact et demandez des ajustements dans les limites des paramètres du modèle. Vérifiez les dimensions, la durée, le son et les ressources exportés, ainsi que la conversation.

STARTfeatured

Commencez avec ces modèles