Agent skill · data analytics · jeremylongshore
framer-common-errors
Diagnose and fix Framer common errors and exceptions.
Why this skill is useful
Provides specific diagnostic commands and error handling patterns for troubleshooting Framer integration issues that the AI wouldn't reliably generate on its own.
What it needs
Requires npm installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Framer Common Errors Prerequisites An authorized site owner, an opaque incident ID, redacted diagnostics, and a safe staging reproduction path. Instructions Classify the issue as publishing, domain, asset, access, integration, or availability; reproduce with a staging page; apply the smallest reversible correction; verify both recovery and a safe failure response. Output Return a receipt with category, opaque correlation ID, action, verification, owner, and follow-up. Keep visitor data, tokens, and page content out of support evidence. Error Handling Pause publishing or integration changes on access, domain, or unexpected-destination failures. Use a rollback and route repeated failures to the site owner. Examples Break a fictional staging publish configuration, restore it, and verify the production site is untouched while the receipt contains no visitor or credential data. Overview Diagnostic reference for common Framer plugin, component, and Server API errors with actionable fixes. Error Reference Plugin Not Appearing in Editor Cause: Dev server not running or plugin not registered. Fix: --- framer is not defined Cause: Calling framer API outside the Framer editor iframe context. Fix: The framer global from framer-plugin only works inside the editor. For server-side access, use framer-api package instead. --- Component Renders Blank on Canvas Cause: Runtime error in component code (swallowed by Framer). Fix: Open Framer's browser console (right-click > Inspect) and check for errors. Common causes: Missing export default on component Undefined props without defaults Fetch errors from blocked CORS requests --- addPropertyControls Not Showing Cause: Called on wrong component or wrong import. Fix: --- Code Override Not Applying Cause: Override function not returning correct shape. Fix: Overrides must return an Override type object (Framer Motion props): --- Server API WebSocket connection failed Cause: Invalid API key, wrong site ID, or network blocking WSS. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/framer-common-errors