USEthree steps

ダウンロード。AIに渡す。自分だけのものに。

スタイルを選び、自身のテキストとアセットを用意してください。アシスタントと最初のプレビューを作成し、動画に仕上げていきます。

01
.motionをダウンロード
テンプレートをプレビューし、スタイルを選んでダウンロードします。パッケージにはソースコード、パラメータ、スタイルバリエーション、ライセンスが含まれます。
テンプレートを閲覧 →
02
AIアシスタントに渡す
ファイルをアシスタントに渡して「このテンプレートを私のコンテンツに使用して」と指示します。motion.jsonを読み、変更可能な項目を説明し、不足している入力を特定します。
AI向けの指示 →
03
動画をエクスポート
テキスト、画像、データを追加します。実行時の依存関係を確認し、エクスポート前にプレビューを確認して、編集可能なプロジェクトを後のために保管します。
Full creation tutorial →

WALKTHROUGH.motion → your video

アシスタントを選んで操作に従ってください。

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

ローカル制作ワークフロー

Claude desktop · Code tab; CLI alternative

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

作業モード: Claude desktop · Code tab; CLI alternative
推奨モデル: Choose an available model with the required tools; verify actual file and runtime access before production.

ワークフロー図解01 / 03

my-video.motionダウンロードしてオリジナルを保持

↓

あなた

このテンプレートを使って、動画づくりを始められるよう案内してください。

Claude Code

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.

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.
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.
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.
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.

これをテンプレートと一緒に送信

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.

ローカル制作ワークフロー

Codex local project / CLI

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

作業モード: Codex local project / CLI
推奨モデル: Choose an available model with the required tools; verify actual file and runtime access before production.

ワークフロー図解01 / 03

my-video.motionダウンロードしてオリジナルを保持

↓

あなた

このテンプレートを使って、動画づくりを始められるよう案内してください。

Codex

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.

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.
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.
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.
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.

これをテンプレートと一緒に送信

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.

ローカル制作ワークフロー

Cursor desktop · Agent

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

作業モード: Cursor desktop · Agent
推奨モデル: Choose an available model with the required tools; verify actual file and runtime access before production.

ワークフロー図解01 / 03

my-video.motionダウンロードしてオリジナルを保持

↓

あなた

このテンプレートを使って、動画づくりを始められるよう案内してください。

Cursor

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.

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.
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.
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.
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.

これをテンプレートと一緒に送信

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.

ローカル制作ワークフロー

豆包 desktop · work mode

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

作業モード: 豆包 desktop · work mode
推奨モデル: Choose an available model with the required tools; verify actual file and runtime access before production.

ワークフロー図解01 / 03

my-video.motionダウンロードしてオリジナルを保持

↓

あなた

このテンプレートを使って、動画づくりを始められるよう案内してください。

豆包

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.

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.
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.
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.
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.

これをテンプレートと一緒に送信

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.

ローカル制作ワークフロー

DeepSeek desktop · work mode

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

作業モード: DeepSeek desktop · work mode
推奨モデル: Choose an available model with the required tools; verify actual file and runtime access before production.

ワークフロー図解01 / 03

my-video.motionダウンロードしてオリジナルを保持

↓

あなた

このテンプレートを使って、動画づくりを始められるよう案内してください。

DeepSeek

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.

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.
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.
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.
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.

これをテンプレートと一緒に送信

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.

ローカル制作ワークフロー

TRAE desktop · SOLO mode

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

作業モード: TRAE desktop · SOLO mode
推奨モデル: Choose an available model with the required tools; verify actual file and runtime access before production.

ワークフロー図解01 / 03

my-video.motionダウンロードしてオリジナルを保持

↓

あなた

このテンプレートを使って、動画づくりを始められるよう案内してください。

TRAE

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.

Prepare this project
Create a folder for this video, add the .motion package and your assets, and open that folder in TRAE.
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.
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.
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.

これをテンプレートと一緒に送信

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.

ローカル制作ワークフロー

WorkBuddy desktop · selected workspace

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

作業モード: WorkBuddy desktop · selected workspace
推奨モデル: Choose an available model with the required tools; verify actual file and runtime access before production.

ワークフロー図解01 / 03

my-video.motionダウンロードしてオリジナルを保持

↓

あなた

このテンプレートを使って、動画づくりを始められるよう案内してください。

WorkBuddy

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.

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.
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.
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.
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.

これをテンプレートと一緒に送信

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.

ローカル制作ワークフロー

Kimi Code Desktop; CLI alternative

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

作業モード: Kimi Code Desktop; CLI alternative
推奨モデル: Choose an available model with the required tools; verify actual file and runtime access before production.

