design-tools-import-design-systemlisted

# import-design-system — the vwf design adapter Return the product's design system as a **vwf design-system payload**. You read from whichever design tool the project uses and normalize; you never write a blueprint doc, and you never decide what the design system *should* be. > **`invocation` must stay `both`.** vwf reaches this skill by delegation. > Flipping it to `user` removes the skill from the model's context and blocks > programmatic invocation — the call would not error, it would silently import > nothing. The payload shape is defined by the vwf adapter contract; read it before returning anything: `${CLAUDE_PLUGIN_ROOT}/../vwf/assets/design-adapter.md` (or the installed vwf plugin's `assets/design-adapter.md`). ## Inputs vwf names the **registry project** whose design system is being imported, and passes the pinned design-system id from `.config/vwf.yaml` (`design.design_system_id`) when one exists. With no pin, list what the tool can reach and ask the user to choose — never guess. ## 1. Resolve the project's design tool **The tool is per project, not per product.** A product may author its website's visual language in Lovable and its app's on the Claude Design canvas, so resolve against the registry project vwf named — never against "the product". Read `projects.<project>.design` in `.config/vwf.yaml`. That is the only key — there is no product-wide fallback. A config still carrying the pre-`13` `design.tool` is drift for `/vwf:setup`'s `12 → 13` migration to