Manage Design Style

For update: JSON string of a partial DesignSpec (same shape as designSpec — see "# designSpec shape"). Merge semantics per the description's field rules: colors/fonts merge by `role` (fonts fall back to `family`); ⚠️ logos / images / styleGuide REPLACE wholesale — to add one, `g…

User library: list, get, create, update, apply, clear, delete. Catalog: list_presets, apply_preset. Supported actions: list, get, create, update, apply, clear, delete, list_presets, apply_preset.

For list_presets (optional): user's chat language code (e.g. 'zh', 'en', 'es'). Catalog preset names/descriptions are stored with English canonical + locale overrides; passing the user's language returns localized text. Defaults to English if omitted.

For update: new name to rename the design style to. Can be combined with `patch` in the same call.

For delete only: set to true ONLY after the user has confirmed the deletion. Omit on first call to trigger the confirmation_required protocol.

For apply_preset (required): the catalog preset UUID returned by list_presets. The backend pins the project's designStyleId FK directly at this catalog row — no clone is made until the user actually edits the spec.

For list_presets (optional): scenario tag to narrow the catalog by. Catalogs tag themselves with applicableScenarios for recommendation / selection; omit to list all visible catalog presets.

Existing project ID from the editor URL or list_projects. Pass this when continuing work on an existing project and the external MCP session is not already targeted.

For create: JSON string of a DesignSpec. The exact shape, field rules, and role conventions are in this tool's description under "# designSpec shape" — follow them verbatim. Core rule: every element carries one `role` label saying what it's FOR, not what it looks like.

For create / update: optional UI cover image URL for the Design Style library / picker. This is not part of designSpec and is not used as a generation reference. Pass null on update to clear it.

For update only: set to true after the user has confirmed it's OK to edit a design style used by multiple projects. Omit on first call so the confirmation_required response can surface the impact.