| name | sales-framer |
| description | Framer platform help — design-first AI website builder for marketing sites, landing pages, and portfolios (Figma-like canvas, AI design agents, CMS Collections, A/B testing, localization) with a developer surface: the Server API (framer-api npm package, API key from site settings, stateful WebSocket + REST/webhook interop — sync CMS from Notion/Airtable, publish programmatically, drive from Claude Code/Cursor), a Plugin API, and Fetch for dynamic data. Use when automating Framer CMS updates or publishing from a server or AI agent, hitting CMS item caps (100 on Basic, 1,000 per collection on Pro), structured data/JSON-LD or hreflang isn't supported and rankings suffer, weighing the no-code-export lock-in before committing, per-language localization and per-seat editor costs balloon the bill, or adding checkout to a Framer site via embeds. Do NOT use for landing-page strategy or builder selection (use /sales-funnel) or checkout platform choice (use /sales-checkout). |
| argument-hint | [describe what you need help with in Framer] |
| license | MIT |
| version | 1.0.0 |
| tags | ["sales","funnels","website-builder","platform"] |
| github | https://github.com/framer |
Framer Platform Help
Framer is a design-first, AI-assisted website builder — a Figma-like canvas that publishes production marketing sites, with AI design agents and a beta Server API built for agent-driven workflows (Claude Code/Cursor). Its structural trades: no code export (full platform lock-in) and content/SEO depth behind Webflow (CMS caps, no JSON-LD/hreflang).
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated platform knowledge.
Ask only what you can't infer from the user's prompt:
-
What are you trying to do?
- A) Build/ship a site (landing page, portfolio, marketing site)
- B) Automate the CMS or publishing (Server API, Notion/Airtable sync, AI-agent workflows)
- C) Fix SEO/content limits (structured data, hreflang, CMS caps)
- D) Understand pricing (plans + seat + per-language add-ons) or the lock-in trade
- E) Add commerce/checkout to a Framer site
-
Which plan? CMS caps, robots.txt editing, and A/B testing are plan-gated — most limit questions are plan questions.
Skip-ahead rule: if the user's prompt already has enough context, go straight to Step 2.
Step 2 — Route or answer directly
| If the user's question is about… | Route to |
|---|
| Which site/landing-page builder to pick (Framer vs Webflow/WordPress builders/Unbounce) | /sales-funnel {question} |
| Landing-page conversion strategy across tools | /sales-funnel {question} |
| Which checkout to embed (Snipcart vs Foxy vs Lemon Squeezy vs Stripe links) | /sales-checkout {question} |
| Tax-handled checkout (Merchant of Record) | /sales-merchant-of-record {question} |
| SEO strategy beyond Framer's controls | /sales-seo {question} |
When routing, give the exact command: "This is a {domain} question — run: /sales-funnel {original question}"
Otherwise, answer Framer-specific questions directly using Step 3.
Step 3 — Framer platform reference
Read references/platform-guide.md for the full reference — capabilities & automation surface, pricing/plan gates, data model, and quick-start recipes (Server API CMS sync, Claude Code agent workflow, adding checkout).
