---
name: apply-canvas-design
description: Implement an approved or edited Enhance canvas design in the owning product source, republish it, and verify source-to-design fidelity. Use for canvas-to-code or canvas-to-prototype handoff.
---

# Apply a canvas design

Use the installed interface: MCP tool contracts or CLI command help. A complete contract returned by search is ready to invoke; describe only when the contract is missing. No second interface is required. For canvas changes use `canvas_edit` / `canvas edit --edits`, preserve selection links, and reuse versions returned by successful writes. Render after a meaningful visual change.

1. Read the selected canvas screen, its exact structure and render, the current prototype, and the owning source. Confirm the source and design versions are not stale.
2. Identify the intended visual, structural, responsive, and interaction differences. Surface ambiguous or conflicting differences instead of inventing intent.
3. Locate the true source owner and implement the smallest complete change in the project's framework, component system, and tokens. Do not ship a detached canvas artifact as the product.
4. Build and republish from the person-selected local directory.
5. Exercise every changed state and viewport. Compare the published result with the selected design using both structure and rendered pixels; inspect clipping, overflow, assets, errors, and unrelated regressions.
6. Iterate until the implementation matches, then report the verified result and any explicit unresolved difference.

Follow MCP remediation. Never overwrite stale source, retry a write with different input under the same token, or reveal credentials, signed URLs, local paths, or private content.