design-tools-import-conversationslisted

# import-conversations — the vwf design adapter Return what the user **said while designing** as a **vwf conversations payload**. You read from whichever design tool the named project uses and normalize; you never classify a remark, never route one, and never write a blueprint doc — those are vwf's, and `/vwf:feedback` does them. > **`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 harvest > 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 **one registry project** per call, and passes the canvas pins it holds for that project from `.config/vwf.yaml` — the per-platform `design.projects.<project>.*` uuids, and `design.design_system_id` when the call is for the product's design system rather than a project's screens. With no pin for a surface, report it in `notes` rather than searching the tool for something that looks close. **One project per call.** vwf iterates; you never harvest "the product". Since `config_format` 13 the tool is per project, so a product may design its website in one tool and its app in another — a call that spanned projects would have to resolve two tools at once and could only get one of them ri