Docs Canvas

Turns your documentation into an interactive canvas instead of a flat markdown file. You give it architecture notes, API references, runbooks, or design docs, and it renders them with a table of contents, structured sections, code blocks, diagrams, and callouts. It's meant for when you need to navigate a large body of technical writing without scrolling through a wall of text. The skill is currently a placeholder with the scaffold in place but light on implementation details, so expect the pattern to evolve. The underlying philosophy is sound though: lead with the answer, keep examples small, and pick whatever layout actually helps the reader understand fastest.

skills.sh installs: 1.2K
GitHub stars: 15.9K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add cursor/plugins --skill docs-canvas --agent claude-code

Installs into .claude/skills of the current project.

Files

Docs Canvas

Build a canvas that presents documentation — architecture notes, API references, design docs, runbooks, or codebase walkthroughs — as an interactive, navigable surface rather than as a flat markdown file.

Status: placeholder. The skill structure is in place so the canvas welcome page can surface this plugin via the marketplace query, but the full skill body still needs to be written. Treat the steps below as a starting outline and refine as the docs canvas pattern matures.

Prerequisites

Read ~/.cursor/skills-cursor/canvas/SKILL.md first. It contains the generation policy, design guidance, slop rules, self-check, and file-path conventions you must follow. The full component and hook surface is declared in ~/.cursor/skills-cursor/canvas/sdk/index.d.ts and its sibling .d.ts files — read them to discover exact exports and prop shapes rather than guessing.

Gather the source material

Accept any of: a directory of markdown files, a single doc URL, an inline outline, or a question to answer from the codebase. Collect headings, code blocks, diagrams, and any cross-references between documents.