Webflow Code Component:Local Dev Setup logo

Webflow Code Component:Local Dev Setup

Organization
webflow
webflow-code-component:local-dev-setup

Initialize a new Webflow Code Components project from scratch. Creates project structure, installs dependencies, configures webflow.json, and sets up development environment.

Overview

Publisherwebflow
Repositorywebflow-skills
Skill namewebflow-code-component:local-dev-setup
Stars
122
Forks
18
Bundled files
1
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by webflow on GitHub. Read the source before you install it.

Installation

Install the Webflow Code Component:Local Dev Setup AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/webflow/webflow-skills.git /tmp/webflow-skills
mkdir -p .claude/skills
cp -r /tmp/webflow-skills/plugins/webflow-skills/skills/local-dev-setup .claude/skills/webflow-webflow-code-component-local-dev-setup
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Webflow Code Component:Local Dev Setup in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Webflow Code Component:Local Dev Setup on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Webflow Code Component:Local Dev Setup is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Local Dev Setup

Set up a new Webflow Code Components project from scratch.

When to Use This Skill

Use when:

  • Starting a brand new code components project
  • User asks to set up, initialize, or create a new project
  • Adding code components to an existing React project
  • Setting up the development environment for the first time

Do NOT use when:

  • Project already exists and is configured (just answer questions directly)
  • Creating individual components (use component-scaffold instead)
  • Deploying components (use deploy-guide instead)

Instructions

Phase 1: Assess Current State

  1. Check if project exists:

    • Is there an existing package.json?
    • Is there an existing webflow.json?
    • What's the current project structure?
  2. Determine setup type:

    • New project from scratch
    • Add to existing React project
    • Add to existing Next.js/Vite project

Phase 2: Project Initialization

  1. Create project structure (if new):

    • Initialize npm project
    • Set up TypeScript
    • Create folder structure
  2. Install dependencies:

    • Core: React, TypeScript
    • Webflow: CLI, data-types, react utils
    • Optional: Styling libraries

Phase 3: Configuration

  1. Create webflow.json:

    • Set library name
    • Configure component glob pattern
    • Set up globals if needed
  2. Configure TypeScript:

    • Set up tsconfig.json
    • Enable JSX support

Phase 4: Create Starter Files

  1. Create example component:

    • Simple Button component
    • Definition file
    • Basic styling
  2. Create globals file (optional):

    • For shared styles
    • For decorators

Phase 5: Verify Setup

  1. Verify bundle compiles:

    • Run npx webflow library bundle --public-path http://localhost:4000/ to catch build errors locally
    • This verifies your components, imports, and configuration are correct
    • Full testing in the Webflow Designer requires deploying with npx webflow library share
  2. Provide next steps:

    • How to create more components
    • How to deploy
    • Development workflow

Examples

For detailed step-by-step examples, see references/EXAMPLES.md.

Available examples:

  1. New Project from Scratch - Complete setup with React, TypeScript, and CSS Modules
  2. Add to Existing React Project - Integrate code components into an existing codebase
  3. With Tailwind CSS - Setup with Tailwind CSS support

Quick Start (New Project):

bash
# 1. Create project
mkdir my-webflow-components && cd my-webflow-components
npm init -y

# 2. Install dependencies
npm install react react-dom
npm install -D typescript @types/react @types/react-dom
npm install -D @webflow/webflow-cli @webflow/data-types @webflow/react

# 3. Create webflow.json
echo '{"library":{"name":"My Library","components":["./src/**/*.webflow.tsx"]}}' > webflow.json

# 4. Create component directory
mkdir -p src/components/Button

Then create your component files (.tsx, .webflow.tsx, .module.css). See Example 1 in references/EXAMPLES.md for complete file contents including component, definition, and CSS files.

Deploy with:

bash
npx webflow library share

Validation

After setup, verify the project is correctly configured:

CheckHow to Verify
webflow.json exists in project rootcat webflow.json
Dependencies installednpm list @webflow/webflow-cli
Bundle compiles without errorsnpx webflow library bundle --public-path http://localhost:4000/
At least one component foundCheck bundle output for "Found N component(s)"

Guidelines

Minimum Requirements

Every code components project needs:

  1. package.json with dependencies
  2. webflow.json with library config
  3. tsconfig.json (for TypeScript)
  4. At least one .webflow.tsx file

Recommended Structure

project/
├── src/
│   ├── components/
│   │   └── [ComponentName]/
│   │       ├── [ComponentName].tsx
│   │       ├── [ComponentName].webflow.tsx
│   │       └── [ComponentName].module.css
│   ├── hooks/           # Custom hooks
│   ├── utils/           # Utilities
│   ├── declarations.d.ts # CSS module types
│   ├── globals.ts       # Decorators/global imports
│   └── globals.css      # Global styles
├── package.json
├── tsconfig.json
├── webflow.json
└── .gitignore

Development Workflow

  1. Create component: Use component-scaffold skill
  2. Develop locally: Run React project to iterate (e.g., npm run dev)
  3. Validate: Use pre-deploy-check skill
  4. Deploy: Use deploy-guide skill or run npx webflow library share
  5. Test in Webflow: Add component to page in Designer

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Webflow Code Component:Local Dev Setup AI skill do?

Initialize a new Webflow Code Components project from scratch. Creates project structure, installs dependencies, configures webflow.json, and sets up development environment.

Why use Webflow Code Component:Local Dev Setup on TypingMind?

Because you install it once and use it with any model. Webflow Code Component:Local Dev Setup is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Webflow Code Component:Local Dev Setup in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/webflow/webflow-skills/tree/main/plugins/webflow-skills/skills/local-dev-setup. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Webflow Code Component:Local Dev Setup?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Webflow Code Component:Local Dev Setup?

As many as you like. As long as a model supports skills, you can use Webflow Code Component:Local Dev Setup with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Webflow Code Component:Local Dev Setup AI skill free?

Yes. It is published on GitHub by webflow under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