dreamina-canvas-cli

Dreamina Canvas CLI public operations

When to use

This skill covers public commands and troubleshooting across modes. Installation is handled by dreamina-canvas-cli-setup , and accounts are handled by dreamina-canvas-cli-auth . The six generation skills each handle their own modes and parameters, and no auxiliary skills are created.

Operation contract

Item	Standard
Input and prerequisites	The selected public command and its required identity
Side effects	Model queries are read-only; canvas/upload/edit writes; runs may incur charges
Output handoff	JSON data / error、projectId、nodeId、resourceId、submitId
Recovery rules	For unknown writes, verify identity first; do not bypass an unclear result with a new ID

Workflow

Step 1: Run `dreamina-canvas --help`、`dreamina-canvas version`、`dreamina-canvas schema`, and read the contract corresponding to the current operation.

Step 2: Read one operation document from the table below as needed; verify the input, output, and side effects, then construct argv.

Step 3: Saving drafts and uploading do not represent approval to generate; before paying, read execution, and for existing tasks read recovery.

Step 4: Separate stdout/stderr according to `--format json` , and recover based on requiredAction. For exit code 20, continue querying with the original submitId.

Step 5: Record the final state and artifact verification; clearly report stages that were not run.

Progressive disclosure (read as needed): atomic operation index

When constructing argv, determining stdout/stderr, persisting identity, or verifying before delivery, read Parameter construction, output, identity, and acceptance。
When selecting a model/voice or checking aspect ratio, resolution, or duration allowlists, read Model, voice, and capability discovery。
When creating a canvas, switching the current canvas, or continuing work across processes by projectId, read Canvas creation and listing。
When uploading local assets, querying artifacts, or downloading and verifying hashes, read Asset upload, query, and download。
When editing image nodes or handling node:/res: references, read Image node sharing mechanism and editing。
When editing video nodes or handling modes and references, read Video node sharing mechanism and editing。
When creating/editing audio nodes (tts and music fields are mutually exclusive), read Audio node sharing mechanism and editing。
When Text/Element nodes, node lookup, or DAG dependency order are needed, read Text, Element, node lookup, and dependency order。
When arranging a timeline, replacing tracks, or assembling audio and video, read Timeline and track replacement。
When quotes, user approval, generation submission, or batch identity are needed, read Quotes, confirmation, runs, and batch identity。
When a task is running, local waiting times out, or recovery by the original identity is needed, read Query, wait, and recovery。
When chaining "query model -> create canvas -> upload assets -> reference nodes" in one go, read Combined scenarios for preparing canvas and assets。
When a command exits with a non-zero code and the next action needs to be determined, read Exit codes and requiredAction。

Scenario examples

Rules

The specification for a command is maintained only in the corresponding references; examples are used for composition and do not define a second set of parameter contracts.
Install the missing skill from the same package:npx skills add full-aigc-skills/dreamina-skills --skill <skill-name>. Hand over by name, do not read adjacent installation directories.
Do not store credentials, do not approve credits on behalf of the user, and do not treat an uncertain submission as a failure and resubmit it.

Validation checklist

Parameters are consistent with the current schema; projectId/nodeId/submitId are each correct.
There is evidence for the draft, submitted, successfully completed, and downloaded states respectively.
Exception recovery reuses the identity, and file byte count and SHA-256 are verified.

Gotchas

A wait timeout does not cancel the server-side task.
Editing generation parameters may clear references that were not passed; timeline replacement rebuilds tracks, so check existing content first.
--yes It cannot replace credit approval for a specific request.

Progressive disclosure (read on demand): supplementary contracts and checklists

When you need the complete contract for the audio field and mode mutual exclusion, read audio-node-audio-node-contract。
When canvas context and identity ownership are unclear under multiple profiles, read canvas-canvas-context。
When you need the seed contract for the full CLI command family (version, flags, exit codes), read cli-contract。
When you need node dependency order and DAG scheduling details, read composition-composition-dag。
When you need the complete capability discovery fields and boundary descriptions, read discovery-capability-discovery。
When errors are hard to classify or you need a recovery playbook, read error-recovery。
When you need credit limits, approval semantics, and batch identity details, read execution-credit-approval。
When you need the complete contract for image node fields and the reference mechanism, read image-node-image-node-contract。
When you need the complete transitions of the task recovery state machine, read recovery-recovery-state-machine。
When you need the detailed rules for artifact byte count and SHA-256 verification, read resources-artifact-verification。
When you need resource upload flag bits and idempotency details, read resources-resource-upload。
When you need the complete contract for timeline tracks and clip parameters, read timeline-timeline-contract。
When checking item by item before delivery, read validation-checklist。
When you need the complete contract for video node modes and the reference mechanism, read video-node-video-node-contract。
When you need the skill-level workflow contract (states, handover, authorization), read workflow-contract。

Non-applicability and boundaries

Specific generation modes do not apply this entry point as a second set of parameter specifications; please choose the six corresponding task skills. Installation and login are handled by setup/auth respectively; do not automatically reinstall or switch accounts just because a single read-only command fails.

Read only the account and asset information necessary for the current operation; do not store, record, or output access tokens, cookies, or temporary signed links.