designer-tools
starsforks
How to install designer-tools?
webflow/webflow-skills/designer-tools
$npx -y skills add webflow/webflow-skills --skill designer-toolsBuild and manage pages, elements, components, and styles in Webflow Designer. Use when adding sections, creating layouts, building elements, inspecting or updating components, viewing what's inside a component, restructuring pages, creating new pages, previewing page structure, s
SKILL.md
| 1 | # Page Structure |
| 2 | |
| 3 | Build, inspect, and manage page elements and components in the Webflow Designer. |
| 4 | |
| 5 | ## Important Note |
| 6 | |
| 7 | **ALWAYS use Webflow MCP tools for all operations:** |
| 8 | - Use Webflow MCP's `webflow_guide_tool` to get best practices **before any other tool call** |
| 9 | - Use Webflow MCP's `data_sites_tool` with action `list_sites` to identify the target site |
| 10 | - Use Webflow MCP's `data_pages_tool` with action `list_pages` to find the target page by name or slug — headless, works against any page |
| 11 | - Use Webflow MCP's `data_pages_tool` with action `create_page` to create new pages — headless |
| 12 | - Use Webflow MCP's `data_element_tool` with action `get_all_elements` or `query_elements` to retrieve or filter page elements — headless, pass the page's ID directly |
| 13 | - Use Webflow MCP's `data_element_builder` to create new elements — headless, pass the page's ID and a parent element ID |
| 14 | - Use Webflow MCP's `data_element_tool` with action `set_attributes`, `set_text`, `set_style`, or `set_link` to modify elements — headless |
| 15 | - Use Webflow MCP's `element_snapshot_tool` to get visual previews of elements before and after changes — this is a Designer tool and requires a Designer connection |
| 16 | - Use Webflow MCP's `data_style_tool` to create and update styles on elements — headless |
| 17 | - Use Webflow MCP's `webflow_guide_tool` to check supported style properties |
| 18 | - Use Webflow MCP's `data_component_tool` with action `get_all_components` or `query_components` to list site components — headless |
| 19 | - Use Webflow MCP's `data_component_tool` with action `get_component` to inspect a component's metadata — headless |
| 20 | - Use Webflow MCP's `data_element_tool` scoped with `scope_component_id` to inspect or edit a component's internal elements (its "content") — headless |
| 21 | - Use Webflow MCP's `data_component_props_tool` to manage prop definitions and set prop values on component instances — headless |
| 22 | - Use Webflow MCP's `data_component_variants_tool` to manage variants and per-variant style overrides — headless |
| 23 | - Use Webflow MCP's `data_component_tool` with action `insert_component_instance` or `unlink_component_instance` to manage component instances on a page — headless, not Designer-gated |
| 24 | - Use Webflow MCP's `designer_tool` only for actions that need a live canvas: `get_current_page`/`switch_page` (what's open in Designer right now), `select_element`/`get_selected_element` (interactive canvas selection), `create_page_folder` (page folders are Designer-only, unlike page creation itself), and `open_component_view` (viewing a component's canvas) |
| 25 | - DO NOT use any other tools or methods for Webflow operations |
| 26 | - All tool calls must include the required `context` parameter (15-25 words, third-person perspective) |
| 27 | - **Designer connection is required for `designer_tool` actions and for `element_snapshot_tool`.** Building, styling, inspecting, and updating elements, components, props, and variants (the `data_` tools) runs headlessly against an explicit page ID from `data_pages_tool`'s `list_pages` — but the before/after visual snapshots this skill relies on for safe mutation need Designer open and connected. If Designer isn't available, skip the snapshot steps and rely on `query_elements` output to describe changes instead. |
| 28 | |
| 29 | ## Instructions |
| 30 | |
| 31 | ### Phase 1: Discovery |
| 32 | 1. **Call `webflow_guide_tool` first** — always the first MCP tool call in any workflow |
| 33 | 2. **Get the site**: Use `data_sites_tool` with action `list_sites` to identify the target site. If only one site exists, use it automatically. |
| 34 | 3. **Get the target page**: Use `data_pages_tool` with action `list_pages` to find the page by name or slug — no Designer connection needed. If the user is actively working in an open Designer session and wants "the page I have open," use `designer_tool` with action `get_current_page` instead. |
| 35 | 4. **If user specifies a different page**: Just use that page's ID directly in later calls — no page "switch" is needed for headless operations. Only use `designer_tool` with action `switch_page` if the user wants the Designer canvas itself to navigate there. |
| 36 | 5. **Identify the task type**: |
| 37 | - **Inspect**: List elements, view structure, preview → go to Phase 2 |
| 38 | - **Build/Modify/Delete**: Add, update, restructure, remove → go to Phase 3 |
| 39 | - **Components**: |
People who liked this also viewed
6 picksType
- web-design-guidelinesReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".SkillsJul 2026
- lark-slides飞书幻灯片：创建和编辑幻灯片。创建演示文稿、读取幻灯片内容、管理幻灯片页面（创建、删除、读取、局部替换）。当用户需要创建或编辑幻灯片、读取或修改单个页面时使用。当用户给出 doubao.com 的 /slides/ URL/token 时，也应直接使用本 skill，不要因为域名不是飞书而回退到 WebFetch；路由依据是 URL 路径模式和 token，而不是域名。不负责：云文档内容编辑（走 SkillsJul 2026
- design-taste-frontendTaste-Skill - gives your AI good taste. stops the AI from generating boring, generic slop SkillsJul 2026
- ui-ux-pro-maxUI/UX design intelligence for web and mobile. Searchable local database with 84 styles, 192 color palettes, 74 font pairings, 192 product types, 98 UX guidelines, 104 icon entries, 16 GSAP motion presSkillsJul 2026
- caveman-helpQuick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".SkillsJul 2026
- codebase-designShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-nSkillsJul 2026
