framer-importlisted

# Clone a Framer site, deploy it, prompt changes, re-deploy The whole point: let anyone point at a **published** Framer URL, get a real static site they own, host it on Vercel, then say "change the hero to X" and ship again — without touching Framer's dashboard by hand. This skill is the orchestration layer over three pieces: ``` Framer (source of truth) ──edit──▶ export ──stitch──▶ deploy ▲ │ └────────────── "prompt a change" ◀─────────────────┘ ``` - **Edit** — via the `framer-agent-api` skill (drives real canvas/CMS edits through `@framer/agent`), then **publish** in Framer so the live URL updates. - **Export + stitch** — via this skill's scripts (wrapping FramerExport) to pull the published site into a routed, fully-localized static bundle. - **Deploy** — Vercel (or Netlify / Cloudflare Pages / any static host). ## How to run it (the flow) The person may not be technical, so **drive the flow** and keep it natural — talk in outcomes (their site, their pages, a link to share), not jargon or raw logs. The steps below are the shape; use your own words. 1. **Get the URL, confirm it's published.** You can only capture what's live on the `*.framer.app`/custom domain — if they just edited in Framer, have them Publish first. 2. **Clone it** (`ensure-deps.sh` if needed, then `clone-framer.mjs`). These are local and safe — just do them, with a light progress line, not a permission ask. 3.