What problem does it solve?
It solves the confusion and breakage that happen when writing Framer Code Components or Code Overrides, especially around SSR hydration, font rendering, and editor-vs-preview behavior.
Core Features & Use Cases
- Code Component vs Code Override guidance: Implement custom React components for the canvas (with property controls) or wrap existing elements via overrides (without property controls).
- Framer-specific required annotations: Add the correct
@framer* metadata and layout hints so the canvas understands sizing and unlink behavior.
- Operational safety patterns: Prevent hydration mismatches with client-only gating, avoid incorrect font styling by spreading the full
props.font, and keep state updates performant using startTransition.
- Advanced troubleshooting and behavior constraints: Handle portals for overlay stacking, intersection/scroll detection constraints, and WebGL/shader pitfalls; use property control patterns and common anti-pattern fixes.
- Use cases: Debug hydration errors in published pages, create editor-friendly debug overlays, implement shader/WebGL effects in Framer, and build interactive animations with reliable property controls.
Quick Start
Ask the AI to generate a Framer Code Component that uses property controls, includes the required @framer* annotations, spreads props.font correctly, and renders client-only logic safely to avoid hydration issues.