zanmaiaffinitylisted

# affinity **Field notes, not law.** Everything here was verified the hard way on Affinity by Canva 2.6, working idioms and stumble warnings so you build fast instead of re-deriving. They are accelerators, not the boundary of what is allowed: the SDK is yours. When the design needs something these notes do not cover, explore (grep the JSLib, check `search_sdk_hints`, experiment on a scratch doc), and record what you find in `.zanmai/memory/technique/affinity.md` (dated, with a version and a confidence), curated, so the next run has it. ## What the SDK can and cannot do (the one hard shape) The SDK can **edit and compose a document's content** (text, images, fills, shapes, vector geometry) but **cannot construct design furniture**, no API to create master pages, named text/character styles, or add/duplicate pages. So the working shape is: a copy of the strongest template as structural carrier, and free composition on its pages, in the design language of all the templates. No template means no CI: stop and ask for one. From-scratch (end of file) cannot carry a brand. ## Access and pre-flight (do this first) - Tools: `mcp__affinity__*` (`execute_script`, `render_spread`, `render_selection`, `list_sdk_documentation`, `read_sdk_documentation_topic`, `list_library_scripts`, `read_library_script`, `search_sdk_hints`, `save_script_to_library`). Never `add_sdk_hint` (data egress). - The app's scripting server is itself MCP. Reach it only through the granted tools, never a hand-ro