<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/471b65c3d53341f79279ad487fa29835&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/471b65c3d53341f79279ad487fa29835-8687dedbe6b11247.gif</thumbnail_url><duration>494.199</duration><title>Create Webflow Stack, NPM Skill Scaffolder</title><description>This Loom introduces an npm scaffolding tool called Create Webflow Stack for quickly setting up Webflow MCP skills for site builds and migrations. The presenter demonstrates using npm create Signal Webflow Stack latest, then choosing a migration type such as Claude design to Webflow, which installs tools including the Webflow MCP skill and the migration-specific skills. They explain that a unique internal project name is required because Webflow MCP authentication is centralized at the system level, and they recommend installing skills at the project scope via symlinks. They also clarify the difference between bridge-accessible capabilities in the designer versus direct MCP access to the data API, noting that most actions are now supported in headless mode while some require manual or designer-assisted steps.</description></oembed>