design-tools-import-screenslisted

# import-screens — the vwf design adapter Return one flow's designed screens, for one platform, as a **vwf screens payload**. You read from whichever design tool the project uses and normalize; you never diff, never decide what a delta means, and never touch a blueprint doc. > **`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 `$ARGUMENTS` is `<flow> <platform>` — the flow folder name (`<NNN>-<flow-slug>`) and one of `mobile` / `tablet` / `desktop` / `web` / `auto`. vwf also passes the **registry project** the flow belongs to, plus whatever pins that tool needs (for Claude Design, `design.projects.<project>.<platform>`). ## 1. Resolve the project's design tool **The tool is per project, not per product.** One product may design its website in Lovable and its mobile app 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