webflow-cli:troubleshooter
Diagnose and fix Webflow CLI issues including installation problems, authentication failures, build errors, and bundle problems. Uses CLI diagnostic flags (--version, --help, --verbose, --debug-bundler) for troubleshooting.
What this skill does
# Webflow CLI Troubleshooter
Diagnose and resolve Webflow CLI issues with diagnostic commands and automated fixes.
## Important Note
**ALWAYS use Bash tool for all diagnostic operations:**
- Execute diagnostic commands via Bash tool
- Use Read tool to examine configuration files
- Verify CLI installation: `webflow --version`
- Check authentication: `webflow auth login` (if needed)
- Use CLI diagnostic flags: `--verbose`, `--debug-bundler`, `--help`
- DO NOT use Webflow MCP tools for CLI workflows
- All CLI commands require proper descriptions (not context parameters)
**Package Manager Detection:**
- Check for lock files: `package-lock.json` (npm), `pnpm-lock.yaml` (pnpm), `yarn.lock` (yarn)
- If no lock file found, ask user which package manager to use (npm/pnpm/yarn)
- Use detected package manager for all install/build commands
## Instructions
### Phase 1: Issue Identification
1. **Ask user to describe issue**: What command failed or what error occurred
2. **Determine error category**:
- CLI not installed or wrong version
- Authentication failed
- Build/bundle failed
- Command not recognized
3. **Capture error message**: Get exact error output
### Phase 2: Run Diagnostics
4. **Check CLI installation**: Run `webflow --version`
5. **Check authentication**: Run `webflow auth login` if needed
6. **Run command with --verbose**: Execute failed command with `--verbose` flag for detailed output
7. **Use --debug-bundler** (if bundle issue): Run with `--debug-bundler` flag to see bundler config
8. **Check --help**: Run `webflow <command> --help` to verify command syntax
### Phase 3: Analyze & Fix
9. **Identify root cause**: Parse error messages and diagnostic output
10. **Present fix**: Show specific solution based on CLI error
11. **Apply fix**: Execute fix commands
12. **Verify**: Re-run original command to confirm resolution
## Examples
### Example 1: CLI Not Installed
**User prompt:**
```
Getting "webflow: command not found"
```
**Diagnostics:**
```
๐ Checking CLI Installation
Executing: webflow --version
Error: bash: webflow: command not found
โ Webflow CLI not installed
```
**Fix:**
```
๐ Fix: Install Webflow CLI
Executing: npm install -g @webflow/cli
โ CLI installed
Verifying...
Executing: webflow --version
Output: @webflow/cli/1.5.2
โ
Issue resolved
```
### Example 2: Build Failed
**User prompt:**
```
Build is failing but I don't know why
```
**Diagnostics:**
```
๐ Running Build with Diagnostics
Executing: webflow library bundle --verbose
Output:
[verbose] Loading webflow.json
[verbose] Found library config
[verbose] Building components from ./src/**/*.webflow.tsx
[verbose] Running bundler
Error: Failed to resolve import './missing-file.ts'
โ Build failed: Missing import file
```
**Fix:**
```
๐ Fix: Missing Import
Issue: Component imports './missing-file.ts' which doesn't exist
Solutions:
1. Create the missing file
2. Fix the import path
3. Remove the import if not needed
Check your component imports and ensure all files exist.
```
### Example 3: Bundle Configuration Issue
**User prompt:**
```
Bundle is failing with webpack errors
```
**Diagnostics:**
```
๐ Checking Bundle Configuration
Executing: webflow library bundle --debug-bundler
Output:
[debug-bundler] Final bundler configuration:
{
"entry": "./src/Component.tsx",
"output": {
"path": "/dist",
"filename": "bundle.js"
},
"resolve": {
"extensions": [".ts", ".tsx", ".js"]
}
}
Error: Module not found: Can't resolve 'styled-components'
โ Bundle failed: Missing dependency
```
**Fix:**
```
๐ Fix: Install Missing Dependency
Executing: npm install styled-components
โ Dependency installed
Retrying bundle...
Executing: webflow library bundle
โ Bundle created successfully
โ
Issue resolved
```
## Guidelines
### CLI Diagnostic Commands
**Version Check:**
```bash
webflow --version
# or
webflow -V
```
**Command Help:**
```bash
webflow --help # General help
webflow library --help # Library commands help
webflow library bundle --help # Specific command help
```
**Verbose Output:**
```bash
# Add --verbose to any command for detailed debugging
webflow library bundle --verbose
webflow cloud deploy --verbose
webflow extension bundle --verbose
```
**Debug Bundler:**
```bash
# Show final bundler configuration
webflow library bundle --debug-bundler
webflow extension bundle --debug-bundler
```
### Common Issues & Fixes
**Issue: CLI Not Found**
- **Diagnostic:** `webflow --version` fails
- **Fix:** `npm install -g @webflow/cli`
- **Verify:** `webflow --version` shows version
**Issue: Wrong CLI Version**
- **Diagnostic:** `webflow --version` shows old version
- **Fix:** `npm update -g @webflow/cli`
- **Verify:** Latest version installed
**Issue: Command Not Recognized**
- **Diagnostic:** "Unknown command" error
- **Fix:** Check command with `webflow --help`
- **Verify:** Use correct command syntax
**Issue: Authentication Failed**
- **Diagnostic:** "Not authenticated" error
- **Fix:** `webflow auth login`
- **Verify:** Authentication succeeds
**Issue: Build Failed**
- **Diagnostic:** Run with `--verbose` flag
- **Fix:** Fix errors shown in verbose output
- **Verify:** Build succeeds
**Issue: Bundle Configuration Error**
- **Diagnostic:** Run with `--debug-bundler` flag
- **Fix:** Adjust bundler config in webflow.json
- **Verify:** Bundle succeeds
**Issue: Missing Dependencies**
- **Diagnostic:** "Module not found" errors
- **Fix:** `npm install` or install specific package
- **Verify:** Build/bundle succeeds
**Issue: Corrupted node_modules**
- **Diagnostic:** Unexplained build failures
- **Fix:** `rm -rf node_modules && npm install`
- **Verify:** Build succeeds
### Error Handling
**CLI Not Installed:**
```
โ Webflow CLI Not Found
Install:
npm install -g @webflow/cli
Verify:
webflow --version
Docs: https://developers.webflow.com/cli
```
**Authentication Required:**
```
โ Authentication Failed
Fix:
webflow auth login
Follow browser prompts to authenticate
```
**Build/Bundle Failed:**
```
โ Build Failed
Run with diagnostics:
webflow library bundle --verbose --debug-bundler
This shows:
- Detailed build steps
- Import resolution
- Bundler configuration
- Exact error location
Fix the errors shown in output
```
**Unknown Error:**
```
โ Unknown Issue
Gather info:
1. What command are you running?
2. Run command with --verbose flag
3. Check command syntax with --help
4. Share full error output
This helps identify the specific problem
```
### File Operations
**Reading Config Files:**
```
# View webflow.json
Read: webflow.json
# View package.json
Read: package.json
# View build output
Read: dist/
```
**Discovering Files:**
```
# Find config files
Glob: **/webflow.json
# Find components
Glob: src/**/*.webflow.tsx
# Find logs
Glob: **/*.log
```
### Best Practices
**Always Start With:**
1. Check CLI version: `webflow --version`
2. Check command syntax: `webflow <command> --help`
3. Run with verbose: Add `--verbose` flag
**For Build/Bundle Issues:**
1. Use `--verbose` for detailed output
2. Use `--debug-bundler` to see config
3. Check import paths
4. Verify dependencies installed
**For Authentication Issues:**
1. Run `webflow auth login`
2. Follow browser prompts
3. Verify workspace access
**For Installation Issues:**
1. Check Node.js version: `node --version`
2. Install CLI globally: `npm install -g @webflow/cli`
3. Verify installation: `webflow --version`
## Quick Reference
**Workflow:** identify โ diagnose โ fix โ verify
**Diagnostic Flags:**
- `--version` / `-V` - Check CLI version
- `--help` / `-h` - Show command help
- `--verbose` - Detailed debugging output
- `--debug-bundler` - Show bundler config
**Common Fixes:**
- Not installed โ `npm install -g @webflow/cli`
- Wrong version โ `npm update -g @webflow/cli`
- Auth failed โ `webflow auth login`
- Build failed โ Check `--verbose` output
- Bundle error โ Check `--debug-bundler` output
- Missing deps โ `npm install`
**DRelated in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.