AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Paper

skill-tommylower-cortex-paper · by tommylower

Paper design canvas workflow for active design work through paper.design or a Paper MCP when available. Use when the user asks to use Paper, paper.design, a visual canvas, artboards, or active design iteration outside Figma. If Paper tools are unavailable, state that clearly and fall back to Figma, Wiretext, browser artifacts, or code.

↗ Repository
— No reviews yet
0 installs
0 views
— view→install

Install

$ agentstack add skill-tommylower-cortex-paper

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Paper? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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

  1. Confirm whether Paper access is available in the current agent.
  2. If available, create or open the canvas and work visually.
  3. Keep the design tied to implementation constraints: components, tokens, breakpoints, and states.
  4. When handing back to code, summarize the screens, tokens, component changes, and unresolved decisions.

Related Skills

  • figma-mcp for Figma-to-code or token extraction.
  • wiretext for quick low-fidelity layouts.
  • preflight for static UI review before shipping.
  • wip-senior-audit for live product review.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Web & Browser