paper

Guides visual design iteration on Paper artboards with fallbacks to Figma or code.

2|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/tommylower/cortex --skill paper-tommylower
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: paper
Source: https://github.com/tommylower/cortex/tree/main/design/tools/paper
Command: npx skills add https://github.com/tommylower/cortex --skill paper-tommylower

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about paper

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I use Paper for design work with an AI agent?▼

Ask the agent to use Paper or paper.design for your design task. The agent first confirms whether a Paper MCP or tooling is available, then creates or opens a canvas and iterates visually on artboards tied to your components and tokens.

What happens if Paper is not connected to my agent?▼

The agent states clearly that Paper tooling is unavailable rather than pretending it is connected. It then offers the nearest alternative path: Figma, Wiretext for low-fidelity layouts, an HTML artifact, or direct code implementation.

When should I use Paper instead of Figma for design iteration?▼

Use Paper when you want active visual canvas work with artboards and layout exploration outside Figma, especially when a Paper MCP is available. Use Figma when you need Figma-to-code workflows or token extraction via figma-mcp.

How does a Paper design hand off to code implementation?▼

When handing back to code, the agent summarizes the screens, design tokens, component changes, and any unresolved decisions. This keeps the visual work tied to implementation constraints like breakpoints and states.

What are the limitations of the Paper design workflow?▼

The workflow depends entirely on Paper MCP or tooling being available in the current agent; without it, no canvas work is possible. It also does not replace static UI review or live product audits, which are handled by related skills like preflight.