← ClaudeAtlas

canva-recontentlisted

Rebuild an existing Canva design with new content while its layout, build steps and animations survive intact. Use whenever a Canva design is filled from a template, adapted after someone shared it, rebranded, translated, or edited across many pages at once — including when the user only says they want to reuse a deck rather than build one from scratch.
aminehaddad-git/presentation-skills · ★ 1 · Web & Frontend · score 74
Install: claude install-skill aminehaddad-git/presentation-skills
# Canva re-content Needs the Canva connector: `copy-design`, `read-design`, `edit-design`. A finished deck is a **template**: someone already solved the layout, the rhythm, the progressive reveals. Re-contenting keeps that solution and replaces only what it says. Text and speaker notes go through the API cleanly. Images, page deletion and animations do not — those become a **gaps file** the human finishes by hand. A run that pretends otherwise ships a broken deck. ## Before you start Confirm the design is one the user owns, has a licence to reuse, or was given by its author for this purpose. Templates and a colleague's shared deck qualify. If provenance is unclear, ask once. ## Steps **1 · Copy first.** `copy-design` with the source id; every later operation targets the copy. The original stays as found, which is what makes a bad result cheap to throw away and rerun. Done when you hold a new design id. **2 · Survey before you touch anything.** One `read-design` with `filter.fields:["presenter_notes"]` across the full page range shows which pages are already converted — cheap, and it catches resumed work. Then one `read-design` with `filter.fields:["design_content"]` (no transaction) returns plain readable text for many pages at once. Field-scoped reads stay small; the full element JSON of step 4 does not. Done when you can name what is on every page. **3 · Write the page map before editing.** A table: page number, what it currently holds, what it becomes, which sourc