The fixed Libraries file stores linked Misaki projects whose Components and supported design-system values are mounted read-only in the current project.
Property: Path · Current behavior: settings/libraries
Property: Workspace · Current behavior: synthetic LIBRARIES File Explorer tree; no center renderer
Property: Source access · Current behavior: foreign/read-only
Property: Consumer edits · Current behavior: instance props/placement in current project
Property: MCP · Current behavior: list/link/unlink libraries and enumerate reusable IDs
Property: Sync · Current behavior: mounted sources can update from their owning project
Right-click LIBRARIES → Add, choose a project, then expand it. With a project-owned visual file open, use a linked Component's Add to open page action. Remove/unlink from the linked project menu.
MCP uses list-libraries, link-library, and unlink-library. Returned token and Component UUIDs can be supplied directly to supported consumer operations. A project cannot link itself; duplicate links are ignored.
Link configuration persists/synchronizes but is a project-level operation rather than ordinary selected-file authoring. Instance placement is a separate design-file transaction. Unlinking makes dependent tokens unresolved and Component instances show a missing source; inspect usage first.
An inaccessible source can remain listed as unavailable. Edit library source only in its owning project.