All skills
webflow avatar

/figma-to-webflow

@ea781d9 official
by webflowwebflow/webflow-skills126 stars
21

Build a Webflow page, section, component, or full site from a Figma design using the Figma MCP and the Webflow MCP (Designer Bridge + Data API). Use whenever translating a Figma file/frame into Webflow, building directly in a Webflow project, or implementing a design as live Webflow elements/styles (not a copy-paste fragment). Triggers: "build this Figma in Webflow", "Figma to Webflow", "implement this design in Webflow", a figma.com URL + a Webflow site, "recreate this in my Webflow project".

  • 5 files
  • 26.8 KB
  • Updated 3 months ago
  • GitHub

Use this Skill: https://skilld.dev/gh/webflow/webflow-skills/figma-to-webflow

This session only. Nothing lands on disk.

referencesnavbar.md

≈628 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Navbar

Read this before building a navigation bar.

Webflow's native Navbar component cannot be created via API/WHTML. WHTML can produce generic blocks with w-* class names, but not the real component JS/CSS. Build a semantic custom nav or ask the user to add the native element in Designer.

Required Prompt

Ask which breakpoint should collapse to hamburger:

  • 3-4 short links, no/short CTA: recommend mobile landscape (767) or mobile portrait (479).
  • 5+ links, long labels, or prominent CTA: recommend tablet (991) so the bar does not crowd.

State the recommendation and reason, then use the user's choice.

Structure

Build with custom tags so it is semantic and Designer-editable:

<nav class="nav">
  <div class="nav-inner">
    <a class="nav-brand" href="/">...</a>
    <input type="checkbox" id="nav-toggle" class="nav-cb">
    <label for="nav-toggle" class="nav-burger">
      <span class="nav-burger-bar"></span>
      <span class="nav-burger-bar"></span>
      <span class="nav-burger-bar"></span>
    </label>
    <div class="nav-menu">
      <a class="nav-link" href="#">...</a>
      <a class="btn" href="#">CTA</a>
    </div>
  </div>
</nav>

The checkbox must be a previous sibling of .nav-menu so :checked ~ .nav-menu works. Order: brand, checkbox, burger, menu.

Make .nav or .nav-inner position:relative so the dropdown anchors to the bar. Use custom-tag input / label, not the Form Checkbox element, because Webflow's .w-checkbox wrapper breaks the sibling chain.

Behavior

Keep desktop visual styling as normal Webflow classes. Put CSS-only responsive/toggle behavior in one component-scoped HtmlEmbed inside the nav root, so it travels if converted to a component. Do not use JavaScript for custom navbar behavior.

<style>
  .nav-cb{ position:absolute; width:1px; height:1px; opacity:0; pointer-events:none; }
  .nav-burger{ display:none; }
  @media screen and (max-width:{BP}px){
    .nav-burger{ display:flex; flex-direction:column; row-gap:5px; cursor:pointer; }
    .nav-menu{
      display:none; position:absolute; top:100%; left:0; right:0;
      flex-direction:column; align-items:flex-start; row-gap:4px;
      padding:16px 24px; background:#fff; box-shadow:0 10px 24px rgba(0,0,0,.10);
    }
    .nav-cb:checked ~ .nav-menu{ display:flex; }
  }
</style>

Pure CSS is zero-JS and publish-safe. It does not set aria-expanded or close on outside click; tell the user that tradeoff rather than adding JavaScript.

Source: SKILL.md on GitHub

No third-party reports yet.

Signed by skilld at ea781d9. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 3 months ago

README badge

README badge for webflow/webflow-skills/figma-to-webflow