Code Components: Custom React components added to canvas. Support addPropertyControls.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionframer-code-components-overridesExecute the skills CLI command in your project's root directory to begin installation:
Fetches framer-code-components-overrides from fredm00n/framerlabs and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate framer-code-components-overrides. Access via /framer-code-components-overrides in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
2
total installs
2
this week
122
GitHub stars
0
upvotes
Run in your terminal
2
installs
2
this week
122
stars
Code Components: Custom React components added to canvas. Support addPropertyControls.
Code Overrides: Higher-order components wrapping existing canvas elements. Do NOT support addPropertyControls.
Always include at minimum:
/**
* @framerDisableUnlink
* @framerIntrinsicWidth 100
* @framerIntrinsicHeight 100
*/
Full set:
@framerDisableUnlink — Prevents unlinking when modified@framerIntrinsicWidth / @framerIntrinsicHeight — Default dimensions@framerSupportedLayoutWidth / @framerSupportedLayoutHeight — any, auto, fixed, any-prefer-fixedimport type { ComponentType } from "react"
import { useState, useEffect } from "react"
/**
* @framerDisableUnlink
*/
export function withFeatureName(Component): ComponentType {
return (props) => {
// State and logic here
return <Component {...props} />
}
}
Naming: Always use withFeatureName prefix.
import { motion } from "framer-motion"
import { addPropertyControls, ControlType } from "framer"
/**
* @framerDisableUnlink
* @framerIntrinsicWidth 300
* @framerIntrinsicHeight 200
*/
export default function MyComponent(props) {
const { style } = props
return <motion.div style={{ ...style }}>{/* content */}</motion.div>
}
MyComponent.defaultProps = {
// Always define defaults
}
addPropertyControls(MyComponent, {
// Controls here
})
Never access font properties individually. Always spread the entire font object.
// ❌ BROKEN - Will not work
style={{
fontFamily: props.font.fontFamily,
fontSize: props.font.fontSize,
}}
// ✅ CORRECT - Spread entire object
style={{
...props.font,
}}
Font control definition:
font: {
type: ControlType.Font,
controls: "extended",
defaultValue: {
fontFamily: "Inter",
fontWeight: 500,
fontSize: 16,
lineHeight: "1.5em",
},
}
All React state updates in Framer must be wrapped in startTransition():
import { startTransition } from "react"
// ❌ WRONG - May cause issues in Framer's rendering pipeline
setCount(count + 1)
// ✅ CORRECT - Always wrap state updates
startTransition(() => {
setCount(count + 1)
})
This is Framer-specific and prevents performance issues with concurrent rendering.
Framer pre-renders on server. Browser APIs unavailable during SSR.
Two-phase rendering pattern:
const [isClient, setIsClient] = useState(false)
useEffect(() => {
setIsClient(true)
}, [])
if (!isClient) {
return <Component {...props} /> // SSR-safe fallback
}
// Client-only logic here
Never access directly at render time:
window, document, navigatorlocalStorage, sessionStoragewindow.innerWidth, window.innerHeightimport { RenderTarget } from "framer"
const isOnCanvas = RenderTarget.current() === RenderTarget.canvas
// Show debug only in editor
{isOnCanvas && <DebugOverlay />}
Use for:
See references/property-controls.md for complete control types and patterns.
See references/patterns.md for implementations: shared state, keyboard detection, show-once logic, scroll effects, magnetic hover, animation triggers.
Cannot read variant names from props (may be hashed). Manage internally:
export function withVariantControl(Component): ComponentType {
return (props) => {
const [currentVariant, setCurrentVariant] = useState("variant-1")
// Logic to change variant
setCurrentVariant("variant-2")
return <Component {...props} variant={currentVariant} />
}
}
Framer's scroll detection uses viewport-based IntersectionObserver. Applying overflow: scroll to containers breaks this detection.
For scroll-triggered animations, use:
const observer = new IntersectionObserver(
(entries) => {
entries.forEach((entry) => {
if (entry.isIntersecting && !hasEntered) {
setHasEntered(true)
}
})
},
{ threshold: 0.1 }
)
See references/webgl-shaders.md for shader implementation patterns including transparency handling.
Standard import (preferred):
import { Component } from "package-name"
Force specific version via CDN when Framer cache is stuck:
import { Component } from "https://esm.sh/[email protected]?external=react,react-dom"
Always include ?external=react,react-dom for React components.
Chrome/Firefox do not natively support HLS streams. A plain <video src="...m3u8"> will either fail or play the lowest quality rendition permanently. Safari handles HLS natively.
Fix: Use HLS.js via dynamic import with silent fallback:
let HlsModule = null
let hlsImportAttempted = false
async function loadHls() {
if (hlsImportAttempted) return HlsModule
hlsImportAttempted = true
try {
const mod = await import("https://esm.sh/hls.js@1?external=react,Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
pproenca/dot-skills
asyrafhussin/agent-skills
shadcn/improve
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
framer-code-components-overrides fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
framer-code-components-overrides reduced setup friction for our internal harness; good balance of opinion and flexibility.
framer-code-components-overrides is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
framer-code-components-overrides fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in framer-code-components-overrides — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for framer-code-components-overrides matched our evaluation — installs cleanly and behaves as described in the markdown.
Registry listing for framer-code-components-overrides matched our evaluation — installs cleanly and behaves as described in the markdown.
We added framer-code-components-overrides from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend framer-code-components-overrides for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
framer-code-components-overrides reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 61