Choose the correct asset surface before adding artwork, sound, or video. Misaki Studio has a tokenized Design-system Images registry, an older freeform SVG Image collection, an Audio registry used by timelines and actions, and a Video registry that does not yet have a native canvas Video node.
Need: reusable SVG/image token with theme/template support · File: design-system/images · Current result: selectable design-system image reference
Need: simple freeform collection of pasted SVG rows · File: file below images/ · Current result: stable row ID, UI-managed collection
Need: reusable uploaded or hosted sound · File: design-system/audios · Current result: usable by timelines and Play Sound logic
Need: reusable hosted video metadata and poster · File: design-system/videos · Current result: registry only; no native canvas Video node yet
Design-system Images and the older Image collection are different file kinds even though both display images.
Open Design System → Images.
Choose TYPES for fixed source items or TEMPLATES for theme/layer-resolved references.
Add an Image or Section.
Upload or paste supported artwork on a Type item.
Configure the selected item in Props, including supported aspect-ratio behavior.
Use the returned token from an image/SVG element or supported style field.
Preview every relevant theme when a Template is involved.
Only Templates participate in theme/layer resolution. Type images remain fixed.
Open Design System → Audios.
Add an Audio item and give it an intentional name.
Use Upload Audio for a project blob or Set URL for a hosted source.
Confirm duration and source information.
Select the stable Audio ID in a timeline lane or Play Sound action.
Preview playback and test exported asset resolution.
Use one effective source. An empty Audio row is not offered in asset pickers.
Add a Video item with a hosted URL and optional poster from Design-system Images. Video is URL-based rather than uploaded; hosted media should support byte-range requests for reliable seeking.
The registry can store dimensions, MIME type, duration, and poster identity, but there is currently no native canvas Video element that renders this token. Treat video placement as unfinished.
In the
Websiteproject, inspect the current Design-system Images, Audios, and Videos files. Add or reuse<asset>in the correct registry, using<safe source>and name<name>. Preserve every section and item. Return the stable token ID and show where it can currently be consumed. Verify Preview/export asset resolution where supported. Do not upload private media, replace a blob, delete a token, or claim native Video placement.
MCP provides image Type/Template, Audio, Video, and shared design-system operations. It does not provide a complete dedicated mutation family for the older images/* collection; manage that collection in its UI or inspect only its raw file data.
distinguish stable IDs from current card order or display position;
check theme/layer resolution for Image Templates;
test aspect ratio, intrinsic size, and missing-asset fallback;
verify uploaded blobs remain available to project export;
verify external URLs, CORS, access, and byte-range support where relevant;
test Audio duration and playback from the actual timeline/action;
inspect generated paths and the final destination.
Token metadata and asset references are persisted/undoable file rows. Uploading also creates blob data, while an external URL remains controlled by another server. File undo does not restore an expired or removed remote asset.
Deleting a token can break every consumer. Search current references and verify generated output before removal.
The older Image collection accepts textual SVG markup, not arbitrary bitmap upload, and has no dedicated production MCP mutation family.
A card number in that collection is not its stable asset ID.
Missing project blobs and unreachable URLs cannot render or play.
Video items are registry references only; native canvas Video placement is unfinished.