Documents
Welcome
Introducing
Why Misaki Studio
Compare
Start Here
Learn
Workflows
Export & Ship
AI & MCP
Questions & Answers
Reference
Project interface reference
File types
Page file
Component file
Code Component file
Mockup file
Document file
Document Page file
Content file
Database table file
Users file
API file
Storage file
Script file
Image collection file
Colors file
Fonts file
Design-system Images file
Font Weights file
Radius file
Spacing file
Themes file
Audios file
Videos file
Export Settings file
Environment file
Libraries file
Legacy CMS Model file
Legacy CMS Data file
General file
Element types
Design properties
Keyboard shortcuts
MCP capabilities
Export output reference
Dependencies and compatibility
Browser versus desktop
Current limitations
Troubleshooting
Examples

General file

General is the safe fallback for stored rows whose metadata/path does not match a registered Misaki Studio file kind.

  • Property: Identity · Current behavior: any unmatched file path/metadata

  • Property: Workspace · Current behavior: no specialized center renderer

  • Property: Storage · Current behavior: generic BaseFile rows are preserved

  • Property: File actions · Current behavior: permitted generic rename/move/duplicate/copy/delete/path actions

  • Property: MCP · Current behavior: get-file-data and generic project file operations

  • Property: Content authoring · Current behavior: no dedicated tool family

Guidance and limits

No renderer does not mean empty or disposable. Inspect the raw rows and identify their producer/schema before changing anything. Do not coerce the content into a guessed typed format.

Moving into a recognized location would change the resolved kind, so the placement guard refuses incompatible moves. There is no specialized in-file Undo workflow because no editor is registered; project file actions have their own recovery boundary.

On this page
General file
Guidance and limits