Use project libraries

Link another accessible Misaki Studio project as a live, read-only source of Components and design-system values. Consumers can place instances and use exposed tokens without copying the source into the current project.

Coverage: UI + MCP for linking, listing, unlinking, and consuming supported values. Source library files remain read-only in the consumer.

Before you link

Choose a library project with intentional public contracts and stable design-system identities. Confirm that the consumer has access and that the source is available in the current environment.

Library entries are stored in the fixed settings/libraries file, but management appears in the File Explorer's synthetic LIBRARIES tree rather than a dedicated center workspace.

Link in the UI

1. Right-click LIBRARIES and choose Add.

2. Select the source project.

3. Expand the mounted project and inspect its Components and design-system files.

4. With a project-owned Page, Component, or Mockup open, use Add to open page on a linked Component.

5. Configure the new instance through the source Component's exposed contract.

The linked file is foreign/read-only. You can edit the instance's parent-owned placement and supplied props, but not the source hierarchy from the consumer project.

Link through MCP

In the Website project, call list-projects and show the exact project ID for <library project>. Link it only if the name and ID match, then call list-libraries and summarize the mounted Components, colors, images/SVGs, radius, spacing, and fonts. Do not place an instance or change a token yet.

Use link-library with the returned project UUID, then list-libraries for current reusable IDs. Those IDs can be passed directly to the relevant Component-instance or style/token operation; there is no separate copy/import step.

To place a Component:

In the selected Website project, inspect <parent design-file reference> and the linked library list. Add one instance of library Component <exact path/UUID> inside <parent element reference>, supply <props/variant/children>, and preserve every existing sibling. Verify the instance reference, Preview, and generated imports. Do not modify or unlink the library.

Update and dependency behavior

Mounted libraries are live references. Changes from the source can flow into the consumer's mounted view and affect instances or tokens. Review source contract changes before accepting them in important consumers.

If the library cannot mount because access or availability changed, it remains listed as unavailable. An unlinked Component instance falls back to a missing-component presentation because its source no longer resolves.

Verify reuse

• confirm the exact linked project UUID and displayed name;

• inspect the mounted/reachable status;

• verify every selected token or Component ID comes from the intended library;

• preview the consumer across affected themes, variants, and screens;

• inspect generated imports and dependencies;

• test behavior after a representative source update;

• identify every consumer before unlinking.

Undo and side effects

Link/unlink changes project-level library configuration, not the active design file's ordinary content stack. Exact UI undo presentation still needs runtime verification. Instance placement is a separate design-file content edit.

Unlinking can break all dependent tokens and Component instances. Treat it as a dependency change: inspect usage, obtain confirmation, unlink, and verify the complete project.

Current limits

• A project cannot link itself.

• The source project must be accessible and mountable.

• Foreign source content is read-only from the consumer.

• A library Component needs a project-owned visual file open for the UI placement command.

• Linking the same project twice is ignored.