Misaki Studio currently resolves 28 file kinds. A file's stored metadata or project path determines which workspace, actions, export behavior, and MCP operations apply; its extension does not.
File: Page · Identity: pages/* · Workspace: responsive visual canvas · MCP coverage: extensive visual/runtime tools
File: Component · Identity: components/*, except components/code/* · Workspace: responsive visual canvas · MCP coverage: extensive visual/runtime tools
File: Code Component · Identity: components/code/* · Workspace: Logic and Code · MCP coverage: source plus shared Component tools
File: Mockup · Identity: mockups/* · Workspace: screenless visual canvas · MCP coverage: visual tools; no runtime Preview/export
File: Document · Identity: documents/* · Workspace: rich-text block editor · MCP coverage: write/edit/embed tools
File: Document Page · Identity: metadata document-page · Workspace: route tree and SEO · MCP coverage: historical blog-* tool family
File: Content · Identity: metadata cms-content · Workspace: table Model/Data/Actions · MCP coverage: table tools with public View restrictions
File: Database table · Identity: database/*, except Users · Workspace: table Model/Data/Actions · MCP coverage: extensive table-* tools
File: Users · Identity: database/auth/users · Workspace: protected auth table · MCP coverage: table tools with protected-field rules
File: API · Identity: apis/* · Workspace: request/response schema · MCP coverage: API tools
File: Storage · Identity: storage/* · Workspace: shared state and API loader · MCP coverage: Storage tools
File: Script · Identity: scripts/* · Workspace: Logic and Code · MCP coverage: create/update/declare/read/call
File: Image collection · Identity: images/* · Workspace: SVG card grid · MCP coverage: generic reads; no dedicated mutation family
File: Colors · Fixed path: design-system/colors · Main capability: primitive, semantic, and alias color tokens · MCP coverage: shared and color tools
File: Fonts · Fixed path: design-system/fonts · Main capability: font Types and typography Templates · MCP coverage: shared and font tools
File: Images · Fixed path: design-system/images · Main capability: image/SVG Types and Templates · MCP coverage: shared and image tools
File: Font weights · Fixed path: design-system/font-weight · Main capability: numeric compatibility registry · MCP coverage: shared tools only; incomplete
File: Radius · Fixed path: design-system/radius · Main capability: reusable corner-radius sizes · MCP coverage: shared and radius tools
File: Spacing · Fixed path: design-system/spacing · Main capability: reusable spacing sizes · MCP coverage: shared and spacing tools
File: Themes · Fixed path: design-system/themes · Main capability: named theme contexts · MCP coverage: theme tools
File: Audios · Fixed path: design-system/audios · Main capability: uploaded/hosted sound registry · MCP coverage: shared and audio tools
File: Videos · Fixed path: design-system/videos · Main capability: hosted-video metadata and poster registry · MCP coverage: shared and video tools
File: Export settings · Identity: settings/export · Purpose: local/Git output destinations · MCP coverage: target tools and local export
File: Environment · Identity: settings/environment · Purpose: environment-variable matrix · MCP coverage: environment tools
File: Libraries · Identity: settings/libraries · Purpose: linked read-only projects · MCP coverage: library tools; File Explorer workspace
File: Legacy CMS Model · Identity: untyped cms/model/* · Purpose: old separate CMS schemas · MCP coverage: legacy tools; hidden from current creation
File: Legacy CMS Data · Identity: untyped cms/data/* · Purpose: old separate CMS datasets · MCP coverage: legacy tools; hidden from current creation
File: General · Identity: unmatched path/metadata · Purpose: safe row-preserving fallback · MCP coverage: generic reads/file actions
Misaki Studio checks explicit metadata types first, then more specific paths before broader paths. For example, Code Components are resolved before ordinary Components, and Users before ordinary Database tables.
Moving a file can change the kind its destination would imply. Ordinary moves/copies are refused across incompatible kinds so stored rows are not interpreted by the wrong editor. Pages, Components, Code Components, and Mockups use their explicit conversion workflow; unrelated file kinds are not interchangeable.
System files, structural roots, pages/index, and authentication files have additional File Explorer permissions. New names are normalized into path segments.
Edits inside a file normally use that file's transactional content model. Whole-file create, rename, move, duplicate, convert, and delete operations are project file-system actions and are not the same history as editing the file's contents. MCP undo/redo currently load design files, not every file kind.
Use current tool schemas rather than this index for exact parameters. See the UI-to-MCP capability map for cross-surface differences.