tommylower Paper
Use Paper as the active design canvas when the user asks for Paper or when the design workflow needs visual artboards and a Paper MCP is available.
Fit
Use Paper for:
- Visual layout exploration before implementation.
- Artboards and design iteration.
- Translating product direction into screens.
- Reviewing a canvas alongside code.
Do not pretend Paper is connected. If no Paper MCP/tooling is available in the current agent, say so and offer the nearest available path: Figma, Wiretext, an HTML artifact, or direct code implementation.
Workflow
- Confirm whether Paper access is available in the current agent.
- If available, create or open the canvas and work visually.
- Keep the design tied to implementation constraints: components, tokens, breakpoints, and states.
- When handing back to code, summarize the screens, tokens, component changes, and unresolved decisions.
Related Skills
figma-mcpfor Figma-to-code or token extraction.wiretextfor quick low-fidelity layouts.preflightfor static UI review before shipping.wip-senior-auditfor live product review.