framer-local-dev-loop
Configure Framer local development with hot reload and testing. Use when setting up a development environment, configuring test workflows, or establishing a fast iteration cycle with Framer. Trigger with phrases like "framer dev setup", "framer local development", "framer dev environment", "develop with framer".
What this skill does
# Framer Local Dev Loop
## Overview
Set up a fast development workflow for Framer plugins and code components with Vite hot-reload, TypeScript, and testing.
## Prerequisites
- Completed `framer-install-auth` setup
- Node.js 18+ with npm
- Framer editor open
## Instructions
### Step 1: Plugin Dev Environment
```bash
npx create-framer-plugin@latest my-plugin
cd my-plugin
npm install
npm run dev # Starts Vite dev server — hot-reloads into Framer editor
```
Project structure:
```
my-plugin/
├── src/
│ ├── App.tsx # Plugin UI (React)
│ ├── main.tsx # Entry point
│ └── framer.d.ts # Type definitions
├── package.json
├── vite.config.ts # Vite config with framer-plugin
└── tsconfig.json
```
### Step 2: Connect to Framer Editor
1. Open Framer, go to your project
2. Click **Plugins** > **Development** in the toolbar
3. Select your local dev plugin
4. Changes in `src/App.tsx` hot-reload instantly
### Step 3: Testing Plugin Logic
```typescript
// tests/sync.test.ts — test data transformation outside Framer
import { describe, it, expect } from 'vitest';
// Extract pure functions for testability
function transformPosts(posts: any[]) {
return posts.map(p => ({
fieldData: {
title: p.title,
body: `<p>${p.body}</p>`,
slug: p.title.toLowerCase().replace(/[^a-z0-9]+/g, '-').slice(0, 50),
},
}));
}
describe('CMS Sync', () => {
it('should transform posts into CMS items', () => {
const posts = [{ title: 'Hello World', body: 'Content here', userId: 1 }];
const items = transformPosts(posts);
expect(items[0].fieldData.title).toBe('Hello World');
expect(items[0].fieldData.slug).toBe('hello-world');
expect(items[0].fieldData.body).toContain('<p>');
});
it('should handle slugs with special characters', () => {
const posts = [{ title: 'What\'s New in 2025?', body: 'test', userId: 1 }];
const items = transformPosts(posts);
expect(items[0].fieldData.slug).toBe('what-s-new-in-2025-');
});
});
```
### Step 4: Code Component Development
```bash
# Code components are edited directly in Framer editor
# For local development of shared component libraries:
mkdir framer-components && cd framer-components
npm init -y
npm install react framer typescript @types/react
```
```tsx
// components/Button.tsx — develop locally, paste into Framer
import { addPropertyControls, ControlType } from 'framer';
export default function Button({ label = 'Click me', variant = 'primary' }) {
const styles = {
primary: { background: '#000', color: '#fff' },
secondary: { background: '#eee', color: '#000' },
};
return <button style={{ ...styles[variant], padding: '12px 24px', border: 'none', borderRadius: 8, fontSize: 16, cursor: 'pointer' }}>{label}</button>;
}
addPropertyControls(Button, {
label: { type: ControlType.String, title: 'Label', defaultValue: 'Click me' },
variant: { type: ControlType.Enum, title: 'Variant', options: ['primary', 'secondary'], defaultValue: 'primary' },
});
```
### Step 5: Server API Development
```typescript
// server-dev.ts — develop Server API integrations locally
import { framer } from 'framer-api';
import 'dotenv/config';
async function dev() {
const client = await framer.connect({
apiKey: process.env.FRAMER_API_KEY!,
siteId: process.env.FRAMER_SITE_ID!,
});
// Test CMS operations
const collections = await client.getCollections();
console.log('Collections:', collections.map(c => `${c.name} (${c.type})`));
}
dev().catch(console.error);
```
## Output
- Vite-powered plugin with hot-reload into Framer editor
- Testable data transformation functions
- Local component development workflow
- Server API development setup
## Error Handling
| Error | Cause | Solution |
|-------|-------|----------|
| Plugin not showing | Dev server not running | Run `npm run dev` |
| Hot-reload not working | Wrong Vite config | Ensure `framer-plugin` Vite plugin is configured |
| `framer` undefined in tests | Editor-only API | Mock `framer` or extract pure functions |
| Component type errors | Missing Framer types | Install `@types/framer` or use `framer.d.ts` |
## Resources
- [create-framer-plugin](https://www.framer.com/developers/plugins-introduction)
- [Framer Developer Reference](https://www.framer.com/developers/reference)
- [Vitest](https://vitest.dev/)
## Next Steps
See `framer-sdk-patterns` for production-ready patterns.
Related 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.