ワークフロー図解01 / 03

my-video.motionダウンロードしてオリジナルを保持

↓

あなた

このテンプレートを使って、動画づくりを始められるよう案内してください。

Kimi Code

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.

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.
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.
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.
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.

これをテンプレートと一緒に送信

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.

ローカル制作ワークフロー

Grok Build CLI; ordinary Grok chat needs a separate handoff

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

作業モード: Grok Build CLI; ordinary Grok chat needs a separate handoff
推奨モデル: Choose an available model with the required tools; verify actual file and runtime access before production.

ワークフロー図解01 / 03

my-video.motionダウンロードしてオリジナルを保持

↓

あなた

このテンプレートを使って、動画づくりを始められるよう案内してください。

Grok Build / Grok

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.

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.
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.
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.
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.

これをテンプレートと一緒に送信

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.

アシスタントのスクリーンショットや実際のエクスポートではなく、図解化されたワークフローです。パッケージの指示と現在使用中のツールに従って操作してください。

HANDOFF引き渡しテキスト

ファイルと一緒に送信

これはMotionGitテンプレートパッケージ（.motionファイル、ZIPコンテナ）です。
安全に新しいディレクトリに展開してください。motion.json、guide.json、README.mdの先頭にある「AI向け手順」、params.schema.jsonの順に読んでください。
パッケージのコードを直接実行しないでください。テンプレートの機能、置き換え可能な項目、実行環境の要件、不足している入力を私に教えてください。
仕様：https://motiongit.com/spec

実行環境要件と記録済みテスト

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 type	What it can do	Export requirements
Chat-only web or mobile assistant	Explain instructions and prepare copy and inputs	Export cannot be promised; hand off to a tool with execution capabilities
Desktop or CLI assistant with real file access, unpacking and commands	Inspect packages, edit content and run production steps	Must also support the package’s runtime.profile and rendering dependencies
The local renderer specified by the template	Read production instances and create previews and video	Follow 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 tool	Entry to use	Recommended model
Claude	Claude Code execution tasks, or a desktop Code / Cowork workspace with file and command tools	The most capable coding / Agent model available to you
ChatGPT / Codex	ChatGPT desktop local Work only when actual file and execution tools are available; a local Codex project is another entry	The most capable coding model available; use a higher reasoning setting when offered
Cursor	Open the production directory in Cursor Agent; approve file edits and terminal commands as needed	Choose the most capable coding / Agent model available to your account
GitHub Copilot	Start Copilot CLI in the production directory; use ask / execute mode for production	Choose the most capable coding / Agent model available to your account
Grok	Grok Build Agent environment with file and terminal tools; ordinary Grok chat can prepare content	The 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

初めて試す際に知っておくべきこと

添付の読み込みが終わらない、または未受信と言われる場合は？

アップロード完了後にファイル名、サイズ、外側の項目を確認してもらいます。サムネイルだけでは受信確認になりません。再送するかダウンロード画面の ZIP 互換ファイルを使い、.motion を再び ZIP に入れないでください。読めない場合は制作フォルダーにアクセスできるローカル助手を使います。クラウドのタスクは本機のパスを自動取得しません。

アシスタントが.motionを認識しない？

ZIPとして外側の項目だけを読み取り専用で確認します。00-START-HERE.mdとassistant/guide.jsonがあれば先に読み、同梱の入口に従ってください。元ファイルは保持し、個人識別情報や保護された内容を解凍しないでください。読めないファイルは速やかに報告します。

Skillをインストールする必要がありますか？

現在の個人用ダウンロードには制作入口が同梱されています。別のSkillやホストの取得、識別情報のコピーは不要です。作者向けのパッケージ化ツールとは区別し、実際のレンダリング依存関係はテンプレートの説明に従ってください。

ChatGPTデスクトップやウェブチャットでは？

まず公開説明から使い方を説明します。制作フォルダーに接続したローカル作業モードを優先し、実際にファイルを読めて実行できるか確認してください。クラウドのタスクは本機のパスやツールを自動で利用できません。チャットのみの場合は素材を整理して実行可能な環境へ渡します。

承認が失効した、またはファイルが読めない場合は？

完了していない操作を報告し、失効した要求を再利用しないでください。新しい要求は現在の操作に限定します。承認やサンドボックスを無効にせず、説明できる使用手順を速やかに伝えてください。

エクスポート結果がプレビューと異なる、またはテキストが収まらない？

正確なタイムスタンプ、テキスト、フレームを指定して、テンプレートのパラメータ範囲内で調整を依頼してください。エクスポートされた寸法、所要時間、音声、アセット、および会話内容を確認してください。

STARTfeatured