What problem does it solve? Designers working with AI agents often need a visual canvas for layout exploration and artboard iteration outside Figma, but agents may not know whether Paper tooling is connected or how to hand designs back to code. This Skill defines a clear workflow for using paper.design or a Paper MCP as the active design canvas, with honest fallback behavior when Paper is unavailable. ## Core Features & Use Cases - Availability Check: Confirms whether Paper access exists in the current agent before attempting canvas work, and states clearly when it does not. - Visual Iteration Workflow: Supports layout exploration, artboards, and translating product direction into screens while keeping designs tied to components, tokens, breakpoints, and states. - Implementation Handoff: Summarizes screens, tokens, component changes, and unresolved decisions when returning to code. - Use Case: A user asks the agent to mock up a new onboarding flow in Paper. The agent checks for a Paper MCP, works visually on the canvas if available, or falls back to Figma, Wiretext, an HTML artifact, or direct code if not. ## Quick Start Ask the agent to use Paper to explore layout options for a new screen and iterate on the artboards before implementation.