Paste-up

Paper is where the design happens before any code, and the specification everything answers to afterwards. This skill covers both jobs: draw a file from a written spec, or open a file that already exists and put it right.

Pixel parity with Paper is never the goal downstream. What Paper governs is the information architecture, the step and state model, the hierarchy, the copy intent, the density and the operational behaviour.

Invoking it

A Paper URL is https://app.paper.design/file/<fileId>/<page>/<nodeId> - for example 01M1AMPBSYGK8DPDW1G5824M7K/1-0/FIE-0. The ULID is the fileId; pass it on every file-scoped call that accepts it, rather than relying on whichever file was most recently opened. 1-0 is the page. A trailing node id means the request is scoped to that one artboard; without it, the whole page is in scope.

• URL plus a repair ask ("go through this and make sure shared tokens are used") runs the repair lane. An audit-only request uses its inventory and checklist without edits, deletion or comment resolution.
• No URL runs the build lane, and the first thing to settle is which file and page to draw in.

Never read node ids back to the person who asked. Name artboards by what they show.

Before the file opens, either lane

Use the Paper MCP connection supplied by the host. If its guide or file tools are unavailable, report the missing connection and ask the user to connect the target file through the host’s supported Paper route (Paper Desktop for the local MCP server). Continue any brief preparation that does not need the connection; do not claim a file was inspected or edited.