webflow-code-component:deploy-guide
Step-by-step guide for deploying Webflow Code Components to a workspace. Covers authentication, pre-flight checks, deployment execution, and verification.
What this skill does
# Deploy Guide
Guide users through deploying their code component library to Webflow.
## When to Use This Skill
**Use when:**
- User is ready to deploy components to Webflow
- User asks how to share, publish, or deploy their library
- First-time deployment to a workspace
- Step-by-step deployment walkthrough needed
**Do NOT use when:**
- Deployment failed (use troubleshoot-deploy instead)
- Just validating before deploy (use pre-deploy-check instead)
- Setting up local development (use local-dev-setup instead)
**Note:** The CLI command is `webflow library share`. This skill uses "deploy" as the user-facing term.
## Instructions
### Phase 1: Pre-Flight Checks
1. **Verify project is ready**:
- Check webflow.json configuration
- Ensure all dependencies installed
- Run pre-deploy-check skill checks
2. **Check authentication status**:
- Look for existing .env with API token
- Verify WEBFLOW_WORKSPACE_API_TOKEN if set
- Prepare for authentication if needed
3. **Confirm deployment target**:
- Which workspace?
- New library or update existing?
### Phase 2: Authentication
4. **Guide authentication**:
- Interactive: Follow CLI prompts
- CI/CD: Use --api-token flag
- Show how to get workspace API token if needed
### Phase 3: Deployment
5. **Execute deployment**:
- Run `npx webflow library share`
- Monitor for errors
- Capture output
### Phase 4: Verification
6. **Verify deployment**:
- Check Webflow Designer for components
- Test component functionality
- Confirm all components appear
7. **Provide next steps**:
- How to use components in Designer
- How to update in future
- Common post-deploy tasks
- If deployment fails, use [troubleshoot-deploy](../troubleshoot-deploy/SKILL.md) to diagnose and fix issues
## Deployment Workflow
### Standard Deployment
```
๐ฆ Deploying Code Components
Step 1: Pre-flight checks
โโโ webflow.json โ
โโโ Dependencies โ
โโโ Build test โ
Step 2: Authentication
โโโ Checking for existing auth...
โโโ Found valid token โ
Step 3: Deploying
โโโ Bundling components...
โโโ Uploading to workspace...
โโโ Processing...
Step 4: Verification
โโโ Library registered โ
โโโ 4 components available โ
๐ Deployment Complete!
```
### CI/CD Deployment
```bash
# Set environment variable
export WEBFLOW_WORKSPACE_API_TOKEN=your-token-here
# Deploy without prompts
npx webflow library share --no-input
```
## Examples
**User prompt:**
```
Deploy my components to Webflow
```
**Response:**
```
๐ Deploy Guide: Code Components
Let me guide you through deploying your component library.
---
## Step 1: Pre-Flight Checks
Running validation...
โ
webflow.json configured
โ
Dependencies installed
โ
Build succeeds
โ
Bundle size: 2.3MB (under 50MB limit)
All checks passed! Ready to deploy.
---
## Step 2: Authentication
**Option A: Interactive (Recommended for first time)**
Run the deploy command:
```bash
npx webflow library share
```
This will:
1. Open your browser for Webflow login
2. Ask you to authorize the app
3. Save credentials to .env
**Option B: API Token (For CI/CD or returning users)**
1. Get your Workspace API Token:
- Go to Webflow Dashboard
- Navigate to your Workspace Settings
- Find "Apps & Integrations" โ "Manage"
- Under "Workspace API Access", click "Generate API Token"
- Copy the token
2. Run with token:
```bash
npx webflow library share --api-token YOUR_TOKEN_HERE
```
Or set environment variable:
```bash
export WEBFLOW_WORKSPACE_API_TOKEN=YOUR_TOKEN_HERE
npx webflow library share
```
---
## Step 3: Deploy
Ready to deploy? Run:
```bash
npx webflow library share
```
Expected output:
```
โ Bundling components...
โ Authenticating...
โ Uploading library...
โ Processing...
Library "My Component Library" successfully shared!
Components:
- Button
- Card
- Accordion
- Modal
View in Designer: Open any site in your workspace
```
---
## Step 4: Verify in Designer
After deployment:
1. **Open Webflow Designer** for any site in your workspace
2. **Open Add Panel** (A key or + button)
3. **Find "Components"** section
4. **Look for your library** under custom components
5. **Drag a component** onto the canvas to test
---
## Step 5: Next Steps
โ
**Your components are live!**
**To update components later:**
```bash
# Make your changes, then re-deploy
npx webflow library share
```
**Important notes:**
- Updates replace the entire library (no partial updates)
- Existing component instances will update automatically
- Don't rename .webflow.tsx files (breaks instances)
---
๐ก **Tips:**
- Add .env to .gitignore to protect your token
- Use `--verbose` flag for debugging issues
- Run `npx webflow library log` to see recent deploy logs
```
---
**Example: First-Time Setup**
```
๐ Deploy Guide: First-Time Setup
I see this is your first deployment. Let me walk you through the full setup.
---
## Step 1: Get Workspace API Token
You'll need a Workspace API token to deploy:
1. **Open Webflow Dashboard**
Go to webflow.com and log in
2. **Navigate to Workspace Settings**
Click your workspace name โ Settings
3. **Find API Access**
Go to "Apps & Integrations" โ "Manage"
4. **Generate Token**
Under "Workspace API Access":
- Click "Generate API Token"
- Copy the token (you won't see it again!)
5. **Save Token**
Add to your .env file:
```
WEBFLOW_WORKSPACE_API_TOKEN=your-token-here
```
โ ๏ธ Add .env to .gitignore:
```bash
echo ".env" >> .gitignore
```
---
## Step 2: Deploy
Now run:
```bash
npx webflow library share
```
The CLI will:
1. Read your token from .env
2. Bundle your components
3. Upload to your workspace
---
## Step 3: Verify
After successful deploy:
1. Open Webflow Designer
2. Press 'A' to open Add panel
3. Find your components in the Components section
4. Drag onto canvas to test
---
๐ **First deployment complete!**
Future deployments are simpler:
```bash
# Just run this after making changes
npx webflow library share
```
```
---
**Example: CI/CD Setup**
```
๐ Deploy Guide: CI/CD Setup
Setting up automated deployments for your pipeline.
---
## GitHub Actions Example
Create `.github/workflows/deploy.yml`:
```yaml
name: Deploy to Webflow
on:
push:
branches: [main]
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: '20'
cache: 'npm'
- name: Install dependencies
run: npm ci
- name: Deploy to Webflow
env:
WEBFLOW_WORKSPACE_API_TOKEN: ${{ secrets.WEBFLOW_WORKSPACE_API_TOKEN }}
run: npx webflow library share --no-input
```
---
## Add Secret to GitHub
1. Go to your repo โ Settings โ Secrets and variables โ Actions
2. Click "New repository secret"
3. Name: `WEBFLOW_WORKSPACE_API_TOKEN`
4. Value: Your workspace API token
5. Click "Add secret"
---
## Key Flags for CI/CD
```bash
npx webflow library share --no-input
```
- `--no-input`: Disables interactive prompts
- Uses `WEBFLOW_WORKSPACE_API_TOKEN` env var automatically
---
## Optional: Add TypeScript Check
```yaml
- name: Type check
run: npx tsc --noEmit
```
---
โ
**CI/CD configured!**
Now every push to main will automatically deploy your components.
```
## Validation
After deployment, verify success with these checks:
| Check | How to Verify |
|-------|---------------|
| Deploy completed | `npx webflow library share` exited without errors |
| Components visible | Open Designer Add panel โ find your library |
| Import logs clean | `npx webflow library log` shows successful import |
| Bundle size OK | Output shows bundle under 50MB |
| Props work | Drag component onto canvas, verify props in right panel |
## Guidelines
### Terminology
The CLI command is `webflow library share`. This skill uses "deploy" as the user-facing term for consistency with common developer vocabulary. See the [CLI reference](../../rRelated in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context โ no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes โ information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development โ guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.